Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values

On Thu, Jan 04, 2007 at 11:09:31AM -0800, Linus Torvalds wrote:
 
> But I'd argue we should only do it if there is an actual 
> honest-to-goodness reason to do so.

How about "makes call graph analysis easier"? ;-)  In principle, I have
no problem with force-casting, but it'd better be cast to the right
type...

(And yes, there's a bunch of sparse-based fun in making dealing with
call graph analysis and sane annotations needed for that).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
    • From: Linus Torvalds <[email protected]>
  • Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
    • From: Al Viro <[email protected]>

• References:
  • [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
    • From: Eric Sandeen <[email protected]>
  • Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
    • From: Andrew Morton <[email protected]>
  • Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
    • From: Eric Sandeen <[email protected]>
  • Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
    • From: Andrew Morton <[email protected]>
  • Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
    • From: Eric Sandeen <[email protected]>
  • Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
    • From: Andrew Morton <[email protected]>
  • Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
    • From: Linus Torvalds <[email protected]>

• Prev by Date: RE: open(O_DIRECT) on a tmpfs?
• Next by Date: Re: Regression in kernel linux-2.6.20-rc1/2: Problems with poweroff
• Previous by thread: Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
• Next by thread: Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]