From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Stefan Bigler <stefan.bigler@keymile.com>,
linux-mtd@lists.infradead.org,
Michael Cashwell <mboards@prograde.net>
Subject: Re: [PATCH] mtd: fix race in cfi_cmdset_0001 driver
Date: Fri, 11 Feb 2011 16:50:54 +0200 [thread overview]
Message-ID: <1297435854.2760.43.camel@localhost> (raw)
In-Reply-To: <OFB4CE4BA6.2B710A36-ONC1257834.0050DBAB-C1257834.00512172@transmode.se>
On Fri, 2011-02-11 at 15:46 +0100, Joakim Tjernlund wrote:
> Artem Bityutskiy <dedekind1@gmail.com> wrote on 2011/02/11 15:02:16:
> >
> > On Mon, 2011-02-07 at 17:07 +0100, Joakim Tjernlund wrote:
> > > As inval_cache_and_wait_for_operation() drop and reclaim the lock
> > > to invalidate the cache, some other thread may suspend the operation
> > > before reaching the for(;;) loop. Therefore the loop must start with
> > > checking the chip->state before reading status from the chip.
> > >
> > > Signed-off-by: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
> >
> > Am I right that this patch should be ignored and a new patch will be
> > created?
>
> No, this is the real thing. Should go to Linus ASAP.
>
> There is a hunt for another flash HW related bug hunt ongoing too
> that may result in another patch touching other areas.
OK, all I can do is pushing to the l2 tree, the Linus story is up to
dwmw2 as usually, you should bug him. All I can do for you is letting
him know about this in the mtd chat.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-02-11 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 16:07 [PATCH] mtd: fix race in cfi_cmdset_0001 driver Joakim Tjernlund
2011-02-07 16:41 ` Stefan Bigler
2011-02-07 17:20 ` Michael Cashwell
2011-02-11 14:02 ` Artem Bityutskiy
2011-02-11 14:46 ` Joakim Tjernlund
2011-02-11 14:50 ` Artem Bityutskiy [this message]
2011-02-11 14:54 ` Joakim Tjernlund
2011-02-11 14:55 ` Artem Bityutskiy
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=1297435854.2760.43.camel@localhost \
--to=dedekind1@gmail.com \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-mtd@lists.infradead.org \
--cc=mboards@prograde.net \
--cc=stefan.bigler@keymile.com \
/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