On Tue, Feb 06, 2007 at 03:25:35PM -0800, Steve Langasek <[EMAIL PROTECTED]>
wrote:
> > (no kill -9), which cannot be a userspace problem unless you assume
> > libdevmapper opens /dev/mem and pokes into the kernel directly.
>
> Ok, that's fair, it's a kernel bug for allowing such a deadlock to occur;
> but it's also a userspace bug for doing something that deadlocks the kernel,
> and I don't think the kernel should bear the greater responsibility here.
Me neither, I think bugs should be fixed, I don't see how responsibility
figures in there :)
> > Right, but just for the sake of helping people who used the never released
> > and unsupported version of devmapper that likely many people using unstable
> > or testing still have installed and doesn't get upgraded it would make sense
> > to do that, won't you think?
>
> I think it's a fair request;
Thanks, thats actually all I am asking for :)
> it's just not release-critical, as you suggested in your bug severity.
I never suggested it was release-critical. reportbug suggested to use
critical because:
1 critical makes unrelated software on the system (or the whole system)
break, or causes serious data loss, or introduces a security hole on
systems where you install the package.
which is certainly true. if reportbug is mistaken, do you know a better
wording and do you think I should report this agains reportbug so it can
be fixed, if critical, in fact, means something else.
Thanks a lot!
--
The choice of a
-----==- _GNU_
----==-- _ generation Marc Lehmann
---==---(_)__ __ ____ __ [EMAIL PROTECTED]
--==---/ / _ \/ // /\ \/ / http://schmorp.de/
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
