On Wed, Jul 28, 2010 at 19:20 +0200, Andi Kleen wrote: > > >I'm agree with you that if allocation fails at boot time, we are dead :) > >But this coding style breaking rules that result from some functions > >_must_ be checked for errors. Maybe we should add BUG_ON() here or > >indicate someway that we have no ideas how to handle error? > > What rules exactly? I don't think any of those functions are > declared with __must_check IMO memmory allocation fails are dangerous in kernel mode. As it is probably not exploitable because of boot time, it can destroy some sensitive data like dirty disk caches those are going to be written on disk. > > Coding style should never get in the way of what is right. > > The classic way to explicitely discard a return value is a cast to > void, but that is generally considered > ugly in the Linux kernel. > > One could possibly add a comment about this at least. > > -Andi > -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
