| To: | NeilBrown <neilb@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 17/19] VFS: set PF_FSTRANS while namespace_sem is held. |
| From: | Al Viro <viro@xxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 16 Apr 2014 17:37:41 +0100 |
| Cc: | linux-mm@xxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20140416155230.4d02e4b9@xxxxxxxxxxxxxx> |
| References: | <20140416033623.10604.69237.stgit@xxxxxxxxxxxxxx> <20140416040337.10604.86740.stgit@xxxxxxxxxxxxxx> <20140416044618.GX18016@xxxxxxxxxxxxxxxxxx> <20140416155230.4d02e4b9@xxxxxxxxxxxxxx> |
| Sender: | Al Viro <viro@xxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Wed, Apr 16, 2014 at 03:52:30PM +1000, NeilBrown wrote: > So something like this? I put that in to my testing instead. Something like this, yes... And TBH I would prefer the same approach elsewhere - this kind of hidden state makes it hard to do any kind of analysis. Put it that way - the simplest situation is when the allocation flags depend only on the call site. Next one is when it's a function of call chain - somewhat harder to review. And the worst is when it's a function of previous history of execution - not just the call chain, but the things that had been called (and returned) prior to that one. How many of those locations need to be of the third kind? All fs/namespace.c ones are of the first one... |
| Previous by Date: | new 64 bit math link fail in xfs in linux-next today, Paul Gortmaker |
|---|---|
| Next by Date: | Re: [PATCH v2 1/2] xfs: fix tmpfile/selinux deadlock and initialize security/acl, Andreas Gruenbacher |
| Previous by Thread: | Re: [PATCH 17/19] VFS: set PF_FSTRANS while namespace_sem is held., NeilBrown |
| Next by Thread: | [PATCH 18/19] nfsd: set PF_FSTRANS during nfsd4_do_callback_rpc., NeilBrown |
| Indexes: | [Date] [Thread] [Top] [All Lists] |