From: Alasdair G Kergon <agk@redhat.com>
To: David Greaves <david@dgreaves.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Oops and BUG in dm-snapshot
Date: Wed, 13 Sep 2006 23:18:41 +0100 [thread overview]
Message-ID: <20060913221840.GU13859@agk.surrey.redhat.com> (raw)
In-Reply-To: <44D3D04B.5060603@dgreaves.com>
On Fri, Aug 04, 2006 at 11:55:07PM +0100, David Greaves wrote:
> EIP is at exit_exception_table+0x36/0x5f [dm_snapshot]
http://bugzilla.kernel.org/show_bug.cgi?id=7040
Here's a patch for this to test:
http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/dm-snapshot-fix-freeing-pending-exception.patch
(depending on your kernel, to apply it you may require earlier snapshot patches
listed in the series file in the same directory)
Alasdair
--
agk@redhat.com
prev parent reply other threads:[~2006-09-13 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 22:55 [linux-lvm] Oops and BUG in dm-snapshot David Greaves
2006-09-13 22:18 ` Alasdair G Kergon [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=20060913221840.GU13859@agk.surrey.redhat.com \
--to=agk@redhat.com \
--cc=david@dgreaves.com \
--cc=linux-kernel@vger.kernel.org \
--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).