Re: invalidate_inode_buffers call in invalidate_list?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Oct 18, 2010 at 12:11:50PM +1100, Dave Chinner wrote:
> > While we're
> > at it - any reaso not to consider I_NEW inodes as busy in
> > invalidate_list?
> 
> Not that I can think of. I'd probably leave the WARN_ON() condition
> there, though, so that if we do ever encounter them we hear about
> it...

The WARN_ON is already unreachable - we check for I_NEW a couple
of lines above and never drop it until after we reach the WARN_ON.

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


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux