From: agk@sourceware.org
To: dm-cvs@sourceware.org, dm-devel@redhat.com
Subject: device-mapper ./WHATS_NEW lib/libdevmapper.h l ...
Date: 2 Sep 2008 12:16:07 -0000 [thread overview]
Message-ID: <20080902121607.13194.qmail@sourceware.org> (raw)
CVSROOT: /cvs/dm
Module name: device-mapper
Changes by: agk@sourceware.org 2008-09-02 12:16:07
Modified files:
. : WHATS_NEW
lib : libdevmapper.h libdm-deptree.c
Log message:
Extend deptree buffers so the largest possible device numbers fit.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/device-mapper/WHATS_NEW.diff?cvsroot=dm&r1=1.249&r2=1.250
http://sourceware.org/cgi-bin/cvsweb.cgi/device-mapper/lib/libdevmapper.h.diff?cvsroot=dm&r1=1.83&r2=1.84
http://sourceware.org/cgi-bin/cvsweb.cgi/device-mapper/lib/libdm-deptree.c.diff?cvsroot=dm&r1=1.40&r2=1.41
--- device-mapper/WHATS_NEW 2008/06/27 15:36:51 1.249
+++ device-mapper/WHATS_NEW 2008/09/02 12:16:06 1.250
@@ -1,5 +1,6 @@
Version 1.02.28 -
================================
+ Extend deptree buffers so the largest possible device numbers fit.
Added generation of the versioned libdevmapper-event.so for LVM's test
Underline longer report help text headings.
--- device-mapper/lib/libdevmapper.h 2008/06/24 22:53:48 1.83
+++ device-mapper/lib/libdevmapper.h 2008/09/02 12:16:07 1.84
@@ -181,8 +181,9 @@
uint64_t size, const char *ttype, const char *params);
/*
- * Format major/minor numbers correctly for input to driver
+ * Format major/minor numbers correctly for input to driver.
*/
+#define DM_FORMAT_DEV_BUFSIZE 13 /* Minimum bufsize to handle worst case. */
int dm_format_dev(char *buf, int bufsize, uint32_t dev_major, uint32_t dev_minor);
/* Use this to retrive target information returned from a STATUS call */
--- device-mapper/lib/libdm-deptree.c 2008/06/25 14:24:17 1.40
+++ device-mapper/lib/libdm-deptree.c 2008/09/02 12:16:07 1.41
@@ -1243,7 +1243,7 @@
size_t paramsize, int *pos)
{
struct seg_area *area;
- char devbuf[10];
+ char devbuf[DM_FORMAT_DEV_BUFSIZE];
int tw;
const char *prefix = "";
@@ -1270,7 +1270,8 @@
int pos = 0;
int tw;
int r;
- char originbuf[10], cowbuf[10], logbuf[10];
+ char originbuf[DM_FORMAT_DEV_BUFSIZE], cowbuf[DM_FORMAT_DEV_BUFSIZE];
+ char logbuf[DM_FORMAT_DEV_BUFSIZE];
const char *logtype;
switch(seg->type) {
next reply other threads:[~2008-09-02 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 12:16 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-29 17:23 device-mapper ./WHATS_NEW lib/libdevmapper.h l agk
2007-01-23 19:18 agk
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=20080902121607.13194.qmail@sourceware.org \
--to=agk@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.