lkml.org 
[lkml]   [2003]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] Altix I/O code cleanup
From
Date
>>>>> "Christoph" == Christoph Hellwig <hch@infradead.org> writes:

Christoph> Of course - but that's not that point. You have to handle
Christoph> an out of memory situtation propery because it may happen
Christoph> all the time - you should not panic at all. The
Christoph> ASSERT_ALWAYS just confuses automatic checker tools that
Christoph> help to find such conditions.

Again,

From a purely theoretical standpoint as I don't remember the code in
question's situation, this again depends on where in the codepath you
hit this. If you don't get your memory for certain key data structures
early on, there's really very little you can do but panic().

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

\
 
 \ /
  Last update: 2005-03-22 13:58    [W:0.742 / U:25.556 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site