[PATCH -rt 2/2] Make sure d_kill sets d_parent to null
From: John Stultz
Date: Wed Jun 30 2010 - 15:12:43 EST
Patch against currrent 2.6.33-rt tree.
This patch is an alternative fix to the select_parent panic that was
suggested by Nick Piggin.
It resolves the issue by making sure d_parent is set to null so that
the dentry ascending code in select_parent will restart if the child
or next dentry was dkilled while the locks were released.
Credit and thanks to Nick for finding the solution.
Signed-off-by: John Stultz <johnstul@xxxxxxxxxx>
CC: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
CC: Nick Piggin <npiggin@xxxxxxx>
CC: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
CC: John Kacur <jkacur@xxxxxxxxxx>
fs/dcache.c | 8 +++++---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/fs/dcache.c b/fs/dcache.c
index da90157..c9d21ae 100644
@@ -225,13 +225,15 @@ static struct dentry *d_kill(struct dentry *dentry)
struct dentry *parent;
- if (dentry->d_parent && dentry != dentry->d_parent)
parent = NULL;
parent = dentry->d_parent;
+ dentry->d_parent = NULL;
+ if (parent)
/*drops the locks, at that point nobody can reach this dentry */
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/