From: Joe Thornber <joe@fib011235813.fsnet.co.uk>
To: linux-lvm@sistina.com, lvm-devel@sistina.com
Subject: [linux-lvm] 2.4.20-dm-1
Date: Fri Nov 29 04:02:02 2002 [thread overview]
Message-ID: <20021129100126.GA554@reti> (raw)
http://people.sistina.com/~thornber/patches/2.4-stable/2.4.20/2.4.20-dm-1.tar.bz2
Revision 1:
2.5 backport
Revision 2:
The locking when leaving __request was broken.
Split off __deferring()
Revision 3:
s->table wasn't being set in the snapshot contructor
Revision 4:
I don't know why dm-ioctl.c was including <linux/compatmac.h>
rather than <asm/uaccess.h>
Revision 5:
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 6:
No need to validate the parameters if we are doing a
REMOVE_ALL command.
Revision 7:
Fluff
Revision 8:
Mempool version by Christoph Hellwig that holds the free objects
in an array rather than a list. This prevents the objects getting
dirtied, eg, people maybe expecting them to come out of a slab with
a particular state.
Revision 9:
Return -ENOTBLK if lookup_device() finds the inode, but it
is not a block device. [Cristoph Hellwig]
Revision 10:
get_kdev() was locking _minor_lock rather than
&_minor_lock. [Heinz Mauelshagen]
Revision 11:
minor change for dm-strip.c. Tests for correct chunksize before it allocates
the stripe context. [Heinz Mauelshagen]
Revision 12:
There's a bug in the dm-stripe.c constructor failing top check if enough
destinations are handed in. [Heinz Mauelshagen]
reply other threads:[~2002-11-29 4:02 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=20021129100126.GA554@reti \
--to=joe@fib011235813.fsnet.co.uk \
--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 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.