From: Petr Rockai <prockai@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] Fix double releasing of vg when repairing of vg is requested
Date: Fri, 05 Jun 2009 20:52:36 +0200 [thread overview]
Message-ID: <873aaetswb.fsf@mornfall.net> (raw)
In-Reply-To: <4A291EDC.4060300@redhat.com> (Milan Broz's message of "Fri, 05 Jun 2009 15:34:20 +0200")
Milan Broz <mbroz@redhat.com> writes:
> [maybe this somehow collide with proposed vg_read changes,
> but this is serious bug which should be fixed asap...]
Yes, it does collide with vg_read changes, and it also duplicates one of the
patches that already unifies the recovery process. There are other crash bugs
waiting for the vg_read patches to be applied, so maybe it would be best to get
the vg_read patches applied, then...
See also this message:
Subject: Re: [lvm-devel][PATCH] Fix segfault when using vgsplit in stacked environment
Message-ID: <87bpt211a3.fsf@eriador.mornfall.net>
which has a patch that fixes a vgsplit segfault that needs new vg_read.
If there's no better interim fix though and this is really urgent, I guess that
vg_read patches will have to give way. I would however ask that this patch be
reverted before applying vg_read bits, because I have rewritten and rebased
vg_read more than enough times already...
Yours,
Petr.
--
Peter Rockai | me()mornfall!net | prockai()redhat!com
http://blog.mornfall.net | http://web.mornfall.net
"In My Egotistical Opinion, most people's C programs should be
indented six feet downward and covered with dirt."
-- Blair P. Houghton on the subject of C program indentation
prev parent reply other threads:[~2009-06-05 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 13:34 [PATCH] Fix double releasing of vg when repairing of vg is requested Milan Broz
2009-06-05 18:52 ` Petr Rockai [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=873aaetswb.fsf@mornfall.net \
--to=prockai@redhat.com \
--cc=lvm-devel@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 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.