From mboxrd@z Thu Jan 1 00:00:00 1970 From: Artem Bityutskiy Subject: Re: [PATCH v2] mtd: Do not corrupt backing device of device node inode Date: Tue, 04 May 2010 17:19:17 +0300 Message-ID: <1272982757.3702.16.camel@localhost> References: <1272922368-18517-1-git-send-email-kirill@shutemov.name> <20100504111947.GB3398@quack.suse.cz> Reply-To: dedekind1@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: "Kirill A. Shutemov" , David Woodhouse , Alexander Viro , David Howells , Alexander Shishkin , linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Jan Kara Return-path: In-Reply-To: <20100504111947.GB3398@quack.suse.cz> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, 2010-05-04 at 13:19 +0200, Jan Kara wrote: > On Tue 04-05-10 00:32:48, 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). > >=20 > > Let's introduce separate inode for MTD device with appropriate back= ing > > device. > >=20 > > Signed-off-by: Kirill A. Shutemov > The patch now looks correct to me. Acked-by: Jan Kara >=20 Is this -stable material? --=20 Best Regards, Artem Bityutskiy (=D0=90=D1=80=D1=82=D1=91=D0=BC =D0=91=D0=B8=D1=82=D1=8E= =D1=86=D0=BA=D0=B8=D0=B9)