public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: mbroz@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW daemons/clvmd/refresh_clvmd.c Date: Thu, 01 Jul 2010 21:46:00 -0000 [thread overview] Message-ID: <20100701214610.947.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: mbroz@sourceware.org 2010-07-01 21:46:09 Modified files: . : WHATS_NEW daemons/clvmd : refresh_clvmd.c Log message: Fix another segfault in clvmd -R if no response from daemon received. Missed the same problem in another function... Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1647&r2=1.1648 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/daemons/clvmd/refresh_clvmd.c.diff?cvsroot=lvm2&r1=1.12&r2=1.13 --- LVM2/WHATS_NEW 2010/07/01 21:23:47 1.1647 +++ LVM2/WHATS_NEW 2010/07/01 21:46:09 1.1648 @@ -1,5 +1,6 @@ Version 2.02.70 - ================================ + Fix another segfault in clvmd -R if no response from daemon received. (2.02.68) Remove superfluous suspended device counter from clvmd. Fix lvm shell crash when input is entirely whitespace. Update partial mode warning message. --- LVM2/daemons/clvmd/refresh_clvmd.c 2010/06/21 15:56:58 1.12 +++ LVM2/daemons/clvmd/refresh_clvmd.c 2010/07/01 21:46:09 1.13 @@ -285,7 +285,7 @@ { int num_responses; char args[1]; // No args really. - lvm_response_t *response; + lvm_response_t *response = NULL; int saved_errno; int status; int i;
next reply other threads:[~2010-07-01 21:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-01 21:46 mbroz [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-09-21 13:40 mbroz 2010-06-21 10:45 mbroz 2010-06-07 13:52 mbroz
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=20100701214610.947.qmail@sourceware.org \ --to=mbroz@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.org \ /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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).