| 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <Pine.LNX.4.64.0805211840200.13797@blonde.site> Date: Wed, 21 May 2008 18:52:27 +0100 (BST) From: Hugh Dickins <hugh@...itas.com> To: Andrew Morton <akpm@...ux-foundation.org> cc: Evgeniy Polyakov <johnpol@....mipt.ru>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: iput() in reclaim context On Tue, 20 May 2008, Andrew Morton wrote: > On Wed, 21 May 2008 10:15:32 +0400 Evgeniy Polyakov <johnpol@....mipt.ru> wrote: > > On Tue, May 20, 2008 at 04:28:16PM -0700, Andrew Morton (akpm@...ux-foundation.org) wrote: > > > It's more than efficiency. There are lots and lots of things we cannot > > > do in direct-reclaim context. > > > > > > ... > > > > > > c) Cannot run iput(). Or at least, we couldn't five or six years > > > ago. afaik nobody has investigated whether the situation is now > > > better or worse. I happened to notice your remark in the buffer heads defrag thread. Do you remember what that limitation was about? Because just a few months ago I discovered a shmem race which I fixed by doing igrab+iput in shmem_writepage, in the reclaim context. Feeling guilty now: I'd better investigate, but would welcome a starting pointer. (If I'm lucky, it'll be that the generic code in vmscan.c cannot use iput, but particular filesystems might themselves be safe to.) Thanks, Hugh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists