Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race

>>>>> Eric Sandeen (ES) writes:

 ES> so I think it's possible that link can sneak in there & find it after
 ES> the mutex is dropped...?  Is this ok? :)  It's certainly -happening-
 ES> anyway....

yes, but it shouldn't allow to re-link such inode back, IMHO.
a filesystem may start some non-revertable activity in its
unlink method.

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/

Follow-Ups:
- Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race
  - From: Eric Sandeen <[email protected]>

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]>

Prev by Date: Re: High lock spin time for zone->lru_lock under extreme conditions
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):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]