From: zkabelac@sourceware.org <zkabelac@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW_DM tools/dmsetup.c
Date: 3 Aug 2010 13:04:33 -0000 [thread overview]
Message-ID: <20100803130433.4922.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac at sourceware.org 2010-08-03 13:04:32
Modified files:
. : WHATS_NEW_DM
tools : dmsetup.c
Log message:
Wait for node creation before displaying debug info in dmsetup.
Readahead check needs to see created node - so wait till udev gets in sync.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.402&r2=1.403
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/dmsetup.c.diff?cvsroot=lvm2&r1=1.143&r2=1.144
--- LVM2/WHATS_NEW_DM 2010/08/03 12:56:00 1.402
+++ LVM2/WHATS_NEW_DM 2010/08/03 13:04:32 1.403
@@ -1,5 +1,6 @@
Version 1.02.54 -
================================
+ Wait for node creation before displaying debug info in dmsetup.
Fix return status 0 for "dmsetup info -c -o help".
Add check for kernel semaphore support and disable udev_sync if not available.
--- LVM2/tools/dmsetup.c 2010/08/03 12:56:00 1.143
+++ LVM2/tools/dmsetup.c 2010/08/03 13:04:32 1.144
@@ -633,9 +633,16 @@
r = 1;
+ if (!_udev_cookie)
+ (void) dm_udev_wait(cookie);
+
if (_switches[VERBOSE_ARG])
r = _display_info(dmt);
+ dm_task_destroy(dmt);
+
+ return r;
+
out:
if (!_udev_cookie)
(void) dm_udev_wait(cookie);
next reply other threads:[~2010-08-03 13:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 13:04 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-24 8:24 LVM2 ./WHATS_NEW_DM tools/dmsetup.c prajnoha
2012-04-24 8:00 prajnoha
2012-03-01 21:56 zkabelac
2012-02-15 12:08 prajnoha
2012-02-15 12:06 prajnoha
2012-02-15 12:02 prajnoha
2012-02-13 12:06 zkabelac
2011-08-11 17:06 mbroz
2011-07-08 17:08 agk
2011-06-17 14:55 prajnoha
2011-03-29 21:49 zkabelac
2011-03-02 2:44 agk
2010-08-03 12:56 zkabelac
2010-07-08 14:29 zkabelac
2009-06-03 20:44 agk
2009-06-03 18:35 agk
2009-04-24 11:30 prajnoha
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=20100803130433.4922.qmail@sourceware.org \
--to=zkabelac@sourceware.org \
--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.