From: Nikolay Borisov <nborisov@suse.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: use nofs context when initializing security xattrs to avoid deadlock
Date: Tue, 11 Dec 2018 10:00:11 +0200 [thread overview]
Message-ID: <9e40b76c-8dde-84bb-bba3-e2789e31320c@suse.com> (raw)
In-Reply-To: <20181210175335.15906-1-fdmanana@kernel.org>
On 10.12.18 г. 19:53 ч., fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> When initializing the security xattrs, we are holding a transaction handle
> therefore we need to use a GFP_NOFS context in order to avoid a deadlock
> with reclaim in case it's triggered.
>
> Fixes: 39a27ec1004e8 ("btrfs: use GFP_KERNEL for xattr and acl allocations")
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
> fs/btrfs/xattr.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/fs/btrfs/xattr.c b/fs/btrfs/xattr.c
> index ea78c3d6dcfc..f141b45ce349 100644
> --- a/fs/btrfs/xattr.c
> +++ b/fs/btrfs/xattr.c
> @@ -11,6 +11,7 @@
> #include <linux/security.h>
> #include <linux/posix_acl_xattr.h>
> #include <linux/iversion.h>
> +#include <linux/sched/mm.h>
> #include "ctree.h"
> #include "btrfs_inode.h"
> #include "transaction.h"
> @@ -422,9 +423,15 @@ static int btrfs_initxattrs(struct inode *inode,
> {
> const struct xattr *xattr;
> struct btrfs_trans_handle *trans = fs_info;
> + unsigned int nofs_flag;
> char *name;
> int err = 0;
>
> + /*
> + * We're holding a transaction handle, so use a NOFS memory allocation
> + * context to avoid deadlock if reclaim happens.
> + */
> + nofs_flag = memalloc_nofs_save();
> for (xattr = xattr_array; xattr->name != NULL; xattr++) {
> name = kmalloc(XATTR_SECURITY_PREFIX_LEN +
> strlen(xattr->name) + 1, GFP_KERNEL);
> @@ -440,6 +447,7 @@ static int btrfs_initxattrs(struct inode *inode,
> if (err < 0)
> break;
> }
> + memalloc_nofs_restore(nofs_flag);
> return err;
> }
>
>
next prev parent reply other threads:[~2018-12-11 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 17:53 [PATCH] Btrfs: use nofs context when initializing security xattrs to avoid deadlock fdmanana
2018-12-11 8:00 ` Nikolay Borisov [this message]
2018-12-12 13:15 ` David Sterba
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=9e40b76c-8dde-84bb-bba3-e2789e31320c@suse.com \
--to=nborisov@suse.com \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox