On Tue, 7 Aug 2007, Serge E. Hallyn wrote: > Shall I resend without the LSM_NEED_LOCK, or do you still want a more > fundamental change? Removing the needlock is enough, the rest was just a query/suggestion. -- James Morris <jmorris@namei.org> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org 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 1/1] file capabilities: clear fcaps on inode change (v2)
- From: "Serge E. Hallyn" <serue@us.ibm.com>
- Re: [PATCH 1/1] file capabilities: clear fcaps on inode change (v2)
- References:
- [PATCH 1/1] file capabilities: clear fcaps on inode change (v2)
- From: "Serge E. Hallyn" <serue@us.ibm.com>
- Re: [PATCH 1/1] file capabilities: clear fcaps on inode change (v2)
- From: James Morris <jmorris@namei.org>
- Re: [PATCH 1/1] file capabilities: clear fcaps on inode change (v2)
- From: "Serge E. Hallyn" <serue@us.ibm.com>
- [PATCH 1/1] file capabilities: clear fcaps on inode change (v2)
- Prev by Date: Re: [PATCH 1/1] file capabilities: clear fcaps on inode change (v2)
- Next by Date: Re: [PATCH] NOMMU: Separate out VMAs
- Previous by thread: Re: [PATCH 1/1] file capabilities: clear fcaps on inode change (v2)
- Next by thread: Re: [PATCH 1/1] file capabilities: clear fcaps on inode change (v2)
- Index(es):
![]() |