linux-kernel - Re: [PATCH 5/9] Make use of permissions, returned by kobj

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47D11068.9010704@openvz.org>
Date:	Fri, 07 Mar 2008 12:52:40 +0300
From:	Pavel Emelyanov <xemul@...nvz.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	linux-kernel@...r.kernel.org, menage@...gle.com,
	sukadev@...ibm.com, serue@...ibm.com, Greg KH <greg@...ah.com>
Subject: Re: [PATCH 5/9] Make use of permissions, returned by kobj_lookup

Andrew Morton wrote:
> On Fri, 07 Mar 2008 12:22:01 +0300 Pavel Emelyanov <xemul@...nvz.org> wrote:
> 
>>> This doesn't include sufficient headers to be compileable.
>>>
>>> I'm sure there are lots of headers like this.  But we regularly need
>>> to fix them.
>>>
>> Not sure, whether this is still relevant after Greg's comments, but that's
>> the -fix patch for this one. (It will cause a conflict with the 9th patch.)
> 
> Well.  Where do we stand with this?  afaict the state of play is:
> 
> Greg: do it in udev
> Pavel: but people want to run old distros in containers

Actually no.

Greg: Use LSM for this
Pavel: My approach just makes maps per-group, while LSM will
       bring a new level of filtering/lookup on device open path

> Realistically, when is the mainline kernel likely to have sufficient
> container functionality which is sufficiently well-tested for people to
> actually be able to do that?  And how much longer will it take for that
> kernel.org functionality to propagate out into non-bleeding-edge distros?

The fact is that we have users of OpenVZ and even Virtuozzo, that still use 
redhat-9 as in containers. So even if this is ready in 5 years, there will 
always be someone who sets the outdated (by that time) fedora-core-8 and find
out, that his udev refuses to work.

> Altogether we're looking at one to three years, aren't we?  By then,
> perhaps a lot of "old" distros are already udev-based.
> 
> otoh, my experience upgrading old kernels to new udev has not been a
> good one (ie: it didn't work).

Agree, but we're talking about making old udev working with new kernel.

> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/