On Fri, 2007-04-20 at 10:10 -0400, Theodore Tso wrote: > On Fri, Apr 20, 2007 at 06:35:41PM +0530, Kalpak Shah wrote: > > > > I saw this problem when I was running a script which created a random > > number of EAs for a file of random sizes. If you mount the image I have > > given, all the EAs are displayed and they can be used/modified/deleted > > without any problems so its not a bug in ext3 code. > > Not a bug in the ext3 code, but if a RHEL5 or SLES 10 or Debian etch > user uses EA-in-Inode, with SELinux enabled, and then uses the e2fsck > shipped with their distro, some of the unsorted EA's would get > deleted.... right? Yes thats what I meant, it is certainly not a bug in ext3. And actually the effects are worse, _all_ the EAs in the inode get deleted. I think not many people have been using > 128 byte inodes and hence this problem might not have cropped up until now. Thanks, Kalpak Shah. <kalpak@xxxxxxxxxxxxx> > > If that's correct, then that's a pretty nasty data corruption problem > (that with SELinux enabled could cause the system to become completely > non-functional, further contributing to SELinux's bad reputation...) > and we'll need to push your patch to the various distro's as a > relatively high priority bug fix. > > - Ted - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
