public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jens Axboe <jens.axboe@oracle.com>, Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH] block: add BIG FAT WARNING to	CONFIG_DEBUG_BLOCK_EXT_DEVT
Date: Wed, 15 Oct 2008 02:31:21 +0900	[thread overview]
Message-ID: <48F4D769.9090702@kernel.org> (raw)
In-Reply-To: <20081014151526.GA30205@infradead.org>

Christoph Hellwig wrote:
> On Mon, Oct 13, 2008 at 03:41:35PM +0900, Tejun Heo wrote:
>> CONFIG_DEBUG_BLOCK_EXT_DEVT can break booting even on some modern
>> distros.  Add BIG FAT WARNING to keep people at a safe distance.
> 
> Just remove the whole "debug" code.  It clutters up all block drivers with
> ifdefs and doesn't actually provide any benefit.

Well, it's mostly intended for distros so that they can enable the
option and detect places where they assume consecutive minors as
otherwise most of those will go unnoticed until some user finally tries
to use more than 16 partitions.  As most distros are broken at the
moment, I'm more inclined to keep the debug option and planning on
enabling it during the next devel cycle of openSUSE and ask RH and other
distros to do the same.  It adds ifdefs to ide-disk and sd, which isn't
too much.  I think it would be good to keep it until at least distros
break out of the consecutive or fixed device number assumption.

Thanks.

-- 
tejun

  reply	other threads:[~2008-10-14 17:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 20:30 [bug] latest -git boot hang Ingo Molnar
2008-10-10 20:40 ` Ingo Molnar
2008-10-10 20:56   ` Ingo Molnar
2008-10-10 21:10     ` Linus Torvalds
2008-10-11  0:50       ` Tejun Heo
2008-10-11  1:42         ` H. Peter Anvin
2008-10-13  9:13           ` Tejun Heo
2008-10-13 11:07             ` [PATCH] block: add partition attribute for partition number Tejun Heo
2008-10-13 11:27               ` Jens Axboe
2008-10-11  7:11         ` [bug] latest -git boot hang Jens Axboe
2008-10-11  7:19         ` Ingo Molnar
2008-10-11 14:08           ` Jens Axboe
2008-10-11 14:33             ` Ingo Molnar
2008-10-11 14:39               ` Jens Axboe
2008-10-11 14:58                 ` Ingo Molnar
2008-10-11 17:58                   ` Jens Axboe
2008-10-13  6:41                     ` [PATCH] block: add BIG FAT WARNING to CONFIG_DEBUG_BLOCK_EXT_DEVT Tejun Heo
2008-10-13  8:46                       ` Jens Axboe
2008-10-14 15:15                       ` Christoph Hellwig
2008-10-14 17:31                         ` Tejun Heo [this message]
2008-10-14 15:07           ` [bug] latest -git boot hang Stephen Smalley
2008-10-14 15:12             ` Ingo Molnar
2008-10-14 15:24               ` Stephen Smalley
2008-10-15  1:48                 ` Casey Schaufler
2008-10-13  8:41         ` Takashi Iwai

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=48F4D769.9090702@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@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