All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: xfs-masters@oss.sgi.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm snapshot broken-out-2007-04-11-02-24.tar.gz uploaded
Date: Wed, 11 Apr 2007 20:03:17 +0200	[thread overview]
Message-ID: <461D22E5.9030705@googlemail.com> (raw)
In-Reply-To: <200704110926.l3B9Qe3D000895@shell0.pdx.osdl.net>

akpm@linux-foundation.org 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/)

  reply	other threads:[~2007-04-11 18:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11  9:26 mm snapshot broken-out-2007-04-11-02-24.tar.gz uploaded akpm
2007-04-11 18:03 ` Michal Piotrowski [this message]
2007-04-11 19:15   ` Andrew Morton
2007-04-11 22:14     ` Michal Piotrowski
2007-04-11 22:42       ` Andrew Morton
2007-04-16  1:59         ` [xfs-masters] " David Chinner
2007-04-16 12:51           ` Michal Piotrowski
2007-04-17  5:50           ` Timothy Shimmin
  -- strict thread matches above, loose matches on Subject: below --
2007-04-11  9:26 akpm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=461D22E5.9030705@googlemail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs-masters@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.