From: Richard Weinberger <richard.weinberger@gmail.com>
To: Emil Lenngren <emil.lenngren@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: mtdswap + ubi results in deadlock
Date: Tue, 15 Oct 2019 22:17:30 +0200 [thread overview]
Message-ID: <CAFLxGvzKqx9eReObd4uuo4v=G+cFepssXL36GgT17+-E6mEGRg@mail.gmail.com> (raw)
In-Reply-To: <CAO1O6sfd3YOnR_7Zm1fcX-Mz-m2pzxA1uLppb78fGxsAdfjFKw@mail.gmail.com>
On Tue, Oct 15, 2019 at 10:10 PM Emil Lenngren <emil.lenngren@gmail.com> wrote:
> Thanks for the tip, I'll try that. But just trying to find some
> information about GFP_NOFS, I found this article from 2003
> https://lwn.net/Articles/22909/. It says "The GFP_NOIO flag allows
> sleeping, but no I/O operations will be started to help satisfy the
> request. GFP_NOFS is a bit less restrictive; some I/O operations can
> be started (writing to a swap area, for example), but no filesystem
> operations will be performed.". I'm not sure how much has changed
> since 2003 but if I interpret it correctly then GFP_NOFS wouldn't work
> since that can still trigger a swap, which would result in the same
> recursive deadlock?
You are right, GFP_NOIO seems to be a better fit.
At least the block layer uses it too.
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-10-15 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 16:59 mtdswap + ubi results in deadlock Emil Lenngren
2019-10-15 18:59 ` Richard Weinberger
2019-10-15 20:10 ` Emil Lenngren
2019-10-15 20:17 ` Richard Weinberger [this message]
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='CAFLxGvzKqx9eReObd4uuo4v=G+cFepssXL36GgT17+-E6mEGRg@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=emil.lenngren@gmail.com \
--cc=linux-mtd@lists.infradead.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).