| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <200910011125.40081.bzolnier@gmail.com> Date: Thu, 1 Oct 2009 11:25:40 +0200 From: Bartlomiej Zolnierkiewicz <bzolnier@...il.com> To: David Miller <davem@...emloft.net> Cc: elendil@...net.nl, manty@...ty.net, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org Subject: Re: kernel BUG at drivers/ide/ide-disk.c:187 (2.6.31) On Thursday 01 October 2009 10:30:30 David Miller wrote: > From: Frans Pop <elendil@...net.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. The problem is that you simply cannot know what is the system state here. Thus when the unknown block layer request is encountered the best thing you can do is to BUG early instead of allowing the situation when some requests are silently dropped and possibly causing the data corruption. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists