From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "J. R. Okajima" <hooanon05g@gmail.com>,
Ira Weiny <ira.weiny@intel.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH][CFT] [coredump] don't use __kernel_write() on kmap_local_page()
Date: Tue, 4 Oct 2022 01:52:23 +0100 [thread overview]
Message-ID: <YzuDx8eTUVK74DIQ@ZenIV> (raw)
In-Reply-To: <CAHk-=wiL2=FfSQx0pHkWAQW29Rc-htDtCouOe6Yp3r5C0tHPwA@mail.gmail.com>
On Mon, Oct 03, 2022 at 05:37:24PM -0700, Linus Torvalds wrote:
> On Mon, Oct 3, 2022 at 5:31 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > OK, incremental is in #fixes, pushed out.
>
> I'm assuming I'll still get a proper pull request. No?
Pull request follows; after all, whatever else is there, this is an obvious
fix for the breakage Okajima caught...
Al, very much hoping there's no other embarrassing fuckups lurking in that
thing ;-/
The following changes since commit 4fe89d07dcc2804c8b562f6c7896a45643d34b2f:
Linux 6.0 (2022-10-02 14:09:07 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes
for you to fetch changes up to 4f526fef91b24197d489ff86789744c67f475bb4:
[brown paperbag] fix coredump breakage (2022-10-03 20:28:38 -0400)
----------------------------------------------------------------
fs/coredump fix
----------------------------------------------------------------
Al Viro (1):
[brown paperbag] fix coredump breakage
fs/coredump.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
next prev parent reply other threads:[~2022-10-04 0:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 22:51 [PATCH][CFT] [coredump] don't use __kernel_write() on kmap_local_page() Al Viro
2022-09-28 17:57 ` Eric W. Biederman
2022-09-28 18:29 ` Al Viro
2022-10-03 3:51 ` Ira Weiny
2022-10-03 10:48 ` J. R. Okajima
2022-10-03 19:31 ` Ira Weiny
2022-10-03 22:18 ` Al Viro
2022-10-03 22:58 ` J. R. Okajima
2022-10-03 23:37 ` Al Viro
2022-10-04 0:20 ` Linus Torvalds
2022-10-04 0:31 ` Al Viro
2022-10-04 0:37 ` Linus Torvalds
2022-10-04 0:52 ` Al Viro [this message]
2022-10-04 6:18 ` Sedat Dilek
2022-10-09 10:37 ` Sedat Dilek
2022-11-09 13:57 ` Geert Uytterhoeven
2022-10-04 2:17 ` Ira Weiny
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=YzuDx8eTUVK74DIQ@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=hooanon05g@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).