From: Christoph Hellwig <hch@infradead.org>
To: Mark Goodwin <markgw@sgi.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs leaking?
Date: Mon, 14 Jul 2008 00:13:03 -0400 [thread overview]
Message-ID: <20080714041303.GA5040@infradead.org> (raw)
In-Reply-To: <487AD102.9020306@sgi.com>
On Mon, Jul 14, 2008 at 02:07:30PM +1000, Mark Goodwin wrote:
>
>
> Eric Sandeen wrote:
>>
>> 2.6.26-rc9 passed without incident.
>
> So what is the conclusion here? Because you just down-rev? Or do we have
> an intermittent leak of some kind?
The symptoms in the first post look like an inode leak, which is more
likely to be in common code than in XFS. I'd expect -rc9 just fixed it
or Eric didn't manage to hit it as easily.
next prev parent reply other threads:[~2008-07-14 4:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 17:04 xfs leaking? Eric Sandeen
2008-07-11 23:38 ` Dave Chinner
2008-07-12 0:35 ` Eric Sandeen
2008-07-12 2:02 ` Eric Sandeen
2008-07-14 4:07 ` Mark Goodwin
2008-07-14 4:13 ` Christoph Hellwig [this message]
2008-07-14 4:15 ` Eric Sandeen
2008-07-12 1:31 ` Eric Sandeen
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=20080714041303.GA5040@infradead.org \
--to=hch@infradead.org \
--cc=markgw@sgi.com \
--cc=sandeen@sandeen.net \
--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