All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: elendil@planet.nl
Cc: manty@manty.net, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	bzolnier@gmail.com
Subject: Re: kernel BUG at drivers/ide/ide-disk.c:187 (2.6.31)
Date: Thu, 01 Oct 2009 01:30:30 -0700 (PDT)	[thread overview]
Message-ID: <20091001.013030.98262804.davem@davemloft.net> (raw)
In-Reply-To: <200910011026.17510.elendil@planet.nl>

From: Frans Pop <elendil@planet.nl>
Date: Thu, 1 Oct 2009 10:26:14 +0200

> Question for IDE maintainers: should maybe the old printing of request info 
> be reinstated, or can the request flags also be obtained from the BUG 
> info?

Using a BUG for this doesn't make it any easier to track down the
problem.  WARN_ON_ONCE() or similar is much more appropriate here.

BUG() is for situations where the system's state is completely
irrecoverably corrupted, and we cannot continue, and that is not the
case here at all.

  reply	other threads:[~2009-10-01  8:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 11:05 kernel BUG at drivers/ide/ide-disk.c:187 (2.6.31) Santiago Garcia Mantinan
2009-10-01  6:57 ` Andrew Morton
2009-10-01  8:26   ` Frans Pop
2009-10-01  8:30     ` David Miller [this message]
2009-10-01  9:25       ` Bartlomiej Zolnierkiewicz
2009-10-01 16:40         ` David Miller
2009-10-01 18:21           ` Bartlomiej Zolnierkiewicz
2009-10-01 18:34             ` David Miller
2009-10-01 18:52               ` Bartlomiej Zolnierkiewicz
2009-10-01 10:11     ` Santiago Garcia Mantinan
2009-10-01 18:47 ` David Miller
2009-10-01 18:53   ` David Miller
2009-10-03  3:39     ` Santiago Garcia Mantinan
2009-10-04 22:37       ` Santiago Garcia Mantinan
2009-10-05  0:19         ` David Miller

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=20091001.013030.98262804.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=bzolnier@gmail.com \
    --cc=elendil@planet.nl \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manty@manty.net \
    /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.