From: Christoph Hellwig <hch@infradead.org>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Mark Fasheh <mfasheh@suse.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
ocfs2-devel@oss.oracle.com, sunil.mushran@oracle.com
Subject: Re: [PATCH] jbd2: Create proc entry with bdevname+i_ino.
Date: Sun, 14 Sep 2008 12:06:35 -0400 [thread overview]
Message-ID: <20080914160635.GA31958@infradead.org> (raw)
In-Reply-To: <20080914090306.GF30537@mit.edu>
On Sun, Sep 14, 2008 at 05:03:06AM -0400, Theodore Tso wrote:
> On Sun, Sep 14, 2008 at 01:40:03AM -0700, Mark Fasheh wrote:
> > On Mon, Sep 08, 2008 at 04:31:14PM -0700, Joel Becker wrote:
> > > jbd2 currently creates statistics files for each loaded journal in
> > > /proc/fs/jbd2/<bdevname>. ocfs2 loads multiple journals when recovering
> > > other nodes, and the multiple journals on a given bdev collide in the
> > > proc namespace.
> >
> > Did this patch ever get reviewied? We'd really like it in so that Ocfs2 can
> > use JBD2...
>
> Thanks for pinging me; it fell through the cracks. I'll make sure it
> gets put into the queue for merging at the next merge window....
Could you please do it the proper way as describe in my reply to the
thread?
next prev parent reply other threads:[~2008-09-14 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 23:31 [PATCH] jbd2: Create proc entry with bdevname+i_ino Joel Becker
2008-09-14 8:40 ` Mark Fasheh
2008-09-14 9:03 ` Theodore Tso
2008-09-14 14:51 ` Mark Fasheh
2008-09-14 16:06 ` Christoph Hellwig [this message]
2008-09-15 1:10 ` Joel Becker
2008-09-15 14:42 ` [Ocfs2-devel] " Christoph Hellwig
2008-09-14 16:31 ` Theodore Tso
2008-09-15 1:19 ` [Ocfs2-devel] " Joel Becker
2008-09-15 17:50 ` Sunil Mushran
2008-09-16 18:01 ` [Ocfs2-devel] " Sunil Mushran
2008-09-20 3:14 ` Jan Kara
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=20080914160635.GA31958@infradead.org \
--to=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=sunil.mushran@oracle.com \
--cc=tytso@MIT.EDU \
/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