mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Mike Snitzer <snizer@redhat.com>,
	James Bottomley <James.Bottomley@suse.de>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [Regression] Please revert a91a2785b20
Date: Tue, 29 Mar 2011 01:03:17 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1103290049330.2774@localhost6.localdomain6> (raw)
In-Reply-To: <yq1hbamkgoe.fsf@sermon.lab.mkp.net>

On Mon, 28 Mar 2011, Martin K. Petersen wrote:
> >>>>> "Thomas" == Thomas Gleixner <tglx@linutronix.de> writes:
> 
> Thomas,
> 
> Thomas> But the changelog does not give the courtesy of explaining these
> Thomas> changes. Also there is no fcking reason why the kernel cannot
> Thomas> deal with the missing integrity capabilities of a drive just by
> Thomas> emitting a warning msg and dealing gracefully with the outcome.
> 
> My mistake. I was made aware of it earlier today and I'm working on a

Why didn't you send a revert to Linus right away?

Darn. I sent a pull request earlier today, which I immediately
revoked, when I noticed that it had a late reported testing
failure. It did not hit Linus public tree fortunately. I could have
said "I'm working on a fix" as well. But that's the wrong thing to do.

So for your thing, it was already in Linus tree. Though if you get
aware of it and it's revertable w/o creating lots of mess, then it's
the right thing to revert it immediately. Do not drag out regressions
longer than necessary, please.

> Surprised we didn't see any reports of this in -next. It's been
> in there for a while.

next does unfortunately get not the full exposure and it's neither a
replacement for common sense nor an excuse for not testing the common
case (i.e. non enterprise hardware with default distro configs)

Thanks,

	tglx

  reply	other threads:[~2011-03-28 23:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 22:35 Thomas Gleixner
2011-03-28 22:43 ` Thomas Gleixner
2011-03-28 23:03   ` Mike Snitzer
2011-03-29  6:59     ` Jens Axboe
2011-03-29 13:20       ` Mike Snitzer
2011-03-29 13:35         ` James Bottomley
2011-03-29 13:42         ` Martin K. Petersen
2011-03-29 13:58           ` Need to refactor DM's integrity profile support a bit (was: Re: Please revert a91a2785b20) Mike Snitzer
2011-04-01 17:42             ` [PATCH] dm: improve block integrity support Mike Snitzer
2011-04-14 14:09               ` Mike Snitzer
2011-04-14 14:42                 ` Mike Snitzer
2011-04-15  4:57                   ` Martin K. Petersen
2011-04-05  2:09           ` Please revert a91a2785b20 NeilBrown
2011-03-28 22:45 ` [Regression] " Martin K. Petersen
2011-03-28 23:03   ` Thomas Gleixner [this message]
2011-03-29  0:09     ` Martin K. Petersen
2011-03-29  0:11       ` Martin K. Petersen
2011-03-29  2:32       ` Thomas Gleixner
2011-03-29  5:32       ` Giacomo Catenazzi

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=alpine.LFD.2.00.1103290049330.2774@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=James.Bottomley@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=snizer@redhat.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®