iput() in reclaim context

From: Hugh Dickins
Date: Wed May 21 2008 - 13:54:05 EST

On Tue, 20 May 2008, Andrew Morton wrote:
> On Wed, 21 May 2008 10:15:32 +0400 Evgeniy Polyakov <johnpol@xxxxxxxxxxx> wrote:
> > On Tue, May 20, 2008 at 04:28:16PM -0700, Andrew Morton (akpm@xxxxxxxxxxxxxxxxxxxx) 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.)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/