From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: David Woodhouse <dwmw2@infradead.org>, Jan Kara <jack@suse.cz>,
Alexander Viro <viro@zeniv.linux.org.uk>,
David Howells <dhowells@redhat.com>,
Alexander Shishkin <virtuoso@slind.org>,
linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org,
stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] mtd: Do not corrupt backing device of device node inode
Date: Thu, 06 May 2010 09:39:19 +0300 [thread overview]
Message-ID: <1273127959.3702.200.camel@localhost> (raw)
In-Reply-To: <1273074054-11849-1-git-send-email-kirill@shutemov.name>
On Wed, 2010-05-05 at 18:40 +0300, Kirill A. Shutemov wrote:
> We cannot modify file->f_mapping->backing_dev_info, because it will corrupt
> backing device of device node inode, since file->f_mapping is equal to
> inode->i_mapping (see __dentry_open() in fs/open.c).
>
> Let's introduce separate inode for MTD device with appropriate backing
> device.
>
> Signed-off-by: Kirill A. Shutemov <kirill@shutemov.name>
> ---
> Changelog:
> v3 -> v4:
> - Use igrab() instead of __iget inside the inode_lock;
> - Add stable@ to CC list.
> v2 -> v3:
> - Rebase to mtd-2.6.git.
> v1 -> v2:
> - Fix error handling based on comments by Jan Kara.
Pushed to l2-mtd-2.6.git / dunno
Also added Jan's ack which disappeared in v4
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-05-06 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 15:40 [PATCH v4] mtd: Do not corrupt backing device of device node inode Kirill A. Shutemov
2010-05-06 6:39 ` Artem Bityutskiy [this message]
2010-05-14 1:04 ` David Woodhouse
2010-05-17 13:19 ` Kirill A. Shutemov
2010-05-17 21:56 ` 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=1273127959.3702.200.camel@localhost \
--to=dedekind1@gmail.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jack@suse.cz \
--cc=kirill@shutemov.name \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=stable@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=virtuoso@slind.org \
/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;
as well as URLs for NNTP newsgroup(s).