* [PATCH] exportfs: do not read dentry after free
@ 2018-11-23 3:15 Pan Bian
2018-11-23 5:58 ` Amir Goldstein
0 siblings, 1 reply; 3+ messages in thread
From: Pan Bian @ 2018-11-23 3:15 UTC (permalink / raw)
To: Amir Goldstein, Miklos Szeredi, linux-kernel; +Cc: Pan Bian
The function dentry_connected calls dput(dentry) to drop the previously
acquired reference to dentry. In this case, dentry can be released.
After that, IS_ROOT(dentry) checks the condition
(dentry == dentry->d_parent), which may result in a use-after-free bug.
This patch directly compares dentry with its parent obtained before
dropping the reference.
Fixes: a056cc8934c("exportfs: stop retrying once we race with
rename/remove")
Signed-off-by: Pan Bian <bianpan2016@163.com>
---
fs/exportfs/expfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/exportfs/expfs.c b/fs/exportfs/expfs.c
index 645158d..a69aaf5 100644
--- a/fs/exportfs/expfs.c
+++ b/fs/exportfs/expfs.c
@@ -77,7 +77,7 @@ static bool dentry_connected(struct dentry *dentry)
struct dentry *parent = dget_parent(dentry);
dput(dentry);
- if (IS_ROOT(dentry)) {
+ if (dentry == parent) { /* is root entry */
dput(parent);
return false;
}
--
2.7.4
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] exportfs: do not read dentry after free
2018-11-23 3:15 [PATCH] exportfs: do not read dentry after free Pan Bian
@ 2018-11-23 5:58 ` Amir Goldstein
2018-11-23 7:41 ` PanBian
0 siblings, 1 reply; 3+ messages in thread
From: Amir Goldstein @ 2018-11-23 5:58 UTC (permalink / raw)
To: bianpan2016
Cc: Miklos Szeredi, linux-kernel, Al Viro, J. Bruce Fields,
Christoph Hellwig
On Fri, Nov 23, 2018 at 5:16 AM Pan Bian <bianpan2016@163.com> wrote:
>
> The function dentry_connected calls dput(dentry) to drop the previously
> acquired reference to dentry. In this case, dentry can be released.
> After that, IS_ROOT(dentry) checks the condition
> (dentry == dentry->d_parent), which may result in a use-after-free bug.
> This patch directly compares dentry with its parent obtained before
> dropping the reference.
>
> Fixes: a056cc8934c("exportfs: stop retrying once we race with
> rename/remove")
>
CC Fixes patch author/reviewers
How did you find this? by code review or did this actually happen?
Normally a IS_ROOT dentry would be either DCACHE_DISCONNECTED or
pinned to some super block, but I guess there may be corner cases?
> Signed-off-by: Pan Bian <bianpan2016@163.com>
> ---
> fs/exportfs/expfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/exportfs/expfs.c b/fs/exportfs/expfs.c
> index 645158d..a69aaf5 100644
> --- a/fs/exportfs/expfs.c
> +++ b/fs/exportfs/expfs.c
> @@ -77,7 +77,7 @@ static bool dentry_connected(struct dentry *dentry)
> struct dentry *parent = dget_parent(dentry);
>
> dput(dentry);
> - if (IS_ROOT(dentry)) {
> + if (dentry == parent) { /* is root entry */
> dput(parent);
> return false;
> }
The change itself looks right, but the name IS_ROOT is confusing
enough as it is. The explicit comment is just plain wrong.
If it was really a root dentry, it wouldn't have been DCACHE_DISCONNECTED
(unless it is a filesystem bug).
Thanks,
Amir.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] exportfs: do not read dentry after free
2018-11-23 5:58 ` Amir Goldstein
@ 2018-11-23 7:41 ` PanBian
0 siblings, 0 replies; 3+ messages in thread
From: PanBian @ 2018-11-23 7:41 UTC (permalink / raw)
To: Amir Goldstein
Cc: Miklos Szeredi, linux-kernel, Al Viro, J. Bruce Fields,
Christoph Hellwig
On Fri, Nov 23, 2018 at 07:58:15AM +0200, Amir Goldstein wrote:
> On Fri, Nov 23, 2018 at 5:16 AM Pan Bian <bianpan2016@163.com> wrote:
> >
> > The function dentry_connected calls dput(dentry) to drop the previously
> > acquired reference to dentry. In this case, dentry can be released.
> > After that, IS_ROOT(dentry) checks the condition
> > (dentry == dentry->d_parent), which may result in a use-after-free bug.
> > This patch directly compares dentry with its parent obtained before
> > dropping the reference.
> >
> > Fixes: a056cc8934c("exportfs: stop retrying once we race with
> > rename/remove")
> >
>
> CC Fixes patch author/reviewers
>
> How did you find this? by code review or did this actually happen?
>
> Normally a IS_ROOT dentry would be either DCACHE_DISCONNECTED or
> pinned to some super block, but I guess there may be corner cases?
I found this by code review, and I have not yet observed crash.
>
> > Signed-off-by: Pan Bian <bianpan2016@163.com>
> > ---
> > fs/exportfs/expfs.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/exportfs/expfs.c b/fs/exportfs/expfs.c
> > index 645158d..a69aaf5 100644
> > --- a/fs/exportfs/expfs.c
> > +++ b/fs/exportfs/expfs.c
> > @@ -77,7 +77,7 @@ static bool dentry_connected(struct dentry *dentry)
> > struct dentry *parent = dget_parent(dentry);
> >
> > dput(dentry);
> > - if (IS_ROOT(dentry)) {
> > + if (dentry == parent) { /* is root entry */
> > dput(parent);
> > return false;
> > }
>
> The change itself looks right, but the name IS_ROOT is confusing
> enough as it is. The explicit comment is just plain wrong.
> If it was really a root dentry, it wouldn't have been DCACHE_DISCONNECTED
> (unless it is a filesystem bug).
I will remove the comment and resubmit the patch.
Thanks a lot,
Pan
>
> Thanks,
> Amir.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-11-23 7:42 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-23 3:15 [PATCH] exportfs: do not read dentry after free Pan Bian
2018-11-23 5:58 ` Amir Goldstein
2018-11-23 7:41 ` PanBian
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.