ebc64a43c3
Merge commit 'refs/top-bases/linux-kernel-mem' into linux-kernel-mem
2010-08-10 11:06:21 -07:00
a2e6ae2bda
Merge branch 'linux-kernel-disk' into refs/top-bases/linux-zfs-branch
2010-08-10 11:06:13 -07:00
82d26b1027
Merge commit 'refs/top-bases/linux-kernel-disk' into linux-kernel-disk
2010-08-10 11:06:11 -07:00
5f466baab9
Merge branch 'linux-have-spl-debug' into refs/top-bases/linux-zfs-branch
2010-08-10 11:06:04 -07:00
6b655f7852
Merge commit 'refs/top-bases/linux-have-spl-debug' into linux-have-spl-debug
2010-08-10 11:06:02 -07:00
299cc480da
Merge branch 'linux-have-mntent' into refs/top-bases/linux-zfs-branch
2010-08-10 11:05:54 -07:00
989bc0ee5e
Merge commit 'refs/top-bases/linux-have-mntent' into linux-have-mntent
2010-08-10 11:05:52 -07:00
8023513a30
Add zvol snapshot and clone tests
...
Add two additional basic sanity tests to confirm zvol snapshots
and clones work. The snapshot test is basically the same as the
example provided in the wiki. The clone test goes one step father
and clones the snapshot then modifies it to match the original
modified volume. It them compares them to ensure everything was
modified as expected.
These are just meant to be sanity tests to catch obvious breakage
before tagging a release. They are still not a substitute for a
full regression test suite.
2010-08-10 10:59:58 -07:00
75562fd246
Merge branch 'linux-have-mlslabel' into refs/top-bases/linux-zfs-branch
2010-08-09 16:53:58 -07:00
d5a9306086
Merge commit 'refs/top-bases/linux-have-mlslabel' into linux-have-mlslabel
2010-08-09 16:53:56 -07:00
051011b7d5
Merge branch 'linux-spa-thread' into refs/top-bases/linux-zfs-branch
2010-08-09 16:53:48 -07:00
47849d4122
Merge commit 'refs/top-bases/linux-spa-thread' into linux-spa-thread
2010-08-09 16:53:46 -07:00
d6208180c0
Merge branch 'linux-topology' into refs/top-bases/linux-zfs-branch
2010-08-09 16:53:39 -07:00
1bdfef0d71
Merge commit 'refs/top-bases/linux-topology' into linux-topology
2010-08-09 16:53:37 -07:00
93d73a57d0
Merge branch 'linux-sha2' into refs/top-bases/linux-zfs-branch
2010-08-09 16:53:30 -07:00
049e6e8c03
Merge commit 'refs/top-bases/linux-sha2' into linux-sha2
2010-08-09 16:53:28 -07:00
284d721530
Merge branch 'linux-user-util' into refs/top-bases/linux-zfs-branch
2010-08-09 16:53:20 -07:00
8980d0fec4
Merge commit 'refs/top-bases/linux-user-util' into linux-user-util
2010-08-09 16:53:18 -07:00
0cf4c00681
Merge branch 'linux-events' into refs/top-bases/linux-zfs-branch
2010-08-09 16:53:11 -07:00
618744bf72
Merge commit 'refs/top-bases/linux-events' into linux-events
2010-08-09 16:53:09 -07:00
8ec113d74b
Merge branch 'linux-kernel-module' into refs/top-bases/linux-zfs-branch
2010-08-09 16:53:01 -07:00
99ca1a490a
Merge commit 'refs/top-bases/linux-kernel-module' into linux-kernel-module
2010-08-09 16:52:59 -07:00
2e43f3afcf
Merge branch 'linux-kernel-device' into refs/top-bases/linux-zfs-branch
2010-08-09 16:52:52 -07:00
62caddd096
Merge commit 'refs/top-bases/linux-kernel-device' into linux-kernel-device
2010-08-09 16:52:50 -07:00
d351ba4c24
Merge branch 'linux-have-idmap' into refs/top-bases/linux-zfs-branch
2010-08-09 16:52:42 -07:00
6f66da4848
Merge commit 'refs/top-bases/linux-have-idmap' into linux-have-idmap
2010-08-09 16:52:40 -07:00
a5ec8afb42
Merge branch 'linux-ztest' into refs/top-bases/linux-zfs-branch
2010-08-09 16:52:33 -07:00
9c87977d4c
Merge commit 'refs/top-bases/linux-ztest' into linux-ztest
2010-08-09 16:52:31 -07:00
0403624550
Merge branch 'linux-unused' into refs/top-bases/linux-zfs-branch
2010-08-09 16:52:23 -07:00
bd0dedf042
Merge commit 'refs/top-bases/linux-unused' into linux-unused
2010-08-09 16:52:21 -07:00
73dfb13fb5
Merge branch 'linux-libspl' into refs/top-bases/linux-zfs-branch
2010-08-09 16:52:14 -07:00
738aa2c55c
Merge commit 'refs/top-bases/linux-libspl' into linux-libspl
2010-08-09 16:52:12 -07:00
af45a68626
Merge branch 'linux-zpios' into refs/top-bases/linux-zfs-branch
2010-08-09 16:52:05 -07:00
1777f810b3
Merge commit 'refs/top-bases/linux-zpios' into linux-zpios
2010-08-09 16:52:03 -07:00
4efa87b0a2
Merge branch 'linux-user-disk' into refs/top-bases/linux-zfs-branch
2010-08-09 16:51:55 -07:00
64e27a563e
Merge commit 'refs/top-bases/linux-user-disk' into linux-user-disk
2010-08-09 16:51:53 -07:00
7d5e54a11b
Merge branch 'linux-symbol-collisions' into refs/top-bases/linux-zfs-branch
2010-08-09 16:51:45 -07:00
11a4494498
Merge commit 'refs/top-bases/linux-symbol-collisions' into linux-symbol-collisions
2010-08-09 16:51:43 -07:00
0ced01c6c5
Merge branch 'linux-kernel-mem' into refs/top-bases/linux-zfs-branch
2010-08-09 16:51:36 -07:00
e39a871d46
Merge commit 'refs/top-bases/linux-kernel-mem' into linux-kernel-mem
2010-08-09 16:51:34 -07:00
acf6f07ace
Merge branch 'linux-kernel-disk' into refs/top-bases/linux-zfs-branch
2010-08-09 16:51:26 -07:00
13c5d88ac4
Merge commit 'refs/top-bases/linux-kernel-disk' into linux-kernel-disk
2010-08-09 16:51:23 -07:00
f73f826e9f
Merge branch 'linux-have-spl-debug' into refs/top-bases/linux-zfs-branch
2010-08-09 16:51:16 -07:00
bbcc7cba51
Merge commit 'refs/top-bases/linux-have-spl-debug' into linux-have-spl-debug
2010-08-09 16:51:13 -07:00
9cb44812a4
Merge branch 'linux-have-mntent' into refs/top-bases/linux-zfs-branch
2010-08-09 16:51:06 -07:00
63d94952dc
Merge commit 'refs/top-bases/linux-have-mntent' into linux-have-mntent
2010-08-09 16:51:03 -07:00
dd11e3f7f0
Limit sysfs name to KOBJ_NAME_LEN
...
See commit dfc166d174
2010-08-09 16:45:38 -07:00
dfc166d174
Limit sysfs name to KOBJ_NAME_LEN
...
It appears that in earlier kernels the maximum name length of a
kobject was KOBJ_NAME_LEN (20) bytes. This was later extended to
dynamically allocate enough memory if it was over KOBJ_NAME_LEN,
and finally it was always made dynamic. Unfortunately, util this
last step happened it doesn't look like it always safe to use
names larger than KOBJ_NAME_LEN. For example, under the RHEL5
2.6.18 kernel if the kobject name length exceeds KOBJ_NAME_LEN
a NULL dereference is tripped.
To avoid this issue the build system has been update to check
to see if KOBJ_NAME_LEN is defined. If it is we have to assume
the maximum kobject name length is only 20 bytes. This 20 byte
name must minimally include the following components.
<zpool>/<dataset>[@snapshot[partition]]
2010-08-09 16:44:41 -07:00
d5168aa089
Insert small delay for udev
...
While the zfs utilities do block until the expected device appears
they can only do this for full devices, not partitions. This means
that once as device appears it still may take a little bit of time
before the kernel rescans the partition table, updates sysfs, udev
is notified and the partition devices are created. The test case
itself could block briefly waiting for the partition beause it knows
what to expect. But for now the simpler thing to do is just delay.
2010-08-09 16:43:54 -07:00
6478a7f847
Remove /zvol/ path component from zconfig.sh
...
See previous commit for details. But the gist is with the removal of
the zvol path component the regression tests must be updated to use
the correct path name.
2010-08-09 16:43:33 -07:00
Brian Behlendorf