From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <1494864339.18055.20.camel@gmail.com> Subject: Re: [PATCH] ubifs: Fix inode leak in xattr code From: Artem Bityutskiy Reply-To: dedekind1@gmail.com To: Richard Weinberger , linux-mtd@lists.infradead.org Cc: linux-kernel@vger.kernel.org, adrian.hunter@intel.com, stable@vger.kernel.org Date: Mon, 15 May 2017 19:05:39 +0300 In-Reply-To: References: <1494858005-18439-1-git-send-email-richard@nod.at> <1494860034.18055.17.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On Mon, 2017-05-15 at 17:22 +0200, Richard Weinberger wrote: > Alternatively we could add a iget_locked/drop_nlink/iput sequence to > ubifs_tnc_remove_ino(). But that will make unlink() much slower for > files > that contain xattrs. At that level we'd need to do it for every xattr, even those that were never be accessed, which would be slow indeed. But we really only need to check the inode cache: hey, icache, I am dying, and if you have any of my guys (xattrs), I want them to die with me. So the question is how to find our guys in the inode cache. I am not sure. Probably be we'd have to have our own list of cached inodes in the host inode, and maintain it. Artem.