From: Christoph Hellwig <hch@infradead.org>
To: Kamal Dasu <kdasu.kdev@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
cernekee@gmail.com, xfs@oss.sgi.com
Subject: Re: Inode lockdep problem observed on 2.6.37.6 xfs with RT subvolume
Date: Thu, 2 Feb 2012 11:28:23 -0500 [thread overview]
Message-ID: <20120202162823.GA3425@infradead.org> (raw)
In-Reply-To: <CAC=U0a11udmsGAKg5Sp+X2uxRTKS8gq37CK9OAZKhLOPKbWHKQ@mail.gmail.com>
On Thu, Feb 02, 2012 at 11:26:28AM -0500, Kamal Dasu wrote:
> > ?xfs: only lock the rt bitmap inode once per allocation
> > ?xfs: fix xfs_get_extsz_hint for a zero extent size hint
> > ?xfs: add lockdep annotations for the rt inodes
> >
> > But in general the RT subvolume code is not regularly tested and only
> > fixed when issues arise.
>
>
> Thanks for quick reply and clarifying this, if upgrading the kernel is
> not an option, should I be
> considering backporting changes to 2.6.37, should I use the entire
> 2.6.39 or 3.0
> xfs implementation as is of cherry pick the above three changes ?.
I don't remember if we have other changes in that area. If backporting
the changes is easy enough, go for it, if not stick to your original
workaround. Either way make sure you don't introduce other regressions
by running xfstests.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-02 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 0:44 Inode lockdep problem observed on 2.6.37.6 xfs with RT subvolume Kamal Dasu
2012-02-02 9:13 ` Christoph Hellwig
2012-02-02 16:26 ` Kamal Dasu
2012-02-02 16:28 ` Christoph Hellwig [this message]
2012-02-10 3:27 ` kdasu
-- strict thread matches above, loose matches on Subject: below --
2012-02-02 1:02 kdasu
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=20120202162823.GA3425@infradead.org \
--to=hch@infradead.org \
--cc=cernekee@gmail.com \
--cc=kdasu.kdev@gmail.com \
--cc=xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox