From: Robin Bowes <robin-lists@robinbowes.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Re: Snapshot segfaults lvremove + bug kernel
Date: Sat, 13 May 2006 01:07:26 +0100 [thread overview]
Message-ID: <e437vu$ali$1@sea.gmane.org> (raw)
In-Reply-To: <4461CA20.2050305@robinbowes.com>
Robin Bowes wrote:
> Heinz Mauelshagen wrote:
>> On Tue, May 09, 2006 at 07:15:25PM +0100, Robin Bowes wrote:
>>> Do you have any idea when we might see a fix for this? Is the bug
>>> present in later versions?
>> A fix has been provided ~2 weeks ago to lkml and was tested ok.
>> It is in the recent stable kernels.
>
> Can you define "recent" so I know which to install.
Heinz,
Any chance you can tell me which kernel versions contain the fix?
Thanks,
R.
next prev parent reply other threads:[~2006-05-13 0:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 9:32 [linux-lvm] Snapshot segfaults lvremove + bug kernel Gabriel Barazer
2006-05-08 22:19 ` [linux-lvm] " Robin Bowes
2006-05-09 9:41 ` [linux-lvm] " Heinz Mauelshagen
2006-05-09 18:15 ` Robin Bowes
2006-05-10 10:48 ` Heinz Mauelshagen
2006-05-10 11:10 ` Robin Bowes
2006-05-13 0:07 ` Robin Bowes [this message]
2006-05-18 22:44 ` [linux-lvm] " Robin Bowes
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='e437vu$ali$1@sea.gmane.org' \
--to=robin-lists@robinbowes.com \
--cc=linux-lvm@redhat.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 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).