| To: | Chandra Seetharaman <sekharan@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] security: Delay freeing inode->i_security till the end of RCU grace period |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 6 Dec 2011 10:14:29 -0500 |
| Cc: | linux-security-module@xxxxxxxxxxxxxxx, Eric Paris <eparis@xxxxxxxxxxxxxx>, XFS Mailing List <xfs@xxxxxxxxxxx> |
| In-reply-to: | <1323110541.31919.1451.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <1323110541.31919.1451.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Mon, Dec 05, 2011 at 12:42:21PM -0600, Chandra Seetharaman wrote: > while running test case 234 from xfstests test suite, I was getting an > occational memory fault in inode_has_perm() with the following stack Interesting. Given that have no good way to free other data with the normal inode callback it looks like we indeed need to do this separately. What about IMA or similar monsters? Posix ACLs already are covered at least. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfstests: check if qa user can execute commands, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH] xfstests: check if qa user can execute commands, Jan Schmidt |
| Previous by Thread: | [PATCH] security: Delay freeing inode->i_security till the end of RCU grace period, Chandra Seetharaman |
| Next by Thread: | Re: [PATCH] security: Delay freeing inode->i_security till the end of RCU grace period, Chandra Seetharaman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |