Message ID | 20230123183926.249601-1-mcgrof@kernel.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:eb09:0:0:0:0:0 with SMTP id s9csp1760619wrn; Mon, 23 Jan 2023 10:41:40 -0800 (PST) X-Google-Smtp-Source: AMrXdXuLGOOTEYPwE7rqK/HC8+2ffviB4FJRy4wj3e4yCsfftPnbwlOPFhsEM6kOmwy/1xim9rcU X-Received: by 2002:a05:6a21:6daa:b0:b5:bc9b:36e4 with SMTP id wl42-20020a056a216daa00b000b5bc9b36e4mr33405611pzb.13.1674499300000; Mon, 23 Jan 2023 10:41:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1674499299; cv=none; d=google.com; s=arc-20160816; b=VAnvqWiuvwoxw/+/o6T8VbxOG3UjCZcJwtNqDmx6OhNxlAZMM5M4Riw8F2A/wQHiXq mlE/M5Nai/TX+ZHDA1SlbB8C1q/Cowz2Ow5y6W+h2HnD00cit5vqJ5dmOBw2lZzKy6P+ PBvfJ8iXXr5KvoGjwGRDUaTqbGGdyLhMIGMs3zxuz4JZ3hnvIVDyd6VRQzhlqP5gZpYw tg77FCwGCW5ZffY+qg810K46H8cfkmG/pdPpe2grto/KvRE2AnjpNsTX37/F+LRxCHnq GuCGsHufHGSAMAnLVrPb0EPI0HQk68hOidfmHcetyzn2KfGWnwRKj8KT1qw5oGTx5i9T Wq9A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=GYeGWMkYLov4QK4pkK8lvvB+kYPg+vVKNOZaYmrHXbY=; b=OihWpI45WZ5iwnPMepuH+nVBu0uWhgpA196mEb84zSMxHvGn1EKd8+slljnNVnztRt VgN6bF2rlEgT2q8ExKJevHBnZIylmTRaQcYn/5i75rAV8MpuCAl85R7XlDK01BTaOTXL GH/K/hYzxSWUmwniM0Vpwbe7gYx9xxVGuHhTPVkpwZmwjYqN9jDKBxlZhUElR1JcsJ4c Xj2+BNh4gMwru3zxUSNsSJQx9cf3ak3cHyOg1uqYe4DKjy/DGkNzjDZteoaa3wA9rrSa 6Wf3EoNm++8KwlfIreR/SwBpMdn2xDtR/G4QL8aD3bCKpA2oKu16AupN2dkTQDIixEND u4Eg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=bombadil.20210309 header.b=hKBjTdma; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e10-20020a63aa0a000000b004789f4ef89fsi52042342pgf.875.2023.01.23.10.41.27; Mon, 23 Jan 2023 10:41:39 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@infradead.org header.s=bombadil.20210309 header.b=hKBjTdma; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232709AbjAWSjz (ORCPT <rfc822;rust.linux@gmail.com> + 99 others); Mon, 23 Jan 2023 13:39:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50700 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232738AbjAWSjs (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 23 Jan 2023 13:39:48 -0500 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F1DBB22DC8; Mon, 23 Jan 2023 10:39:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Sender:Content-Transfer-Encoding: Content-Type:MIME-Version:Message-Id:Date:Subject:Cc:To:From:Reply-To: Content-ID:Content-Description:In-Reply-To:References; bh=GYeGWMkYLov4QK4pkK8lvvB+kYPg+vVKNOZaYmrHXbY=; b=hKBjTdmagqddwOXhL9SHigxZJ5 3Gij3l2SPXkefz85Oh87vkxqVE/l/y03ca8YWVnqdFtP49vRmFv+d2GCUzf/qFDw7mNZxpn5ifRZe Il61AJ9blRyUOVoWoVdIU2iV6ehnOeWTiCJNnUlJpbhw1QCMH5edw2xCmfys0wFbakccOvW5vRiQd nMyZM7rDnn9WrBUXcZJGD3NNjOqwZqLt5Vi54BPOQipWRWoeRDwCpqCSpVbZFnlP1dF0cwLcxrp2j IoFvvRJeZ1R/sFiL3inNcE8cf5c56kc1bMJUHTw2Pf7YILmEJ35x+ue8QT6uqn+TyC6v101nvDpDf M5rIfUrg==; Received: from mcgrof by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1pK1jC-0012wu-JU; Mon, 23 Jan 2023 18:39:34 +0000 From: Luis Chamberlain <mcgrof@kernel.org> To: corbet@lwn.net, gregkh@linuxfoundation.org, javier.gonz@samsung.com, linux-doc@vger.kernel.org Cc: a.manzanares@samsung.com, dave@stgolabs.net, darren@os.amperecomputing.com, catalin.marinas@arm.com, mcgrof@kernel.org, ndesaulniers@google.com, gost.dev@samsung.com, linux-kernel@vger.kernel.org, Luis Chamberlain <mcgrof.c@samsung.com> Subject: [PATCH] docs: embargoed-hardware-issues: add embargoed HW contact for Samsung Date: Mon, 23 Jan 2023 10:39:26 -0800 Message-Id: <20230123183926.249601-1-mcgrof@kernel.org> X-Mailer: git-send-email 2.37.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: Luis Chamberlain <mcgrof@infradead.org> X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1755839777860058778?= X-GMAIL-MSGID: =?utf-8?q?1755839777860058778?= |
Series |
docs: embargoed-hardware-issues: add embargoed HW contact for Samsung
|
|
Commit Message
Luis Chamberlain
Jan. 23, 2023, 6:39 p.m. UTC
After discussions internally at the company, Javier has been volunteered
and is willing to be the embargoed hardware contact for Samsung.
Cc: Javier González <javier.gonz@samsung.com>
Signed-off-by: Luis Chamberlain <mcgrof.c@samsung.com>
---
Documentation/process/embargoed-hardware-issues.rst | 1 +
1 file changed, 1 insertion(+)
Comments
On Mon, Jan 23, 2023 at 10:39:26AM -0800, Luis Chamberlain wrote: > After discussions internally at the company, Javier has been volunteered > and is willing to be the embargoed hardware contact for Samsung. > > Cc: Javier González <javier.gonz@samsung.com> > Signed-off-by: Luis Chamberlain <mcgrof.c@samsung.com> > --- > Documentation/process/embargoed-hardware-issues.rst | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst > index b6b4481e2474..fbb754253cf7 100644 > --- a/Documentation/process/embargoed-hardware-issues.rst > +++ b/Documentation/process/embargoed-hardware-issues.rst > @@ -251,6 +251,7 @@ an involved disclosed party. The current ambassadors list: > IBM Z Christian Borntraeger <borntraeger@de.ibm.com> > Intel Tony Luck <tony.luck@intel.com> > Qualcomm Trilok Soni <tsoni@codeaurora.org> > + Samsung Javier González <javier.gonz@samsung.com> No tab? :(
On Mon, Jan 23, 2023 at 07:54:34PM +0100, Greg KH wrote: > On Mon, Jan 23, 2023 at 10:39:26AM -0800, Luis Chamberlain wrote: > > After discussions internally at the company, Javier has been volunteered > > and is willing to be the embargoed hardware contact for Samsung. > > > > Cc: Javier González <javier.gonz@samsung.com> > > Signed-off-by: Luis Chamberlain <mcgrof.c@samsung.com> > > --- > > Documentation/process/embargoed-hardware-issues.rst | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst > > index b6b4481e2474..fbb754253cf7 100644 > > --- a/Documentation/process/embargoed-hardware-issues.rst > > +++ b/Documentation/process/embargoed-hardware-issues.rst > > @@ -251,6 +251,7 @@ an involved disclosed party. The current ambassadors list: > > IBM Z Christian Borntraeger <borntraeger@de.ibm.com> > > Intel Tony Luck <tony.luck@intel.com> > > Qualcomm Trilok Soni <tsoni@codeaurora.org> > > + Samsung Javier González <javier.gonz@samsung.com> > > No tab? :( I'll send a fix on v2. BTW while at it, it got me wondering, since most of the emails on this hw embargo page are not required to have kernel.org accounts not all of the folks on that page have a PGP key on the pgpkeys git tree [0]. Today we constrain kernel.org accounts to folks that send pull requests to Linus. Not all folks on the embargo list need to also be active kernel developers. Given the issues reported before by Konstantin on PGP keyservers we rely on our own git tree for keys we wish to get access to in our community. The below email addresses do not have any PGP key associated on the pgpkeys tree as of this day. * Tom Lendacky <thomas.lendacky@amd.com> * Catalin Marinas <catalin.marinas@arm.com> * Anton Blanchard <anton@linux.ibm.com> * Trilok Soni <tsoni@codeaurora.org> * James Morris <jamorris@linux.microsoft.com So it occurs to me to perhaps modify pgpg keys documentation to welcome community related keys to at least include folks like the above for the hw embargo emails should communication via PGP be required. Thoughts? [0] https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git Luis
On Mon, Jan 23, 2023 at 01:48:03PM -0800, Luis Chamberlain wrote: > > > @@ -251,6 +251,7 @@ an involved disclosed party. The current ambassadors list: > > > IBM Z Christian Borntraeger <borntraeger@de.ibm.com> > > > Intel Tony Luck <tony.luck@intel.com> > > > Qualcomm Trilok Soni <tsoni@codeaurora.org> > > > + Samsung Javier González <javier.gonz@samsung.com> > > I'll send a fix on v2. > > BTW while at it, it got me wondering, since most of the emails on > this hw embargo page are not required to have kernel.org accounts This isn't the list of hw embargo people. This is the list of "ambassadors" who can help people work through the security disclosure process. My impression is that it's to tell me that I should contact Konrad, since he also works at Oracle, to help me through the process. It's not for people outside Oracle to contact. If I have the wrong impression of that list, perhaps the description could be clarified. > not all of the folks on that page have a PGP key on the pgpkeys git > tree [0]. Today we constrain kernel.org accounts to folks that send > pull requests to Linus. Not all folks on the embargo list need to also > be active kernel developers. Given the issues reported before by Konstantin > on PGP keyservers we rely on our own git tree for keys we wish to get access > to in our community. The below email addresses do not have any PGP > key associated on the pgpkeys tree as of this day. > > * Tom Lendacky <thomas.lendacky@amd.com> > * Catalin Marinas <catalin.marinas@arm.com> > * Anton Blanchard <anton@linux.ibm.com> > * Trilok Soni <tsoni@codeaurora.org> > * James Morris <jamorris@linux.microsoft.com > > So it occurs to me to perhaps modify pgpg keys documentation to welcome > community related keys to at least include folks like the above for the > hw embargo emails should communication via PGP be required. Thoughts? > > [0] https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git > > Luis
On Tue, Jan 24, 2023 at 02:39:53AM +0000, Matthew Wilcox wrote: > On Mon, Jan 23, 2023 at 01:48:03PM -0800, Luis Chamberlain wrote: > > > > @@ -251,6 +251,7 @@ an involved disclosed party. The current ambassadors list: > > > > IBM Z Christian Borntraeger <borntraeger@de.ibm.com> > > > > Intel Tony Luck <tony.luck@intel.com> > > > > Qualcomm Trilok Soni <tsoni@codeaurora.org> > > > > + Samsung Javier González <javier.gonz@samsung.com> > > > > I'll send a fix on v2. > > > > BTW while at it, it got me wondering, since most of the emails on > > this hw embargo page are not required to have kernel.org accounts > > This isn't the list of hw embargo people. This is the list of > "ambassadors" who can help people work through the security disclosure > process. My impression is that it's to tell me that I should contact > Konrad, since he also works at Oracle, to help me through the process. > It's not for people outside Oracle to contact. > > If I have the wrong impression of that list, perhaps the description > could be clarified. That is correct, but it is primarily a list that I use when needing to contact companies about potential issues in their hardware. For that I don't need a GPG key, that's only required if they need to get added to a secure mailing list, and at that point I can have a key sent to me, it does not have to be in our kernel.org keyring at all (and list participants usually are not there.) So there's no need for any of these addresses to be part of the kernel gpg ring of trust for any of their activities. thanks, greg k-h
On Mon, Jan 23, 2023 at 01:48:03PM -0800, Luis Chamberlain wrote: > The below email addresses do not have any PGP > key associated on the pgpkeys tree as of this day. [...] > * Catalin Marinas <catalin.marinas@arm.com> FWIW, this one does have a key: keys/6BD6B12D00C85EF1.asc
On Tue, Jan 24, 2023 at 06:20:46AM +0100, Greg KH wrote: > On Tue, Jan 24, 2023 at 02:39:53AM +0000, Matthew Wilcox wrote: > > On Mon, Jan 23, 2023 at 01:48:03PM -0800, Luis Chamberlain wrote: > > > > > @@ -251,6 +251,7 @@ an involved disclosed party. The current ambassadors list: > > > > > IBM Z Christian Borntraeger <borntraeger@de.ibm.com> > > > > > Intel Tony Luck <tony.luck@intel.com> > > > > > Qualcomm Trilok Soni <tsoni@codeaurora.org> > > > > > + Samsung Javier González <javier.gonz@samsung.com> > > > > > > I'll send a fix on v2. > > > > > > BTW while at it, it got me wondering, since most of the emails on > > > this hw embargo page are not required to have kernel.org accounts > > > > This isn't the list of hw embargo people. This is the list of > > "ambassadors" who can help people work through the security disclosure > > process. My impression is that it's to tell me that I should contact > > Konrad, since he also works at Oracle, to help me through the process. > > It's not for people outside Oracle to contact. > > > > If I have the wrong impression of that list, perhaps the description > > could be clarified. > > That is correct, but it is primarily a list that I use when needing to > contact companies about potential issues in their hardware. That is the impression I gathered. > For that I > don't need a GPG key, that's only required if they need to get added to > a secure mailing list, and at that point I can have a key sent to me, it > does not have to be in our kernel.org keyring at all (and list > participants usually are not there.) That might be useful to explain in the documentation. > So there's no need for any of these addresses to be part of the kernel > gpg ring of trust for any of their activities. Sounds good. Luis
On Tue, Jan 24, 2023 at 08:22:45AM -0800, Luis Chamberlain wrote: > On Tue, Jan 24, 2023 at 06:20:46AM +0100, Greg KH wrote: > > On Tue, Jan 24, 2023 at 02:39:53AM +0000, Matthew Wilcox wrote: > > > On Mon, Jan 23, 2023 at 01:48:03PM -0800, Luis Chamberlain wrote: > > > > > > @@ -251,6 +251,7 @@ an involved disclosed party. The current ambassadors list: > > > > > > IBM Z Christian Borntraeger <borntraeger@de.ibm.com> > > > > > > Intel Tony Luck <tony.luck@intel.com> > > > > > > Qualcomm Trilok Soni <tsoni@codeaurora.org> > > > > > > + Samsung Javier González <javier.gonz@samsung.com> > > > > > > > > I'll send a fix on v2. > > > > > > > > BTW while at it, it got me wondering, since most of the emails on > > > > this hw embargo page are not required to have kernel.org accounts > > > > > > This isn't the list of hw embargo people. This is the list of > > > "ambassadors" who can help people work through the security disclosure > > > process. My impression is that it's to tell me that I should contact > > > Konrad, since he also works at Oracle, to help me through the process. > > > It's not for people outside Oracle to contact. > > > > > > If I have the wrong impression of that list, perhaps the description > > > could be clarified. > > > > That is correct, but it is primarily a list that I use when needing to > > contact companies about potential issues in their hardware. > > That is the impression I gathered. > > > For that I > > don't need a GPG key, that's only required if they need to get added to > > a secure mailing list, and at that point I can have a key sent to me, it > > does not have to be in our kernel.org keyring at all (and list > > participants usually are not there.) > > That might be useful to explain in the documentation. It is not really needed as the kernel.org gpg keyring has nothing to do with this list or the people on it. No need to say "that other thing over there has nothing to do with this thing here", otherwise we would be enumerating everything in this file :) thanks, greg k-h
diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst index b6b4481e2474..fbb754253cf7 100644 --- a/Documentation/process/embargoed-hardware-issues.rst +++ b/Documentation/process/embargoed-hardware-issues.rst @@ -251,6 +251,7 @@ an involved disclosed party. The current ambassadors list: IBM Z Christian Borntraeger <borntraeger@de.ibm.com> Intel Tony Luck <tony.luck@intel.com> Qualcomm Trilok Soni <tsoni@codeaurora.org> + Samsung Javier González <javier.gonz@samsung.com> Microsoft James Morris <jamorris@linux.microsoft.com> VMware