From: David Chinner <dgc@sgi.com>
To: Christoph Hellwig <hch@infradead.org>,
David Chinner <dgc@sgi.com>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 2.6.20 (XFS? related) crash after uptime of > 180 days during apt-get dist-upgrade on Debian Testing
Date: Tue, 18 Sep 2007 20:39:16 +1000 [thread overview]
Message-ID: <20070918103916.GV23367404@sgi.com> (raw)
In-Reply-To: <20070918092013.GA1352@infradead.org>
On Tue, Sep 18, 2007 at 10:20:13AM +0100, Christoph Hellwig wrote:
> On Tue, Sep 18, 2007 at 11:45:37AM +1000, David Chinner wrote:
> > No idea - it looks like dkpg was trying to remove a directory on the
> > same path the lookup was and both have gone splat in __d_lookup on
> > the same dentry. Something happened in those 180 days that left a
> > landmine that was tripped over here, I think. I can't see any way of
> > tracking it down from this, but thanks for reporting it anyway,
>
> This looks a lot like the i_sem leak that Vlad debugged. Do you remember
> where this was fixed?
The i_sem leak was hitting us on sles9 - 2.6.5 base kernel - and it was fixed
before the i_sem -> i_mutex conversion in mainline. Some time around 2.6.16,
IIRC. Given this was a 2.6.20 kernel, there'd be an almighty kaboom if that
bug still existed after the i_mutex conversion....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-09-18 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 17:20 2.6.20 (XFS? related) crash after uptime of > 180 days during apt-get dist-upgrade on Debian Testing Justin Piszcz
2007-09-18 1:45 ` David Chinner
2007-09-18 9:20 ` Christoph Hellwig
2007-09-18 10:39 ` David Chinner [this message]
2007-09-18 11:09 ` Christoph Hellwig
2007-09-19 8:47 ` Justin Piszcz
2007-09-21 0:15 ` David Chinner
2007-09-21 8:48 ` Justin Piszcz
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=20070918103916.GV23367404@sgi.com \
--to=dgc@sgi.com \
--cc=hch@infradead.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--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