public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent CARON <lcaron@lncsa.com>
To: Stefan Seifert <nine@detonation.org>
Cc: Hannes Dorbath <light@theendofthetunnel.de>,
	linux-kernel@vger.kernel.org, drbd-user@linbit.com,
	Lars Ellenberg <lars.ellenberg@linbit.com>
Subject: Re: [DRBD-user] Crash on 2.6.22
Date: Fri, 28 Sep 2007 11:25:14 +0200	[thread overview]
Message-ID: <46FCC87A.3060004@lncsa.com> (raw)
In-Reply-To: <46FCC7A2.8090506@detonation.org>

Stefan Seifert wrote:
> The deadlock also occures with 0.7.x. A patch for that is floating around.

Here is a transcript from a mail I sent to Lars Ellenberg

It should 'normally' be fixed.

Am I wrong ?

Thanks



On Sun, Sep 16, 2007 at 05:34:01PM +0200, Laurent CARON wrote:
> > Lars Ellenberg a écrit :
>> > >On Fri, Sep 14, 2007 at 12:33:01AM +0200, Laurent CARON wrote:
>>> > >>Hi,
>>> > >>
>>> > >>After reading the thread about XFS, drbd 8.0.5 and 2.6.22+
kernels (XFS
>>> > >>filesystem locks on mounting with 0.8.0.5), i wonder if the same
applies
>>> > >>to using 0.7.24 and 2.6.22+.
>> > >
>> > >basically, yes.
>> > >so either don't use 0.7 with the kernels showing this behaviour,
>> > >or wait for some maintenance release,
>> > >or patch it yourself.
> >
> >
> > You said that this is fixed in the latest 8.x SVN.

it is fixed in 8.0.6

> > It is fixed in the latest 0.7.x SVN too ?

now, since you are so pushy today  :)
I just checked in something (r3062),
which should do the job, but is untested by me so far.
please test and report back.

      reply	other threads:[~2007-09-28  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  9:00 Crash on 2.6.22 Laurent CARON
2007-09-28  9:05 ` [DRBD-user] " Hannes Dorbath
2007-09-28  9:12   ` Laurent CARON
2007-09-28  9:21   ` Stefan Seifert
2007-09-28  9:25     ` Laurent CARON [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=46FCC87A.3060004@lncsa.com \
    --to=lcaron@lncsa.com \
    --cc=drbd-user@linbit.com \
    --cc=lars.ellenberg@linbit.com \
    --cc=light@theendofthetunnel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nine@detonation.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