From: Al Viro <viro@zeniv.linux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 00/13] Clean up kernel_read/kernel_write
Date: Thu, 15 Oct 2020 19:23:34 +0100 [thread overview]
Message-ID: <20201015182334.GQ3576660@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20201015175641.GC23287@lst.de>
On Thu, Oct 15, 2020 at 07:56:41PM +0200, Christoph Hellwig wrote:
> Al,
>
> can you pick up patches 1 and 2 to unbreak linux-next?
OK... I really don't like the idea of mangling base.set_fs, so
a bit of bisect hazard will be there - I'd put these two into
a branch on top of base.set_fs (#work.set_fs). Regenerated
with addition of your reviewed-by, added to #for-next and pushed
out.
prev parent reply other threads:[~2020-10-15 18:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 2:55 [PATCH 00/13] Clean up kernel_read/kernel_write Matthew Wilcox (Oracle)
2020-10-03 2:55 ` [PATCH 01/13] fs: Allow a NULL pos pointer to __kernel_write Matthew Wilcox (Oracle)
2020-10-15 17:56 ` Christoph Hellwig
2020-10-03 2:55 ` [PATCH 02/13] fs: Allow a NULL pos pointer to __kernel_read Matthew Wilcox (Oracle)
2020-10-15 17:56 ` Christoph Hellwig
2020-10-03 2:55 ` [PATCH 03/13] fs/acct: Pass a NULL pointer to __kernel_write Matthew Wilcox (Oracle)
2020-10-03 2:55 ` [PATCH 04/13] um/mconsole: Pass a NULL pointer to kernel_read Matthew Wilcox (Oracle)
2020-10-03 2:55 ` [PATCH 05/13] x86/aout: " Matthew Wilcox (Oracle)
2020-10-03 2:55 ` [PATCH 06/13] aout: " Matthew Wilcox (Oracle)
2020-10-03 2:55 ` [PATCH 07/13] binfmt_flat: " Matthew Wilcox (Oracle)
2020-10-03 2:55 ` [PATCH 08/13] exec: " Matthew Wilcox (Oracle)
2020-10-03 2:55 ` [PATCH 09/13] bpfilter: Pass a NULL pointer to kernel_read and kernel_write Matthew Wilcox (Oracle)
2020-10-03 2:55 ` [PATCH 10/13] keys: " Matthew Wilcox (Oracle)
2020-10-03 2:55 ` [PATCH 11/13] target: Pass a NULL pointer to kernel_write Matthew Wilcox (Oracle)
2020-10-03 2:55 ` [PATCH 12/13] proc: " Matthew Wilcox (Oracle)
2020-10-03 2:55 ` [PATCH 13/13] usermode: " Matthew Wilcox (Oracle)
2020-10-03 3:47 ` [PATCH 00/13] Clean up kernel_read/kernel_write Al Viro
2020-10-09 22:07 ` Eric Biggers
2020-10-15 17:56 ` Christoph Hellwig
2020-10-15 18:23 ` Al Viro [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=20201015182334.GQ3576660@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.