| 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
| ||
|
Message-ID: <20150305013301.GA5041@blaptop> Date: Thu, 5 Mar 2015 10:33:02 +0900 From: Minchan Kim <minchan@...nel.org> To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Nitin Gupta <ngupta@...are.org>, linux-kernel@...r.kernel.org, Jerome Marchand <jmarchan@...hat.com> Subject: Re: [PATCH 0/2] make automatic device_id generation possible On Thu, Mar 05, 2015 at 10:20:43AM +0900, Sergey Senozhatsky wrote: > On (03/05/15 09:58), Sergey Senozhatsky wrote: > > /* yet "/dev/zram$(id -u)" thing looks interesting */ > > > > hm, I can think of a huge build server with tons of users. /dev/zram$(id -u) > created during user login and destroyed during logout. so users use theirs own > zram devices with predictable device ids (which also makes it simpler for admin) > for compilation/etc., and don't pressure hdds that much. They upgraded the system and from now on, one of app tries automatic id with zram for some reason. What happens if he gets some user id before the user login? The system should have fallback in the case of failing to create own userid assignment. Hmm, Coexisting specific and automatic id assign seem to be not a godd idea. > > -ss -- Kind regards, Minchan Kim -- 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/
Powered by blists - more mailing lists