lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 17 May 2017 00:20:14 +0200 From: Richard Weinberger <richard@....at> To: dedekind1@...il.com, linux-mtd@...ts.infradead.org Cc: linux-kernel@...r.kernel.org, adrian.hunter@...el.com, stable@...r.kernel.org Subject: Re: [PATCH] ubifs: Fix inode leak in xattr code Artem, Am 15.05.2017 um 18:05 schrieb Artem Bityutskiy: > 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. That turned out to be much easier than expected. Patch ahead! Thanks, //richard
Powered by blists - more mailing lists