From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-kernel@lists.codethink.co.uk,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org
Subject: RFC: fixup for mtdblock issue with erase warnings
Date: Wed, 26 Apr 2017 18:46:08 +0100 [thread overview]
Message-ID: <20170426174609.29433-1-ben.dooks@codethink.co.uk> (raw)
We have been running into a warning from __might_sleep() in the cfi erase
code. We think this is due to the mtdblock driver trying to sleep when an
operation is going to complete from the _erase callback.
If this patch is acceptable, it should probably go into stable as well as
the current release.
Note, currently being tested on v4.4.y
next reply other threads:[~2017-04-26 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 17:46 Ben Dooks [this message]
2017-04-26 17:46 ` [PATCH 1/1] mtd: mtdblock: avoid __might_sleep warnings in mtd_erase Ben Dooks
2017-04-26 18:18 ` [Linux-kernel] " Ben Hutchings
2017-04-27 8:27 ` Ben Dooks
2017-04-27 12:04 ` Ben Hutchings
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=20170426174609.29433-1-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@lists.codethink.co.uk \
--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