From: Lars Marowsky-Bree <lmb@suse.de>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] Re: [DRBD-cvs] svn commit by phil - r1985 - branches/drbd-0.7/drbd - Fixed a self made SMP lockup; showing up in drbd_al_com
Date: Mon, 17 Oct 2005 15:43:49 +0200 [thread overview]
Message-ID: <20051017134349.GT8354@marowsky-bree.de> (raw)
In-Reply-To: <20051017134012.CB1741431D@mail.linbit.com>
On 2005-10-17T15:40:12, drbd-cvs@lists.linbit.com wrote:
> Author: phil
> Date: 2005-10-17 15:40:11 +0200 (Mon, 17 Oct 2005)
> New Revision: 1985
>
> Modified:
> branches/drbd-0.7/drbd/drbd_bitmap.c
> Log:
> Fixed a self made SMP lockup; showing up in drbd_al_complete_io()
>
> With drbd-0.7.12 we moved the al_lock before the bm_clear_bit()
> in __drbd_set_in_sync(). That by itself is okay, but
> in bm_clear_bit() we used the spin_[un]lock_irq() functions,
> therefore reenabling interrupts...
> This is fixed now.
Hi Philipp, how critical is this bug, and how likely is it that it will
be hit in practice?
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
next parent reply other threads:[~2005-10-17 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051017134012.CB1741431D@mail.linbit.com>
2005-10-17 13:43 ` Lars Marowsky-Bree [this message]
2005-10-17 13:56 ` [Drbd-dev] Re: [DRBD-cvs] svn commit by phil - r1985 - branches/drbd-0.7/drbd - Fixed a self made SMP lockup; showing up in drbd_al_com Lars Ellenberg
2005-10-17 13:57 ` Lars Marowsky-Bree
2005-10-17 14:15 ` Lars Ellenberg
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=20051017134349.GT8354@marowsky-bree.de \
--to=lmb@suse.de \
--cc=drbd-dev@lists.linbit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.