linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Pavel Machek <pavel@ucw.cz>
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 11:05:06 -0700	[thread overview]
Message-ID: <CAHk-=whFVYJabpFsSRL-t7PjDfisvNU=kUMPQUh=SDtLtT587w@mail.gmail.com> (raw)
In-Reply-To: <20201017100234.GA3797@amd>

On Sat, Oct 17, 2020 at 3:02 AM Pavel Machek <pavel@ucw.cz> wrote:
>
> Bad Linus!

Christ people.

The bug is in linux-next, not in mainline.  I've told the people
involved already over a week ago.

I can't do anything about linux-next being broken and people not fixing it.

              Linus

  reply	other threads:[~2020-10-17 18:05 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 [this message]
2020-10-17 19:47       ` Pavel Machek
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='CAHk-=whFVYJabpFsSRL-t7PjDfisvNU=kUMPQUh=SDtLtT587w@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --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=pavel@ucw.cz \
    --cc=raven@themaw.net \
    --cc=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).