From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Kevin Cernekee <cernekee@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: mtd_blkdevs: don't increase 'open' count on error path
Date: Thu, 17 Nov 2011 23:35:06 +0200 [thread overview]
Message-ID: <1321565708.2272.11.camel@koala> (raw)
In-Reply-To: <1320709865-21903-1-git-send-email-computersforpeace@gmail.com>
On Mon, 2011-11-07 at 15:51 -0800, Brian Norris wrote:
> Some error paths in mtd_blkdevs were fixed in the following commit:
>
> commit 94735ec4044a6d318b83ad3c5794e931ed168d10
> mtd: mtd_blkdevs: fix error path in blktrans_open
>
> But on these error paths, the block device's `dev->open' count is
> already incremented before we check for errors. This meant that, while
> the error path was handled correctly on the first time through
> blktrans_open(), the device is erroneously considered already open on
> the second time through.
Pushed to l2-mtd-2.6.git, thanks!
Artem.
prev parent reply other threads:[~2011-11-17 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 23:51 [PATCH] mtd: mtd_blkdevs: don't increase 'open' count on error path Brian Norris
2011-11-17 21:35 ` Artem Bityutskiy [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=1321565708.2272.11.camel@koala \
--to=dedekind1@gmail.com \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--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