[email protected] napisał(a):
> The mm snapshot broken-out-2007-04-11-02-24.tar.gz has been uploaded to
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-04-11-02-24.tar.gz
>
> It contains the following patches against 2.6.21-rc6:
>
After a few seconds of running test_mount_fs.sh
http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/broken-out-2007-04-11-02-24/test_mount_fs.sh
I get this
[11083.747512] Filesystem "loop4": Disabling barriers, not supported by the underlying device
[11083.759050] XFS mounting filesystem loop4
[11083.763769] Slab corruption: xfs_buf start=cce14938, len=272
[11083.769986] Redzone: 0x5a2cf071/0x5a2cf071.
[11083.774575] Last user: [<fddaacde>](xfs_buf_free+0x77/0x7b [xfs])
[11083.781146] 0b0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6c 6b 6b 6b
[11083.787988] Prev obj: start=cce1481c, len=272
[11083.792488] Redzone: 0x5a2cf071/0x5a2cf071.
[11083.796828] Last user: [<fddaacde>](xfs_buf_free+0x77/0x7b [xfs])
[11083.803131] 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
[11083.810392] 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
[11083.817677] Next obj: start=cce14a54, len=272
[11083.822146] Redzone: 0x5a2cf071/0x5a2cf071.
[11083.826415] Last user: [<fddaacde>](xfs_buf_free+0x77/0x7b [xfs])
[11083.832784] 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
[11083.839403] 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
[11083.852797] Ending clean XFS mount for filesystem: loop4
[11083.865789] SELinux: initialized (dev loop4, type xfs), uses xattr
http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/broken-out-2007-04-11-02-24/serialconsole.log
http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/broken-out-2007-04-11-02-24/mm-config
BTW. I wonder when this bug will be fixed
[11050.534896] =============================================
[11050.541883] [ INFO: possible recursive locking detected ]
[11050.547425] 2.6.21-rc6-mm1-1 #1
[11050.550630] ---------------------------------------------
[11050.556142] umount/3359 is trying to acquire lock:
[11050.561060] (&(&ip->i_lock)->mr_lock){----}, at: [<fdd8729a>] xfs_ilock+0x4d/0x6e [xfs]
[11050.569565]
[11050.569567] but task is already holding lock:
[11050.575487] (&(&ip->i_lock)->mr_lock){----}, at: [<fdd8729a>] xfs_ilock+0x4d/0x6e [xfs]
Otherwise, for me it's another stable kernel
boot - ok
aio_dio_bugs - ok
aiostress - ok
bash_shared_mapping - ok
cat_proc - ok
cat_sys - ok
cpu_hotplug - ok
cyclictest - ok
fio - ok
fsfuzzer - ok
fsx - ok
isic - ok
linus_stress - ok
ltp - ok
rmaptest - ok
rttester - ok
scrashme - ok
spew - ok
stress - ok
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group (PL)
(http://www.stardust.webpages.pl/ltg/)
LTG - Linux Testers Group (EN)
(http://www.stardust.webpages.pl/linux_testers_group_en/)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
