From: Joe Thornber <joe@fib011235813.fsnet.co.uk>
To: linux-lvm@sistina.com, lvm-devel@sistina.com
Cc: Alan Cox <alan@redhat.com>
Subject: [linux-lvm] dm patches for 2.5.50
Date: Thu Nov 28 06:05:02 2002 [thread overview]
Message-ID: <20021128120436.GA11436@reti> (raw)
Latest dm patches for 2.5.50 are available here:
http://people.sistina.com/~thornber/patches/2.5-stable/2.5.50/
- Joe
Revision 1:
Four constants:
DM_DIR,
DM_MAX_TYPE_NAME,
DM_NAME_LEN,
DM_UUID_LEN
Were being declared in device-mapper.h, these are all specific to
the ioctl interface, so they've been moved to dm-ioctl.h. Nobody
in userland should ever include <linux/device-mapper.h> so remove
ifdef __KERNEL guards.
Revision 2:
Joe,
I believe Steve and I found a bug in dm-table.c. The function open_dev()
has the wrong check after the call to blkdev_get(). Thus, if the
blkdev_get() call succeeds, bd_claim() is never called. Futhermore, if
blkdev_get() fails (for instance, if you try to create a target to a
non-existent device), bd_claim() will fail, and blkdev_put() may segfault.
--
Kevin Corry
corryk@us.ibm.com
http://evms.sourceforge.net/
==============================
Revision 3:
Return -ENOTBLK if lookup_device() finds the inode, but it
is not a block device. [Cristoph Hellwig]
Revision 4:
No need to validate the parameters if we are doing a
REMOVE_ALL command.
Revision 5:
check_device_area was comparing the bytes with sectors.
[Stefan Lauterbach]
reply other threads:[~2002-11-28 6:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021128120436.GA11436@reti \
--to=joe@fib011235813.fsnet.co.uk \
--cc=alan@redhat.com \
--cc=linux-lvm@sistina.com \
--cc=lvm-devel@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox