From: Kees Cook <keescook@chromium.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Denys Vlasenko <vda.linux@googlemail.com>,
Vlastimil Babka <vbabka@suse.cz>,
"Liam R . Howlett" <liam.howlett@oracle.com>,
Jann Horn <jannh@google.com>,
linux-mm@kvack.org
Subject: Re: [GIT PULL] Fix fill_files_note
Date: Wed, 9 Mar 2022 13:45:56 -0800 [thread overview]
Message-ID: <202203091345.3755C2B5@keescook> (raw)
In-Reply-To: <8735jqdg84.fsf@email.froward.int.ebiederm.org>
On Wed, Mar 09, 2022 at 02:27:07PM -0600, Eric W. Biederman wrote:
> It turns out I missed a crazy corner case of binfmt_flat, when coredumps
> are disabled. This fixes a compile error that was reported.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git coredump-vma-snapshot-fix-for-v5.18
> HEAD: f833116ad2c3eabf9c739946170e07825cca67ed coredump: Don't compile flat_core_dump when coredumps are disabled
>
> Can you include this as well.
Thanks! Pulled and pushed out.
--
Kees Cook
prev parent reply other threads:[~2022-03-09 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220131153740.2396974-1-willy@infradead.org>
[not found] ` <871r0nriy4.fsf@email.froward.int.ebiederm.org>
[not found] ` <YfgKw5z2uswzMVRQ@casper.infradead.org>
[not found] ` <877dafq3bw.fsf@email.froward.int.ebiederm.org>
[not found] ` <YfgPwPvopO1aqcVC@casper.infradead.org>
[not found] ` <CAG48ez3MCs8d8hjBfRSQxwUTW3o64iaSwxF=UEVtk+SEme0chQ@mail.gmail.com>
[not found] ` <87bkzroica.fsf_-_@email.froward.int.ebiederm.org>
2022-03-08 19:35 ` [GIT PULL] Fix fill_files_note Eric W. Biederman
2022-03-08 21:49 ` Kees Cook
2022-03-09 16:29 ` Eric W. Biederman
2022-03-09 16:32 ` Kees Cook
2022-03-09 20:27 ` Eric W. Biederman
2022-03-09 21:45 ` Kees Cook [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=202203091345.3755C2B5@keescook \
--to=keescook@chromium.org \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=vda.linux@googlemail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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).