From: Jan Kara <jack@suse.cz>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Benny Halevy <bhalevy@panasas.com>
Subject: Re: [RFC] vfs/inode: For none-block-based filesystems default to sb->s_bdi
Date: Tue, 5 Oct 2010 10:32:08 +0200 [thread overview]
Message-ID: <20101005083208.GA3514@quack.suse.cz> (raw)
In-Reply-To: <4CAA4EE5.2070308@panasas.com>
Hi Boaz,
On Mon 04-10-10 18:02:13, Boaz Harrosh wrote:
> Sorry I've just seen Jan's patch:
> From: Jan Kara <jack@suse.cz>
> Date: Mon, 27 Sep 2010 23:56:48 +0200
> Subject: [PATCH] bdi: Initialize inode->i_mapping.backing_dev_info to sb->s_bdi
...
> That works for me as well. Was it decided how to solve this? Other wise
> I'll need to patch exofs, ASAP for this -rc
In the end, we'll use Christoph's patch
(http://lkml.org/lkml/2010/9/29/76) changing inode_to_bdi() to be
more conservative and also the warning will be gone. So you don't have to
patch anything...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2010-10-05 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 21:46 [RFC] vfs/inode: For none-block-based filesystems default to sb->s_bdi Boaz Harrosh
2010-10-04 22:02 ` Boaz Harrosh
2010-10-05 8:32 ` Jan Kara [this message]
2010-10-05 13:53 ` Boaz Harrosh
2010-10-05 13:54 ` Boaz Harrosh
2010-10-05 15:12 ` Jan Kara
2010-10-05 15:09 ` Jan Kara
2010-10-05 15:29 ` Boaz Harrosh
2010-10-05 15:50 ` Jan Kara
2010-10-06 8:55 ` Christoph Hellwig
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=20101005083208.GA3514@quack.suse.cz \
--to=jack@suse.cz \
--cc=Trond.Myklebust@netapp.com \
--cc=bhalevy@panasas.com \
--cc=bharrosh@panasas.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.