[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#342455: marked as done (tech-ctte: Ownership and permissions of device mapper block devices)

Your message dated Sat, 10 Jun 2006 14:47:10 -0700
with message-id <E1FpBIU-0001KU-7o@spohr.debian.org>
and subject line Bug#341901: fixed in devmapper 2:1.02.07-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: tech-ctte
Severity: important

Dear Technical Committee,

Ownership and permissions of device mapper block devices

This concerns Debian bugs #329409, #316883 and #341901:
#329409: group and perms wrong in /dev/mapper
#316883: lvm2: creates device nodes as root:root 600, breaking amanda
#341901: udev: Ownership and permissions incorrect for device-mapper
         devices and directories

The package maintainer (Bastian Blank) does not agree with the bug
submitters that this is a bug, and has tagged the bugs +wontfix.  He
has also rejected the patches I (and others) submitted to fix this.  He
has agreed to my submitting this to the Technical Committee.


Disk block devices on the Debian system have historically been owned
by root:disk with 0660 permissions (user and group readable and
writable).  This was also the case with LVM1, and also
LVM2/device-mapper until earlier this year.  The change was in the
default device ownership and permissions of logical volume devices
created under /dev/mapper by libdevmapper (in the devmapper package).

This change made the LV devices different than all the other disk
block devices on the Debian system.  The effect of this is to break
the use of the "disk" group.  For example, the "backup" user is a
member of the disk group, and uses the ability to read and write disk
block devices in order to backup and restore backups, for example
using dump/restore, tar, or a backup system such as amanda.  It is not
currently possible to back up or restore backups using e.g. amanda

1) manually fixing up the ownership and permissions.  This is fragile
   in the face of device name changes or device creation, and the
   changes are not preserved over a reboot, so a power cut breaks
   everything.  I'm currently using a hacked-up init script to work
   around this, but it's far from perfect, and certainly not something
   our users should be forced to do.
2) using special udev rules, but I have yet to see any such rules
   in existence.

The defaults are hard-coded in the devmapper package, and there is
nothing the end user can do short of rebuilding the package by hand.
This is simple stuff, and there is no reason it shouldn't just work if
the defaults were changed back to root:disk, 0660.

The discussion in #329409 and #316883 shows exactly what breaks, and
both provide the same solution to the problem, which is even suggested
by LVM upstream.  Neither have any rationale given for the change by
the maintainer.  I have attached proposed patches to both bugs.

#341901 is a duplicate I filed before finding the other two.  Note
that the udev package does not create any LVM device other than
/dev/mapper; the other device creation is done purely by devmapper,
and its behaviour is not configurable by an end-user.

Note that this issue also affects the current stable release, sarge,
so stable users cannot back up their systems.  I regard this as a
serious defect in the stable release, having production servers which
can't be backed up without stupid hacks.  If possible, I would like to
get this fixed in time for the next sarge point release.

Many thanks,
Roger Leigh

--- End Message ---
--- Begin Message ---
Source: devmapper
Source-Version: 2:1.02.07-1

We believe that the bug you reported is fixed in the latest version of
devmapper, which is due to be installed in the Debian FTP archive:

  to pool/main/d/devmapper/devmapper_1.02.07-1.diff.gz
  to pool/main/d/devmapper/devmapper_1.02.07-1.dsc
  to pool/main/d/devmapper/devmapper_1.02.07.orig.tar.gz
  to pool/main/d/devmapper/dmsetup-udeb_1.02.07-1_amd64.udeb
  to pool/main/d/devmapper/dmsetup_1.02.07-1_amd64.deb
  to pool/main/d/devmapper/libdevmapper-dev_1.02.07-1_amd64.deb
  to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.07-1_amd64.udeb
  to pool/main/d/devmapper/libdevmapper1.02_1.02.07-1_amd64.deb

A summary of the changes between this version and the previous one is

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 341901@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
Bastian Blank <waldi@debian.org> (supplier of updated devmapper package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)

Hash: SHA1

Format: 1.7
Date: Sat, 10 Jun 2006 21:20:43 +0000
Source: devmapper
Binary: dmsetup libdevmapper1.02-udeb libdevmapper1.02 libdevmapper-dev dmsetup-udeb
Architecture: source amd64
Version: 2:1.02.07-1
Distribution: unstable
Urgency: low
Maintainer: Debian LVM Team <pkg-lvm-maintainers@lists.alioth.debian.org>
Changed-By: Bastian Blank <waldi@debian.org>
 dmsetup    - The Linux Kernel Device Mapper userspace library
 dmsetup-udeb - The Linux Kernel Device Mapper userspace library (udeb)
 libdevmapper-dev - The Linux Kernel Device Mapper header files
 libdevmapper1.02 - The Linux Kernel Device Mapper userspace library
 libdevmapper1.02-udeb - The Linux Kernel Device Mapper userspace library (udeb)
Closes: 316883 329409 341901 342455
 devmapper (2:1.02.07-1) unstable; urgency=low
   * New upstream version.
   * Update priorities to match overrides.
   * Acknowledge NMU. (closes: #316883, #329409, #341901, #342455)
 4d3f3baac4e84bce0b7484503364c960 762 admin optional devmapper_1.02.07-1.dsc
 ed0ff12decdc617d9268f213ed2c1d29 923619 admin optional devmapper_1.02.07.orig.tar.gz
 4a01f14aaf585cbfb8e7d2a88f03ac47 44831 admin optional devmapper_1.02.07-1.diff.gz
 f6776d113347ee10fb43744f88fd5f45 51844 libdevel optional libdevmapper-dev_1.02.07-1_amd64.deb
 b00e5a071a951a26d10f809504b2881b 41058 libs required libdevmapper1.02_1.02.07-1_amd64.deb
 1cdc69ffa8c9ce18f5a9db68dca4c931 29196 debian-installer optional libdevmapper1.02-udeb_1.02.07-1_amd64.udeb
 225df1b21e94d9f7694446487a5773d6 27394 admin optional dmsetup_1.02.07-1_amd64.deb
 a861d35324f707a1ea14d6f088751242 13074 debian-installer optional dmsetup-udeb_1.02.07-1_amd64.udeb
Package-Type: udeb

Version: GnuPG v1.4.3 (GNU/Linux)


--- End Message ---

Reply to: