From: Matthew Wilcox <willy@infradead.org>
To: Pradeep P V K <ppvk@codeaurora.org>
Cc: miklos@szeredi.hu, linux-fsdevel@vger.kernel.org,
stummala@codeaurora.org, sayalil@codeaurora.org
Subject: Re: [PATCH V3] fuse: Remove __GFP_FS flag to avoid allocator recursing
Date: Wed, 23 Sep 2020 13:49:14 +0100 [thread overview]
Message-ID: <20200923124914.GO32101@casper.infradead.org> (raw)
In-Reply-To: <1600840675-43691-1-git-send-email-ppvk@codeaurora.org>
On Wed, Sep 23, 2020 at 11:27:55AM +0530, Pradeep P V K wrote:
> Changes since V2:
> - updated memalloc_nofs_save() to allocation paths that potentially
> can cause deadlock.
That's the exact opposite of what I said to do. Again, the *THREAD*
is the thing which must not block, not the *ALLOCATION*. So you
set this flag *ON THE THREAD*, not *WHEN IT DOES AN ALLOCATION*.
If that's not clear, please ask again.
next prev parent reply other threads:[~2020-09-23 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 5:57 [PATCH V3] fuse: Remove __GFP_FS flag to avoid allocator recursing Pradeep P V K
2020-09-23 12:49 ` Matthew Wilcox [this message]
2020-09-24 14:56 ` ppvk
2020-10-08 6:03 ` ppvk
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=20200923124914.GO32101@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=ppvk@codeaurora.org \
--cc=sayalil@codeaurora.org \
--cc=stummala@codeaurora.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;
as well as URLs for NNTP newsgroup(s).