[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201026083836.GA24911@duo.ucw.cz>
Date: Mon, 26 Oct 2020 09:38:37 +0100
From: Pavel Machek <pavel@....cz>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Ian Kent <raven@...maw.net>, Ondrej Mosnacek <omosnace@...hat.com>,
Christoph Hellwig <hch@....de>,
kernel list <linux-kernel@...r.kernel.org>,
autofs@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
the arch/x86 maintainers <x86@...nel.org>,
Peter Anvin <hpa@...or.com>
Subject: Re: autofs: use __kernel_write() for the autofs pipe writing causes
regression in -next was Re: 5.9.0-next-20201015: autofs oops in
update-binfmts
On Sat 2020-10-17 17:13:20, Linus Torvalds wrote:
> On Sat, Oct 17, 2020 at 12:48 PM Pavel Machek <pavel@....cz> wrote:
> >
> > But: you are the last one to sign it off, so I assume committed it to
> > git, and you are the one to talk to about fixing it.
>
> The thing is, the commit you point to - and the one I signed off on - is fine.
>
> The buggy one is in linux-next, which breaks that whole "NULL means no
> position" thing.
>
> IOW, the real bug is in commit 4d03e3cc5982 ("fs: don't allow kernel
> reads and writes without iter ops"), which does that bogus
>
> kiocb.ki_pos = *pos;
>
> and no, I never signed off on that.
>
> Get it? Stop confusing people. This bug does not exist in mainline,
> and never will. Because I'm not pulling that buggy commit.
And I guess that's a good thing. It is now fixed in -next, too. Sorry
for the noise.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)
Powered by blists - more mailing lists