User: Password:
|
|
Subscribe / Log in / New account

Yama: not so fast

Yama: not so fast

Posted Aug 5, 2010 21:19 UTC (Thu) by kees (subscriber, #27264)
In reply to: Yama: not so fast by MattPerry
Parent article: Yama: not so fast

While I'd like to think that waiting will work, I suspect only constant pressure will get any traction. Lucky for me, I don't have to waste any time writing code since I've already implemented this stuff both in the core and as an LSM. ;)

All my time will be wasted trying to convince people that the changes have value. I'm still stunned that it's not obvious based on all the evidence.


(Log in to post comments)

Yama: not so fast

Posted Aug 6, 2010 11:59 UTC (Fri) by nix (subscriber, #2304) [Link]

But you're only plugging holes which can more easily be plugged by fixing several hundreds of thousands of broken userspace apps. The latter is surely faster than writing one not terribly large kernel patch.

Or something.

(No, I can't figure out what their rationale could be, either. I note that nobody has come up with a single case, even an academic one, which your /tmp-race-fixing restrictions would break. But it's apparently unacceptable anyway.)

Yama: not so fast

Posted Aug 13, 2010 15:01 UTC (Fri) by renox (subscriber, #23785) [Link]

I think that this kind of situation is easier to solve with a 'face to face' meeting(*) than by email: it's far too easy for these 'finger pointing' situations to arrive with remote discussion.

I hope that you'll keep applying pressure and be able to participate to the right 'real life' kernel meetings to resolve things.

*: provided there are not too many people in the meeting and that the 'right' people are here.


Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds