From: Jes.Sorensen@redhat.com
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org, dledford@redhat.com
Subject: [PATCH 0/1] Incremental() additional locking fixes
Date: Fri, 21 Oct 2011 18:21:37 +0200 [thread overview]
Message-ID: <1319214098-10409-1-git-send-email-Jes.Sorensen@redhat.com> (raw)
From: Jes Sorensen <Jes.Sorensen@redhat.com>
Hi,
This one goes on top of my previous set of changes to the locking
hierachy in Incremental(). I basically noticed that in most places, an
error in Incremental() would error out without releasing the lock.
Cheers,
Jes
Jes Sorensen (1):
Incremental() lock error handling
Incremental.c | 27 ++++++++++++++-------------
1 files changed, 14 insertions(+), 13 deletions(-)
--
1.7.4.4
next reply other threads:[~2011-10-21 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 16:21 Jes.Sorensen [this message]
2011-10-21 16:21 ` [PATCH 1/1] Incremental() lock error handling Jes.Sorensen
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=1319214098-10409-1-git-send-email-Jes.Sorensen@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).