Bill Davidsen <[email protected]> wrote: > mount /base on point1 - rw [ hopefully really r/w ] > mount /base on point2 - ro [ hopefully r/o ] I think Al Viro probably has the right idea as to how to fix this: Move the R/O R/W flag into vfsmount and count the number of R/W vfsmounts in the superblock. I never quite finished implementing the patch to do this, but I can go back and revisit it. David - 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: recent nfs change causes autofs regression
- From: David Howells <[email protected]>
- Re: recent nfs change causes autofs regression
- From: David Howells <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Ian Kent <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Bill Davidsen <[email protected]>
- Re: recent nfs change causes autofs regression
- References:
- Re: recent nfs change causes autofs regression
- From: Bill Davidsen <[email protected]>
- recent nfs change causes autofs regression
- From: "Hua Zhong" <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Trond Myklebust <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Linus Torvalds <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Trond Myklebust <[email protected]>
- Re: recent nfs change causes autofs regression
- Prev by Date: Re: recent nfs change causes autofs regression
- Next by Date: Re: recent nfs change causes autofs regression
- Previous by thread: Re: recent nfs change causes autofs regression
- Next by thread: Re: recent nfs change causes autofs regression
- Index(es):
 |