public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	reiserfs-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.30-rc: reiserfs_delete_xattrs log spam (bug 13122)
Date: Sat, 09 May 2009 10:10:05 -0400	[thread overview]
Message-ID: <4A058EBD.8030302@suse.com> (raw)
In-Reply-To: <20090509130152.GD8633@ZenIV.linux.org.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Al Viro wrote:
> On Sat, May 09, 2009 at 02:44:25PM +0200, Stefan Richter wrote:
>> On  9 May, Stefan Richter wrote:
>>> I just switched from 2.6.29.1 to 2.6.30-rc5, and I'm getting the same as 
>>> the reporter of http://bugzilla.kernel.org/show_bug.cgi?id=13122 alias
>>> http://marc.info/?l=linux-kernel&m=123990989515105, i.e. repetitions of
>>>  >>>
>>> May  9 14:27:22 stein REISERFS warning (device sda1): jdm-20004 
>>> reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
>>> May  9 14:27:22 stein
>>> <<<
>>>
>>> This happens in irregular intervals, but a lot of times --- presumably 
>>> when certain files are accessed.  I'm on a recently set-up Gentoo 
>>> machine.  I created its root filesystem using the Gentoo x86-64 minimal 
>>> boot CD; my guess is that the kernel of the boot CD had 
>>> CONFIG_REISERFS_FS_XATTR enabled.  All kernels which I used since then 
>>> have it disabled:  2.6.27-gentoo-r8, 2.6.29.1, now 2.6.30-rc5.
>> PS:  Also, the following came up at this (= first) boot of 2.6.30-rc, as
>> a warm reboot from 2.6.29.1. I have no idea whether it's connected to
>> the issue.
> 
> That WARN_ON() is fixed in the patches in VFS queue; should be gone in
> -next and I'm going to push a bunch of fixes to Linus today, this one
> among them.
> 
> The first one you've reported is a different story.  Could you try to
> bisect it?

I'm looking into this right now. I have an idea, but I haven't been able
to reproduce it yet to test.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkoFjr0ACgkQLPWxlyuTD7LiowCgpZPFraYS+c7Y38LtNcVJaHiH
kMwAoIN8X7g37TyLs/7VskKScS+cap7G
=A7Xx
-----END PGP SIGNATURE-----

  reply	other threads:[~2009-05-09 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-09 12:38 2.6.30-rc: reiserfs_delete_xattrs log spam (bug 13122) Stefan Richter
2009-05-09 12:44 ` Stefan Richter
2009-05-09 13:01   ` Al Viro
2009-05-09 14:10     ` Jeff Mahoney [this message]
2009-05-09 15:21       ` Stefan Richter
2009-05-09 15:39     ` Jeff Mahoney

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=4A058EBD.8030302@suse.com \
    --to=jeffm@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=viro@ZenIV.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox