public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: zkabelac@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW daemons/dmeventd/dmeventd.c Date: Mon, 20 Dec 2010 14:08:00 -0000 [thread overview] Message-ID: <20101220140846.24389.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2010-12-20 14:08:46 Modified files: . : WHATS_NEW daemons/dmeventd: dmeventd.c Log message: Add check for unlink errors Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1846&r2=1.1847 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/daemons/dmeventd/dmeventd.c.diff?cvsroot=lvm2&r1=1.72&r2=1.73 --- LVM2/WHATS_NEW 2010/12/20 13:57:19 1.1846 +++ LVM2/WHATS_NEW 2010/12/20 14:08:46 1.1847 @@ -1,5 +1,6 @@ Version 2.02.79 - =================================== + Add check for unlink error result in remove_lockfile() (dmeventd). Use dm_free for dm_malloc-ed areas in _clog_ctr/_clog_dtr (cmirrord). Add checks for allocation errors in config node clonning. Fix error path if regex engine cannot be created in _build_matcher(). --- LVM2/daemons/dmeventd/dmeventd.c 2010/12/13 10:43:57 1.72 +++ LVM2/daemons/dmeventd/dmeventd.c 2010/12/20 14:08:46 1.73 @@ -1642,7 +1642,8 @@ static void remove_lockfile(void) { - unlink(DMEVENTD_PIDFILE); + if (unlink(DMEVENTD_PIDFILE)) + perror(DMEVENTD_PIDFILE ": unlink failed"); } static void _daemonize(void)
next reply other threads:[~2010-12-20 14:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-20 14:08 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-12-21 13:03 zkabelac 2011-02-28 19:47 zkabelac 2010-03-31 12:01 mpatocka
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=20101220140846.24389.qmail@sourceware.org \ --to=zkabelac@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).