>>>>> Eric Sandeen (ES) writes: ES> Al says "no" and I'm not arguing. :) ES> Apparently this may be OK with some filesystems, and Al says he doesn't ES> want to know about i_nlink in the vfs in any case. well, generic_drop_inode() uses i_nlink ... ES> But I suppose there may be other filesystems which DO care, and should ES> be checking if they're not. this is why I thought VFS could take care. thanks, Alex - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race
- From: Eric Sandeen <[email protected]>
- Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race
- From: Alex Tomas <[email protected]>
- Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race
- From: Eric Sandeen <[email protected]>
- Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race
- From: Alex Tomas <[email protected]>
- Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race
- From: Eric Sandeen <[email protected]>
- Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race
- From: Alex Tomas <[email protected]>
- Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race
- From: Eric Sandeen <[email protected]>
- [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race
- Prev by Date: Re: SATA hotplug from the user side ?
- Next by Date: Re: 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1)
- Previous by thread: Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race
- Next by thread: Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race
- Index(es):