public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Christoph Hellwig <hch@infradead.org>,
	Theodore Tso <tytso@MIT.EDU>, Mark Fasheh <mfasheh@suse.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH] jbd2: Create proc entry with bdevname+i_ino.
Date: Mon, 15 Sep 2008 10:42:30 -0400	[thread overview]
Message-ID: <20080915144230.GA21089@infradead.org> (raw)
In-Reply-To: <20080915011042.GA29193@mail.oracle.com>

On Sun, Sep 14, 2008 at 06:10:42PM -0700, Joel Becker wrote:
> Christoph,
> 	Not sure what you mean here.  Do you mean switching over
> wholesale without the JBD compat config option?  We're currently
> tracking a spinlock deadlock in JBD2, so I don't know if we're ready for
> that.
> 	If you don't get this, I'll try to track you down tomorrow.

Sorry, not related to jbd2 in ocfs2, but the bdevname bits in this
thread.  I saw Ted posted another patch later that basically does the
same for the journal dev as the VFS does for sb->s_id so this is okay.
I still think we should do the / substitution in get_sb_bdev, too and
will send a separate patch for it.


  reply	other threads:[~2008-09-15 14:42 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
2008-09-15  1:10       ` Joel Becker
2008-09-15 14:42         ` Christoph Hellwig [this message]
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=20080915144230.GA21089@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mfasheh@suse.com \
    --cc=ocfs2-devel@oss.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