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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



phillip@xxxxxxxxxxxxxxxxxxx wrote:
> Hmm, the problem with this is it bloats bad_inode.o with lots of empty
> functions that return -EIO.  Even though we're not interested in the
> parameters, GCC doesn't know this, and doesn't fold the functions into only
> the couple of definitions that return different types.
> 

After posting this, I saw the discussion on the LKML.  I was only about 12 hours late, as usual...

Phillip


-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux