linux-kernel - Re: [PATCH 5/9] writeback: introduce the pageout work

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120302095910.GB1744@quack.suse.cz>
Date:	Fri, 2 Mar 2012 10:59:10 +0100
From:	Jan Kara <jack@...e.cz>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Jan Kara <jack@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>,
	Greg Thelen <gthelen@...gle.com>,
	Ying Han <yinghan@...gle.com>,
	"hannes@...xchg.org" <hannes@...xchg.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Rik van Riel <riel@...hat.com>, Mel Gorman <mgorman@...e.de>,
	Minchan Kim <minchan.kim@...il.com>,
	Linux Memory Management List <linux-mm@...ck.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 5/9] writeback: introduce the pageout work

On Fri 02-03-12 12:48:58, Wu Fengguang wrote:
> On Thu, Mar 01, 2012 at 05:38:37PM +0100, Jan Kara wrote:
> > On Thu 01-03-12 20:36:40, Wu Fengguang wrote:
> > > > Please have a think about all of this and see if you can demonstrate
> > > > how the iput() here is guaranteed safe.
> > > 
> > > There are already several __iget()/iput() calls inside fs-writeback.c.
> > > The existing iput() calls already demonstrate its safety?
> > > 
> > > Basically the flusher works in this way
> > > 
> > > - the dirty inode list i_wb_list does not reference count the inode at all
> > > 
> > > - the flusher thread does something analog to igrab() and set I_SYNC
> > >   before going off to writeout the inode
> > > 
> > > - evict() will wait for completion of I_SYNC
> >   Yes, you are right that currently writeback code already holds inode
> > references and so it can happen that flusher thread drops the last inode
> > reference. But currently that could create problems only if someone waits
> > for flusher thread to make progress while effectively blocking e.g.
> > truncate from happening. Currently flusher thread handles sync(2) and
> > background writeback and filesystems take care to not hold any locks
> > blocking IO / truncate while possibly waiting for these.
> > 
> > But with your addition situation changes significantly - now anyone doing
> > allocation can block and do allocation from all sorts of places including
> > ones where we hold locks blocking other fs activity. The good news is that
> > we use GFP_NOFS in such places. So if GFP_NOFS allocation cannot possibly
> > depend on a completion of some writeback work, then I'd still be
> > comfortable with dropping inode references from writeback code. But Andrew
> > is right this at least needs some arguing...
> 
> You seem to miss the point that we don't do wait or page allocations
> inside queue_pageout_work().
  I didn't miss this point. I know we don't wait directly. But if the only
way to free pages from the zone where we need to do allocation is via flusher
thread, then we effectively *are* waiting for the work to complete. And if
the flusher thread is blocked, we have a problem. And I agree it's unlikely
but given enough time and people, I believe someone finds a way to
(inadvertedly) trigger this.

> The final iput() will not block the
> random tasks because the latter don't wait for completion of the work.
> 
>         random task                     flusher thread
> 
>         page allocation
>           page reclaim
>             queue_pageout_work()
>               igrab()
> 
>                   ......  after a while  ......
> 
>                                         execute pageout work                
>                                         iput()
>                                         <work completed>
> 
> There will be some reclaim_wait()s if the pageout works are not
> executed quickly, in which case vmscan will be impacted and slowed
> down. However it's not waiting for any specific work to complete, so
> there is no chance to form a loop of dependencies leading to deadlocks.
> 
> The iput() does have the theoretic possibility to deadlock the flusher
> thread itself (but not with the other random tasks). Since the flusher
> thread has always been doing iput() w/o running into such bugs, we can
> reasonably expect the new iput() to be as safe in practical.
  But so far, kswapd could do writeout itself so even if flusher thread is
blocked in iput(), we could still do writeout from kswapd to clean zones.

Now I don't think blocking on iput() can be a problem because of reasons I
outlined in another email yesterday (GFP_NOFS allocations and such). Just
I don't agree with your reasoning that it cannot be a problem because it
was not problem previously. That's just not true.

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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/