LKML Archive on
 help / color / Atom feed
From: Sasha Levin <>
To: Linus Torvalds <>
Cc: Thomas Gleixner <>,
	Chris Wilson <>,
	Linux List Kernel Mailing <>,
	Bandan Das <>
Subject: Re: Linux 5.3-rc7
Date: Sun, 8 Sep 2019 07:02:53 -0400
Message-ID: <20190908110253.GC2012@sasha-vm> (raw)
In-Reply-To: <>

On Sat, Sep 07, 2019 at 02:13:22PM -0700, Linus Torvalds wrote:
>On Sat, Sep 7, 2019 at 1:44 PM Thomas Gleixner <> wrote:
>> That's what I just replied to Chris. Can you do it right away or should I queue it up?

I'd like to bring back a discussion we had last year on ksummit-discuss:
. I've pointed out that some of the commits that go in the -rc cycles
are of low quality and are untested, you seemed to agree but said that
it's "by-design" because late -rc cycle commits are more complex.

Is this commit and it's fallout really how our development process
should be working?

This commit was rushed through the process: it was authored and merged
into -tip of the same day, and pulled in by you just a few days later.
There was no meaningful time for review, testing, or really any sort of

We really do have a better story now for catching the sort of issues
introduced by these patch: multiple CI systems tripped on this, but
people still need the time to look into it, make sure that the failure
is real and bisect it.

What was the rush in making it skip all of our safeguards? The "bug" has
been there forever, the fix isn't urgent, and no one seemed to care for
quite a while.

Even if this patch was fixing a bug introduced in this merge window, is
the tradeoff around rushing an untested fix worth it vs giving it more
time and shipping it as part of our stable tree?

I'm not trying to pick on this patch in particular - I feel that this is
a systematic issue and should be addressed as part of our process.


      reply index

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02 17:28 Linus Torvalds
2019-09-07 10:10 ` Chris Wilson
2019-09-07 14:29   ` Thomas Gleixner
2019-09-07 14:41     ` Chris Wilson
2019-09-07 15:00       ` Thomas Gleixner
2019-09-07 15:24         ` Chris Wilson
2019-09-07 20:12           ` Thomas Gleixner
2019-09-07 19:17         ` Linus Torvalds
2019-09-07 19:27           ` Linus Torvalds
2019-09-09 13:54             ` Bandan Das
2019-09-07 20:44           ` Thomas Gleixner
2019-09-07 21:13             ` Linus Torvalds
2019-09-08 11:02               ` Sasha Levin [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190908110253.GC2012@sasha-vm \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

LKML Archive on

Archives are clonable:
	git clone --mirror lkml/git/0.git
	git clone --mirror lkml/git/1.git
	git clone --mirror lkml/git/2.git
	git clone --mirror lkml/git/3.git
	git clone --mirror lkml/git/4.git
	git clone --mirror lkml/git/5.git
	git clone --mirror lkml/git/6.git
	git clone --mirror lkml/git/7.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ \
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone