From: Chris Mason <mason@suse.com>
To: linux-lvm@sistina.com
Cc: andrea@suse.de
Subject: Re: [linux-lvm] Patch for Kernel 2.2.16
Date: Fri, 19 Jan 2001 16:04:42 -0500 [thread overview]
Message-ID: <20320000.979938282@tiny> (raw)
In-Reply-To: <20010119181735.B14771@srv.sistina.com>
On Friday, January 19, 2001 06:17:35 PM +0000 "Heinz J. Mauelshagen"
<Heinz.Mauelshagen@t-online.de> wrote:
>> After testing a bit more, I have found a bug in the snapshot creation.
>> Under load, you can get a
>> 'kernel panic: brw_kiovec: iobuf not locked for I/O'
>
> I think Andrea Arcangeli's patch set the previously introduced
>
> iobuf->locked = 1;
>
> to 0 again.
> Change it to 1 and test.
> This should fix it.
>
Yes, this diff looks like it came from Andrea's code, but his brw_kiovec
doesn't panic when the iobuf isn't locked.
-chris
next prev parent reply other threads:[~2001-01-19 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 15:19 [linux-lvm] Patch for Kernel 2.2.16 ZECHA,HOLGER (HP-Germany,ex1)
2001-01-19 16:17 ` AJ Lewis
2001-01-19 16:49 ` AJ Lewis
2001-01-19 17:22 ` Joe Thornber
2001-01-19 19:51 ` AJ Lewis
2001-01-20 17:51 ` Joe Thornber
2001-01-19 18:17 ` Heinz J. Mauelshagen
2001-01-19 21:04 ` Chris Mason [this message]
2001-01-19 16:24 ` Joe Thornber
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=20320000.979938282@tiny \
--to=mason@suse.com \
--cc=andrea@suse.de \
--cc=linux-lvm@sistina.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.