All of lore.kernel.org
 help / color / mirror / Atom feed
From: mornfall@sourceware.org
To: dm-cvs@sourceware.org, dm-devel@redhat.com
Subject: device-mapper ./WHATS_NEW dmeventd/libdevmappe ...
Date: 2 Aug 2007 22:31:59 -0000	[thread overview]
Message-ID: <20070802223159.24050.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/dm
Module name:	device-mapper
Changes by:	mornfall@sourceware.org	2007-08-02 22:31:59

Modified files:
	.              : WHATS_NEW 
	dmeventd       : libdevmapper-event.c 

Log message:
	Fix a possible segfault in libdevmapper-event. Thanks to Brian J. Wood
	for noticing this.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/device-mapper/WHATS_NEW.diff?cvsroot=dm&r1=1.196&r2=1.197
http://sourceware.org/cgi-bin/cvsweb.cgi/device-mapper/dmeventd/libdevmapper-event.c.diff?cvsroot=dm&r1=1.22&r2=1.23

--- device-mapper/WHATS_NEW	2007/07/28 10:48:36	1.196
+++ device-mapper/WHATS_NEW	2007/08/02 22:31:59	1.197
@@ -1,5 +1,6 @@
 Version 1.02.22 - 
 ================================
+  Fix a possible segfault in libdevmapper-event
   Export dm_create_dir (was create_dir) to help fix LVM2 link error
   Don't log mkdir fail-with-EROFS, to make create_dir equiv to the one in LVM2
   Introduce and use log_sys_* macros from LVM2
--- device-mapper/dmeventd/libdevmapper-event.c	2007/04/19 19:10:19	1.22
+++ device-mapper/dmeventd/libdevmapper-event.c	2007/08/02 22:31:59	1.23
@@ -706,6 +706,7 @@
 	}
 
 	dm_task_destroy(dmt);
+	dmt = 0;
 
 	if (msg.data) {
 		dm_free(msg.data);
@@ -759,7 +760,8 @@
 	if (reply_uuid)
 		dm_free(reply_uuid);
 	_dm_event_handler_clear_dev_info(dmevh);
-	dm_task_destroy(dmt);
+	if (dmt)
+		dm_task_destroy(dmt);
 	return ret;
 }
 

             reply	other threads:[~2007-08-02 22:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02 22:31 mornfall [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-27 12:26 device-mapper ./WHATS_NEW dmeventd/libdevmappe mornfall
2007-04-19 19:10 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=20070802223159.24050.qmail@sourceware.org \
    --to=mornfall@sourceware.org \
    --cc=dm-cvs@sourceware.org \
    --cc=dm-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.