On Sat, Oct 17, 2020 at 12:48 PM Pavel Machek <pavel@xxxxxx> 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.
The commit you talk about IS NOT THE BUGGY ONE.
Linus
