From: Marian Csontos <mcsontos@redhat.com>
To: lvm-devel@redhat.com
Subject: dmeventd generates segfault when creating snapshots
Date: Wed, 12 Feb 2014 10:06:34 +0100 [thread overview]
Message-ID: <52FB399A.9090406@redhat.com> (raw)
In-Reply-To: <52F9FC6D.6090708@redhat.com>
On 02/11/2014 11:33 AM, Zdenek Kabelac wrote:
> Dne 10.2.2014 12:34, Chiyohiko Morita napsal(a):
>>
>> (I'm not on this list; please Cc me)
>>
>> With a high load, the dmeventd daemon sometimes generates
>> a segmentation violation when createing a lvm-snapshot.
>>
>> In _register_for_event(), it may take 10 or more seconds between
>> calling _register_for_timeout() and _create_thread().
>> (Please refer to the following _register_for_timeout().)
>>
>> If the _timeout_thread thread calls pthread_kill() before
>> _create_thread() is called, dmeventd will generate segfault.
>> This is because the value of thread->thread is still NULL.
>> (Please refer to the following _timeout_thread().)
>>
>> A related source code and coredump are shown below.
>>
>
> Could you please open regular lvm2 bugzilla
> (at http://bugzilla.redhat.com/ - use Fedora Rawhide in case you don't
> have match for your distro)
>
> Attach all your information provided here in your email.
>
> Add info from 'vgs, lvs -a, pvs' and your in-use lvm.conf
> version of your lvm2 package,
> how many volumes are active.
IMO this is closely related to Bug 889651 - segfault in dmeventd in low
memory situations.
https://bugzilla.redhat.com/show_bug.cgi?id=889651
-- Marian
>
> Thank you
>
> Zdenek
>
> --
> lvm-devel mailing list
> lvm-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/lvm-devel
>
prev parent reply other threads:[~2014-02-12 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 11:34 dmeventd generates segfault when creating snapshots Chiyohiko Morita
2014-02-11 10:33 ` Zdenek Kabelac
2014-02-12 8:18 ` Chiyohiko Morita
2014-02-12 9:06 ` Marian Csontos [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=52FB399A.9090406@redhat.com \
--to=mcsontos@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.