linux-kernel - Re: [PATCH 13/18] fs: split locking of inode writeback and LRU lists

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: <20101008080018.GV4681@dastard>
Date:	Fri, 8 Oct 2010 19:00:18 +1100
From:	Dave Chinner <david@...morbit.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 13/18] fs: split locking of inode writeback and LRU
 lists

On Fri, Oct 08, 2010 at 03:42:43AM -0400, Christoph Hellwig wrote:
> On Fri, Oct 08, 2010 at 04:21:27PM +1100, Dave Chinner wrote:
> > From: Dave Chinner <dchinner@...hat.com>
> > 
> > Now that the inode LRU and IO lists are split apart, we can separate
> > the locking for them. The IO lists are only ever accessed in the
> > context of writeback, so a per-BDI lock for those lists separates
> > them out nicely.
> 
> I think this description needs some updates.  It seems like it's from
> Nick's original patch that splits the lock, but at this point we still
> have inode_lock anyway.

Ok, will do.

> > -static inline struct backing_dev_info *inode_to_bdi(struct inode *inode)
> > -{
> > -	struct super_block *sb = inode->i_sb;
> > -
> > -	if (strcmp(sb->s_type->name, "bdev") == 0)
> > -		return inode->i_mapping->a_bdi;
> > -
> > -	return sb->s_bdi;
> > -}
> 
> Please don't extent the scope of this one.  Just add a new inode_wb_del
> or similar helper to remove and inode from the writeback list.

OK, will do.

> > @@ -484,7 +483,7 @@ static int writeback_sb_inodes(struct super_block *sb, struct bdi_writeback *wb,
> >  			return 0;
> >  		}
> >  
> > -		if (inode->i_state & (I_NEW | I_WILL_FREE)) {
> > +		if (inode->i_state & (I_NEW | I_WILL_FREE | I_FREEING)) {
> >  			requeue_io(inode);
> >  			continue;
> >  		}
> 
> What does this have to do with the rest of the patch?

That's because there's now a window between setting I_FREEING and taking
the inode off the writeback list which means that we can see inodes
in that state here. Generally it means that the code setting
I_FREEING is spinning waiting for the wb->b_lock that this thread
currently holds so it can be removed from the list.. Hence the requeue
to move the inode out of the way and keep processing inodes for
writeback.


> > @@ -495,8 +494,11 @@ static int writeback_sb_inodes(struct super_block *sb, struct bdi_writeback *wb,
> >  		if (inode_dirtied_after(inode, wbc->wb_start))
> >  			return 1;
> >  
> > -		BUG_ON(inode->i_state & I_FREEING);
> > +		spin_lock(&inode->i_lock);
> >  		iref_locked(inode);
> > +		spin_unlock(&inode->i_lock);
> 
> Shouldn't this become a plain iref now?

No, because we're holding the inode_lock here. And later, the lock
get moved to protect the i_state fields as well, so it would end up
this way, anyway.

> > +/*
> > + * check against I_FREEING as inode writeback completion could race with
> > + * setting the I_FREEING and removing the inode from the LRU.
> > + */
> > +void inode_lru_list_add(struct inode *inode)
> > +{
> > +	spin_lock(&inode_lru_lock);
> > +	if (list_empty(&inode->i_lru) && !(inode->i_state & I_FREEING)) {
> > +		list_add(&inode->i_lru, &inode_lru);
> > +		percpu_counter_inc(&nr_inodes_unused);
> > +	}
> > +	spin_unlock(&inode_lru_lock);
> > +}
> 
> Ah, here you introduce the lru list helpers I suggested earlier.  Moving
> them earlier in the series probably is a good idea to avoid exporting
> nr_inodes_unused, even if the locking for the helpers will change in
> this patch.

I'll see what I can do.

Cheers,

Dave.
-- 
Dave Chinner
david@...morbit.com
--
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/