Skip to contentSkip to conversation

2.6.6-mm2

DISCUSSION Andy Lutomirski 2 participants 2 messages May 14, 2004 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 15 lines · Chris Wright
Quoted 11 lines · * Andrew Morton ([email protected]) wrote:
Quoted 6 lines · Christoph Hellwig
Quoted 3 lines

+hugetlb_shm_group-sysctl-gid-0-fix.patch

Don't make gid 0 special for hugetlb shm.

As Oracle has agreed on fixing their DB to use hugetlbfs could we please stop doctoring around on this broken patch and revert it.

Once I'm convinced that kernel.org kernels will be able to run applications which vendor kernels will run, sure.

Quoted 5 lines

What about something that's just simple and generic? This is similar to Andrea's disable_cap_mlock patch and the disabling capabilities patch that wli produced back in that thread. It would remove the hack, and buy us some time to find better solutions. Downside of course (as all of these have) is reduced security value.

I actually like the magic group better. This one means that _anyone_ can DoS the system. Why not just give Oracle its own LSM if this is what you want to do (that way the nastiness is completely isolated)?

<shameless_plug> My patch (posted a couple hours ago) solves this one cleanly </shameless_plug>

--And

#3 lore raw
Quoted 10 lines · * Andy Lutomirski ([email protected]) wrote:
Quoted 5 lines · Chris Wright

What about something that's just simple and generic? This is similar to Andrea's disable_cap_mlock patch and the disabling capabilities patch that wli produced back in that thread. It would remove the hack, and buy us some time to find better solutions. Downside of course (as all of these have) is reduced security value.

I actually like the magic group better. This one means that _anyone_ can DoS the system. Why not just give Oracle its own LSM if this is what you want to do (that way the nastiness is completely isolated)?

Magic group has better safety property, but it evolved from disable_cap_mlock which for CAP_IPC_LOCK has the identical property to this patch. Agreed it's safer w/out, but the magic group is so special purpose that it feels like a hack. This patch is more contained and IMO is just a hold over until we have something that really works.

Quoted 2 lines

<shameless_plug> My patch (posted a couple hours ago) solves this one cleanly </shameless_plug>

I'll comment on that separately ;-)

thanks,
-chris

Signature · 1 line
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net