I could build 2.6.28.1 fine with Reiser4, but if I applied Ingo's patch, it would not build. I've had no issues, but haven't used Reiser4 heavily at all yet. Cheers, Teran PS: 2.6.28.2 is out. On Sun, Jan 25, 2009 at 17:44, Edward Shishkin <edward.shishkin@xxxxxxxxx> wrote: > Volker Armin Hemmann wrote: >> On Sonntag 25 Januar 2009, Edward Shishkin wrote: >> >>> Volker Armin Hemmann wrote: >>> >>>> On Montag 19 Januar 2009, Edward Shishkin wrote: >>>> >>>>> Ingo Bormuth wrote: >>>>> >>>>>> Reiser4-for-2.6.28 does apply but fails to compile on >>>>>> vanilla-2.6.28.1 due to the following commit: >>>>>> >>>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm >>>>>> it diff;h=54566b2c1594c2326a645a3551f9d989f7ba3c5e >>>>>> >>>>>> Attached is a tiny fix which works fine here. >>>>>> >>>>> yeah, with your patch it will act as earlier, >>>>> however, -mm guys decided to get rig of __GFP_FS flag: >>>>> http://userweb.kernel.org/~akpm/mmotm/broken-out/fs-symlink-write_begin- >>>>> all ocation-context-fix-reiser4-fix.patch it seems they found it >>>>> deadlocky.. >>>>> >>>> so without Ingo Bormuth's patch you can't use r4 with 2.6.28.1 >>>> >>> Ingo's patch is against -rc >>> >>> >>>> and later and >>>> with his patch there is a risk of deadlocks? >>>> >>> Not sure. >>> Nobody complained so far.. >>> >> >> hm, I had two lockups with 2.6.28 and your r4 patch so far. Suddenly the box >> only responded to sysrq > > Would you please send the sysrq-t output? > > >> - and on reboot the software raid5 with my r4 >> partitions on needed a resync. Might be related or not. I am back to 2.6.27 >> which never showed any misbehaviour. >> >> Glück Auf, >> Volker >> >> >> > > -- > To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html