Your message dated Sat, 26 Jun 2010 23:01:38 +0100
with message-id <[email protected]>
and subject line Re: [buildd-tools-devel] Bug#584961: Bug#584961: schroot:
lvm-snapshot device lock permission failure
has caused the Debian Bug report #584961,
regarding schroot: lvm-snapshot device lock permission failure
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
584961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584961
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: schroot
Version: 1.2.3
Severity: normal
When a non-root user is accessing an lvm snapshot chroot, the call to lockdev
is made with insufficient permissions, resulting in this error:
E: test-f13-401b1c48-570f-48bb-8389-4b6d44f18577: Failed to lock chroot:
/dev/fastvg/f13lv: Failed to lock device: Failed to lock device
This issue can also be reproduced in schroot 1.4.2
Additional details are available in Fedora bug 600638 here:
https://bugzilla.redhat.com/show_bug.cgi?id=600636
The patch proposed there consists of moving the setuid call to an earlier
point before the call to lockdev is made.
-Zach
--- End Message ---
--- Begin Message ---
Version: 1.2.3
On Mon, Jun 07, 2010 at 10:38:35PM +0100, Roger Leigh wrote:
> On Mon, Jun 07, 2010 at 01:30:22PM -0700, Zach Carter wrote:
> > When a non-root user is accessing an lvm snapshot chroot, the call to
> > lockdev
> > is made with insufficient permissions, resulting in this error:
> >
> > E: test-f13-401b1c48-570f-48bb-8389-4b6d44f18577: Failed to lock chroot:
> > /dev/fastvg/f13lv: Failed to lock device: Failed to lock device
> >
> > This issue can also be reproduced in schroot 1.4.2
> >
> > Additional details are available in Fedora bug 600638 here:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=600636
> >
> > The patch proposed there consists of moving the setuid call to an earlier
> > point before the call to lockdev is made.
>
> Hi Zach,
>
> This is not a bug in schroot. It's a bug in lockdev, specifically a
> patch to lockdev added in RedHat/Fedora which breaks setuid programs.
> schroot works fine using the vanilla upstream/Debian lockdev without
> this patch.
>
> This is the patch:
>
> http://lists.alioth.debian.org/pipermail/lockdev-devel/2010-February/000013.html
> and this is my review with the rationale:
>
> http://lists.alioth.debian.org/pipermail/lockdev-devel/2010-February/000039.html
> and here's a previous finder of this issue in CentOS:
> http://www.nikhef.nl/~dennisvd/schroot.html
Bug reported against lockdev in Fedora bugzilla. Closing this here
since it's not an schroot issue.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature
--- End Message ---
