Re: kernel BUG at drivers/ide/ide-disk.c:187 (2.6.31)

On Thursday 01 October 2009 18:40:34 David Miller wrote:
From: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
Date: Thu, 1 Oct 2009 11:25:40 +0200

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.

Yes, but if you BUG() in this kind of location, the chance of getting
the debugging information from the user can be close to zero. We were
very lucky this time :-)

Do you mean that there is higher chance of user noticing some WARN_ON
warning somewhere in the log than OOPS? I don't quite believe it..

If we're tossing a request, signal an error to the submitter.

I hear we have infrastructure for that :-)

It has its own problems (see blk_execute_rq() overriding error values
for one of many examples)..

Anyway this is completely besides the point here (however please don't
let it stop you from fixing the aforementioned infrastructure) until
the whole issue gets debugged properly and I'd be quite happy to do it
under normal circumstances but since:

- you are always jumping the gun with your strong opinions before people
even had chance to debug the issue properly and find real root causes
(vide infamous sparc cmd64x problems, which were caused by the real
bugfixes and were completely fixed within 48h from the initial report)

- for the last three months you haven't debugged/fixed a single IDE issue
and you keep dodging every single bug-report

- I have neither time nor interest for this kind of silly corporate-style
games (I had some really good laugh few times though :)

- I really do not have to work on IDE (never had, it was always a hobby)

- I'm not the maintainer any longer :)

I simply do not even want to be cc:ed on IDE problems unless it is a paid
job or mail comes from the person who in the past proved the ability to
work well with others.

Thank you for understanding.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: slurping in binary data
    ... You seem to doubt you have a bug. ... console window in Windows), so there's no problem using printfto ... My own most fundamental rule for debugging programs is ... with a series of premises assumed to ...
    (comp.lang.c)
  • Re: Lebans Continuous Forms Sample Problem
    ... Subclassing/VB IDE bug. ... If you have had or currently opened the VB IDE ... >> Access Code, Tips and Tricks ...
    (microsoft.public.access.formscoding)
  • Re: Unhandled Exception in Form Load in EXE but not in IDE
    ... IDE by the normal Try-Catch syntax are not caught in an EXE unless the JIT ... If this is by design then it is a silly design but I ... So the answer to your last question about whether or not it's a bug in IDE ...
    (microsoft.public.dotnet.languages.vb)
  • Re: IDE changing file subtype from Form to Code???
    ... Not sure it that is a bug or if it is fixed, but for what is worth, the list ... > Our development team has a problem where the IDE will automatically change ... > the code type in the .csproj files from one type to another, ...
    (microsoft.public.vsnet.ide)
  • Re: Ctrl+Y invokes Delete Current Line instead of Redo...
    ... It should be a bug. ... I'm not trying to start a flame war here, but my goodness you complain ... Visual Basic .Net is not C++ and the VB 2005 ide is not the ide ... so either adjust to the new language/ide (or ...
    (microsoft.public.dotnet.languages.vb)