On 2011-04-12, Roger Leigh <rle...@codelibre.net> wrote: > Having multiple tmpfses with the kernel defaults means that a user or > badly written program could intentionally or accidentally lock up the > machine by using all available memory by filling up one or more of the > tmpfses. And the majority /are/ user writable by default, even /run > (via /var/lock, which is not a separate mount by default--maybe it > should be?). /dev/shm is user writable, /tmp is user writable.
How is that different from lock-ups due to fork bombs? If the admin cares, he can still fence his users. (Like DSA do on their machines by setting a sane tmpfs size limit.) Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrniq9d38.phd.tr...@kelgar.0x539.de
