That's the one; this bug could potentially cause inode table or
corruption of block groups, causing data loss. It could *potentially*
show up on single processor systems, if CONFIG_PREMPT is defined, but
in practice it's unlikely for UP systems to hit the race.
On Fri, Jun 19, 2009 at 04:49:19PM -0000, Derek wrote: kernel. org/pub/ scm/linux/ kernel/ git/tytso/ ext4.git for-stable-2.6.28 git.kernel. org/?p= linux/kernel/ git/tytso/ ext4.git; a=shortlog; h=for-stable- 2.6.28 git.kernel. org/?p= linux/kernel/ git/tytso/ ext4.git; a=commitdiff; h=16cb5dd9f53e5 69130584696909d 423b6fe38c1e
> > git://git.
> > http://
> >
> > (This is where it's handy to have a file system specialist working at
> > the distribution; when I found the problem, I was able to contact Eric
> > and he made sure the patch was quickly dropped into the F11 kernel.)
>
> Is this:
> http://
>
> 'cause the machines I was getting lockups on were single core.
That's the one; this bug could potentially cause inode table or
corruption of block groups, causing data loss. It could *potentially*
show up on single processor systems, if CONFIG_PREMPT is defined, but
in practice it's unlikely for UP systems to hit the race.