[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201017194758.GA9904@duo.ucw.cz>
Date: Sat, 17 Oct 2020 21:47:58 +0200
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
Hi!
> > Bad Linus!
>
> Christ people.
https://www.christpeople.church/ ? Those are unlikely to help, I'd say :-).
> The bug is in linux-next, not in mainline. I've told the people
> involved already over a week ago.
Yes, I reported the bug against -next.
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.
> I can't do anything about linux-next being broken and people not
> fixing it.
90fb702791bf99b959006972e8ee7bb4609f441b causes oops at boot for me.
So... I'm not git wizard, but... if I do log on v5.8, it is not in the
list, and if I do log on v5.9, it shows it.
So yes, I believe this in mainline.
Should I test v5.9 next? Or do you want me to test some patch?
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