From: Mark Salyzyn <salyzyn@android.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
Miklos Szeredi <miklos@szeredi.hu>,
Jonathan Corbet <corbet@lwn.net>, Vivek Goyal <vgoyal@redhat.com>,
Amir Goldstein <amir73il@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
John Stultz <john.stultz@linaro.org>,
linux-doc@vger.kernel.org, linux-security-module@vger.kernel.org,
selinux@vger.kernel.org
Subject: Re: [PATCH v18 0/4] overlayfs override_creds=off & nested get xattr fix
Date: Wed, 21 Oct 2020 08:15:19 -0700 [thread overview]
Message-ID: <c6ca6eea-2fb2-2278-bc4a-39c43e984657@android.com> (raw)
In-Reply-To: <87wnzj6305.fsf@x220.int.ebiederm.org>
On 10/21/20 7:57 AM, Eric W. Biederman wrote:
> Is there any reason why the cc list from the body of the email does not
> match the people who have been cc'd on the email. Skipping the
> linux-unionfs list (which seems to be the mail list for overlayfs)
> seems like a pretty big oversight.
>
>> Signed-off-by: Mark Salyzyn <salyzyn@android.com>
>> Cc: Miklos Szeredi <miklos@szeredi.hu>
>> Cc: Jonathan Corbet <corbet@lwn.net>
>> Cc: Vivek Goyal <vgoyal@redhat.com>
>> Cc: Eric W. Biederman <ebiederm@xmission.com>
>> Cc: Amir Goldstein <amir73il@gmail.com>
>> Cc: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Stephen Smalley <sds@tycho.nsa.gov>
>> Cc: John Stultz <john.stultz@linaro.org>
>> Cc: linux-doc@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org
>> To: linux-fsdevel@vger.kernel.org
>> To: linux-unionfs@vger.kernel.org
>> Cc: linux-security-module@vger.kernel.org
>> Cc: kernel-team@android.com
>> Cc: selinux@vger.kernel.org
> Eric
>
I used git send-email to do the heavy lifting of sending the submission,
minus the obligatory maintainers script because it adds 100s of
recipients and breaks entry into several of the lists. AFAICT send-email
appears to not add To: entries found in the body, only Cc: entries :-(.
I will resend with everything as Cc: entries shortly.
Sincerely -- Mark Salyzyn
prev parent reply other threads:[~2020-10-21 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 14:35 [PATCH v18 0/4] overlayfs override_creds=off & nested get xattr fix Mark Salyzyn
2020-10-21 14:35 ` [PATCH v18 1/4] Add flags option to get xattr method paired to __vfs_getxattr Mark Salyzyn
2020-10-21 14:35 ` [PATCH v18 2/4] overlayfs: handle XATTR_NOSECURITY flag for get xattr method Mark Salyzyn
2020-10-21 14:35 ` [PATCH v18 3/4] overlayfs: override_creds=off option bypass creator_cred Mark Salyzyn
2020-10-21 14:35 ` [PATCH v18 4/4] overlayfs: inode_owner_or_capable called during execv Mark Salyzyn
2020-10-21 14:57 ` [PATCH v18 0/4] overlayfs override_creds=off & nested get xattr fix Eric W. Biederman
2020-10-21 15:15 ` Mark Salyzyn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c6ca6eea-2fb2-2278-bc4a-39c43e984657@android.com \
--to=salyzyn@android.com \
--cc=amir73il@gmail.com \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=rdunlap@infradead.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).