From: Lars Marowsky-Bree <lmb@suse.de>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org, axboe@suse.de
Subject: Re: Locking bugs in 2.4 md.c
Date: Fri, 19 Sep 2003 10:36:40 +0200 [thread overview]
Message-ID: <20030919083639.GE3143@marowsky-bree.de> (raw)
In-Reply-To: <20030919072610.GB3143@marowsky-bree.de>
On 2003-09-19T09:26:10,
Lars Marowsky-Bree <lmb@suse.de> said:
> > A patch against 2.4-current is below. It probably works but I haven't
> > reviewed it in the context of other recent changes to md so I make no
> > promises.
> Thanks. I'll merge it against the current 2.4.
Hi Neil, turns out your patch did exactly what I did with lock_mddev(),
just with a bigger granularity (which I think is a good thing, but I was
too shy to introduce a new lock).
However, I can still reliably panic the kernel with the sequence I gave
on a SMP box, even though the panic now seems to occur in different
places...
So if you have any further idea what could cause that, I appreciate any
hints ;-)
I'll go dig in some deeper now and gear up kgdb...
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering ever tried. ever failed. no matter.
SuSE Labs try again. fail again. fail better.
Research & Development, SuSE Linux AG -- Samuel Beckett
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-09-19 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 15:23 Locking bugs in 2.4 md.c Lars Marowsky-Bree
2003-09-19 2:08 ` Neil Brown
2003-09-19 7:26 ` Lars Marowsky-Bree
2003-09-19 8:36 ` Lars Marowsky-Bree [this message]
2003-09-19 14:18 ` Lars Marowsky-Bree
2003-09-22 5:54 ` Neil Brown
2003-09-23 11:08 ` Lars Marowsky-Bree
2003-09-24 10:31 ` [fixes] " Lars Marowsky-Bree
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=20030919083639.GE3143@marowsky-bree.de \
--to=lmb@suse.de \
--cc=axboe@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).