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

Stephen Rothwell wrote: > Hi Eric, > > On Wed, 03 Jan 2007 12:42:47 -0600 Eric Sandeen <[EMAIL PROTECTED]> wrote: >> So here's the first stab at fixing it. I'm sure there are style points >> to be hashed out. Putting all the functions as static inlines in a header >> was just to avoid hundreds

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

Hi Eric, On Wed, 03 Jan 2007 12:42:47 -0600 Eric Sandeen <[EMAIL PROTECTED]> wrote: > > So here's the first stab at fixing it. I'm sure there are style points > to be hashed out. Putting all the functions as static inlines in a header > was just to avoid hundreds of lines of simple function

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

Hi Eric, On Wed, 03 Jan 2007 12:42:47 -0600 Eric Sandeen [EMAIL PROTECTED] wrote: So here's the first stab at fixing it. I'm sure there are style points to be hashed out. Putting all the functions as static inlines in a header was just to avoid hundreds of lines of simple function

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

Stephen Rothwell wrote: Hi Eric, On Wed, 03 Jan 2007 12:42:47 -0600 Eric Sandeen [EMAIL PROTECTED] wrote: So here's the first stab at fixing it. I'm sure there are style points to be hashed out. Putting all the functions as static inlines in a header was just to avoid hundreds of lines of