All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ian Kent <raven@themaw.net>,
	Ondrej Mosnacek <omosnace@redhat.com>,
	Christoph Hellwig <hch@lst.de>,
	kernel list <linux-kernel@vger.kernel.org>,
	autofs@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	the arch/x86 maintainers <x86@kernel.org>,
	Peter Anvin <hpa@zytor.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
Date: Sat, 17 Oct 2020 21:47:58 +0200	[thread overview]
Message-ID: <20201017194758.GA9904@duo.ucw.cz> (raw)
In-Reply-To: <CAHk-=whFVYJabpFsSRL-t7PjDfisvNU=kUMPQUh=SDtLtT587w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 861 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2020-10-17 19:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 12:35 5.9.0-next-20201015: autofs oops in update-binfmts Pavel Machek
2020-10-17  2:11 ` Ian Kent
2020-10-17 10:02   ` autofs: use __kernel_write() for the autofs pipe writing causes regression in -next was " Pavel Machek
2020-10-17 18:05     ` Linus Torvalds
2020-10-17 19:47       ` Pavel Machek [this message]
2020-10-18  0:13         ` Linus Torvalds
2020-10-26  8:38           ` Pavel Machek
2020-10-18  7:22       ` Christoph Hellwig

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=20201017194758.GA9904@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=autofs@vger.kernel.org \
    --cc=bp@alien8.de \
    --cc=hch@lst.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=omosnace@redhat.com \
    --cc=raven@themaw.net \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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.