lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 26 Oct 2020 09:38:37 +0100
From:   Pavel Machek <>
To:     Linus Torvalds <>
Cc:     Ian Kent <>, Ondrej Mosnacek <>,
        Christoph Hellwig <>,
        kernel list <>,, Thomas Gleixner <>,
        Ingo Molnar <>, Borislav Petkov <>,
        the arch/x86 maintainers <>,
        Peter Anvin <>
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

On Sat 2020-10-17 17:13:20, Linus Torvalds wrote:
> On Sat, Oct 17, 2020 at 12:48 PM Pavel Machek <> 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,


Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)

Powered by blists - more mailing lists