From: bfields@fieldses.org (J. Bruce Fields)
To: Andrew Elble <aweits@rit.edu>
Cc: linux-nfs@vger.kernel.org, etmsys@rit.edu,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] NFS: fix BUG() crash in notify_change() with patch to chown_common()
Date: Mon, 23 Feb 2015 15:54:35 -0500 [thread overview]
Message-ID: <20150223205435.GA28635@fieldses.org> (raw)
In-Reply-To: <1424699484-74025-1-git-send-email-aweits@rit.edu>
Looks OK to me. I think it would go through Al.--b.
Acked-by: J. Bruce Fields <bfields@redhat.com>
On Mon, Feb 23, 2015 at 08:51:24AM -0500, Andrew Elble wrote:
> We have observed a BUG() crash in fs/attr.c:notify_change(). The crash
> occurs during an rsync into a filesystem that is exported via NFS.
>
> 1.) fs/attr.c:notify_change() modifies the caller's version of attr.
> 2.) 6de0ec00ba8d ("VFS: make notify_change pass ATTR_KILL_S*ID to
> setattr operations") introduced a BUG() restriction such that "no
> function will ever call notify_change() with both ATTR_MODE and
> ATTR_KILL_S*ID set". Under some circumstances though, it will have
> assisted in setting the caller's version of attr to this very
> combination.
> 3.) 27ac0ffeac80 ("locks: break delegations on any attribute
> modification") introduced code to handle breaking
> delegations. This can result in notify_change() being re-called. attr
> _must_ be explicitly reset to avoid triggering the BUG() established
> in #2.
> 4.) The path that that triggers this is via fs/open.c:chmod_common().
> The combination of attr flags set here and in the first call to
> notify_change() along with a later failed break_deleg_wait()
> results in notify_change() being called again via retry_deleg
> without resetting attr.
>
> Solution is to move retry_deleg in chmod_common() a bit further up to
> ensure attr is completely reset.
>
> There are other places where this seemingly could occur, such as
> fs/utimes.c:utimes_common(), but the attr flags are not initially
> set in such a way to trigger this.
>
> Fixes: 27ac0ffeac80 ("locks: break delegations on any attribute modification")
> Reported-by: Eric Meddaugh <etmsys@rit.edu>
> Tested-by: Eric Meddaugh <etmsys@rit.edu>
> Signed-off-by: Andrew Elble <aweits@rit.edu>
> ---
> fs/open.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/open.c b/fs/open.c
> index 33f9cbf2610b..44a3be145bfe 100644
> --- a/fs/open.c
> +++ b/fs/open.c
> @@ -570,6 +570,7 @@ static int chown_common(struct path *path, uid_t user, gid_t group)
> uid = make_kuid(current_user_ns(), user);
> gid = make_kgid(current_user_ns(), group);
>
> +retry_deleg:
> newattrs.ia_valid = ATTR_CTIME;
> if (user != (uid_t) -1) {
> if (!uid_valid(uid))
> @@ -586,7 +587,6 @@ static int chown_common(struct path *path, uid_t user, gid_t group)
> if (!S_ISDIR(inode->i_mode))
> newattrs.ia_valid |=
> ATTR_KILL_SUID | ATTR_KILL_SGID | ATTR_KILL_PRIV;
> -retry_deleg:
> mutex_lock(&inode->i_mutex);
> error = security_path_chown(path, uid, gid);
> if (!error)
> --
> 1.9.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org (J. Bruce Fields)
To: Andrew Elble <aweits-H6Ufl4FQnQQ@public.gmane.org>
Cc: linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
etmsys-H6Ufl4FQnQQ@public.gmane.org,
Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] NFS: fix BUG() crash in notify_change() with patch to chown_common()
Date: Mon, 23 Feb 2015 15:54:35 -0500 [thread overview]
Message-ID: <20150223205435.GA28635@fieldses.org> (raw)
In-Reply-To: <1424699484-74025-1-git-send-email-aweits-H6Ufl4FQnQQ@public.gmane.org>
Looks OK to me. I think it would go through Al.--b.
Acked-by: J. Bruce Fields <bfields-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Mon, Feb 23, 2015 at 08:51:24AM -0500, Andrew Elble wrote:
> We have observed a BUG() crash in fs/attr.c:notify_change(). The crash
> occurs during an rsync into a filesystem that is exported via NFS.
>
> 1.) fs/attr.c:notify_change() modifies the caller's version of attr.
> 2.) 6de0ec00ba8d ("VFS: make notify_change pass ATTR_KILL_S*ID to
> setattr operations") introduced a BUG() restriction such that "no
> function will ever call notify_change() with both ATTR_MODE and
> ATTR_KILL_S*ID set". Under some circumstances though, it will have
> assisted in setting the caller's version of attr to this very
> combination.
> 3.) 27ac0ffeac80 ("locks: break delegations on any attribute
> modification") introduced code to handle breaking
> delegations. This can result in notify_change() being re-called. attr
> _must_ be explicitly reset to avoid triggering the BUG() established
> in #2.
> 4.) The path that that triggers this is via fs/open.c:chmod_common().
> The combination of attr flags set here and in the first call to
> notify_change() along with a later failed break_deleg_wait()
> results in notify_change() being called again via retry_deleg
> without resetting attr.
>
> Solution is to move retry_deleg in chmod_common() a bit further up to
> ensure attr is completely reset.
>
> There are other places where this seemingly could occur, such as
> fs/utimes.c:utimes_common(), but the attr flags are not initially
> set in such a way to trigger this.
>
> Fixes: 27ac0ffeac80 ("locks: break delegations on any attribute modification")
> Reported-by: Eric Meddaugh <etmsys-H6Ufl4FQnQQ@public.gmane.org>
> Tested-by: Eric Meddaugh <etmsys-H6Ufl4FQnQQ@public.gmane.org>
> Signed-off-by: Andrew Elble <aweits-H6Ufl4FQnQQ@public.gmane.org>
> ---
> fs/open.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/open.c b/fs/open.c
> index 33f9cbf2610b..44a3be145bfe 100644
> --- a/fs/open.c
> +++ b/fs/open.c
> @@ -570,6 +570,7 @@ static int chown_common(struct path *path, uid_t user, gid_t group)
> uid = make_kuid(current_user_ns(), user);
> gid = make_kgid(current_user_ns(), group);
>
> +retry_deleg:
> newattrs.ia_valid = ATTR_CTIME;
> if (user != (uid_t) -1) {
> if (!uid_valid(uid))
> @@ -586,7 +587,6 @@ static int chown_common(struct path *path, uid_t user, gid_t group)
> if (!S_ISDIR(inode->i_mode))
> newattrs.ia_valid |=
> ATTR_KILL_SUID | ATTR_KILL_SGID | ATTR_KILL_PRIV;
> -retry_deleg:
> mutex_lock(&inode->i_mutex);
> error = security_path_chown(path, uid, gid);
> if (!error)
> --
> 1.9.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-23 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 13:51 [PATCH] NFS: fix BUG() crash in notify_change() with patch to chown_common() Andrew Elble
2015-02-23 20:54 ` J. Bruce Fields [this message]
2015-02-23 20:54 ` J. Bruce Fields
2015-03-20 14:28 ` Andrew W Elble
2015-03-20 14:28 ` Andrew W Elble
2015-03-20 14:50 ` J. Bruce Fields
2015-03-20 14:53 ` Al Viro
2015-03-20 14:53 ` Al Viro
2015-03-20 14:54 ` J. Bruce Fields
2015-03-20 15:13 ` Andrew W Elble
-- strict thread matches above, loose matches on Subject: below --
2015-03-04 16:41 Andrew Elble
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150223205435.GA28635@fieldses.org \
--to=bfields@fieldses.org \
--cc=aweits@rit.edu \
--cc=etmsys@rit.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.