From: Karel Zak <kzak@redhat.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Nitin Gupta <ngupta@vflare.org>,
linux-kernel@vger.kernel.org,
Jerome Marchand <jmarchan@redhat.com>
Subject: Re: [PATCH 0/2] make automatic device_id generation possible
Date: Thu, 5 Mar 2015 13:10:10 +0100 [thread overview]
Message-ID: <20150305121010.GY8046@ws.net.home> (raw)
In-Reply-To: <20150305020436.GB5041@blaptop>
On Thu, Mar 05, 2015 at 11:04:36AM +0900, Minchan Kim wrote:
> On Thu, Mar 05, 2015 at 10:47:52AM +0900, Sergey Senozhatsky wrote:
> > On (03/05/15 10:33), Minchan Kim wrote:
> > > > 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.
> >
> > we upgraded our scripts but landed some bugs there? it's up to particular
> > implementation. in your example, I assume, someone used zram with num_devices >= 1000?
> > that's impossible. current num_devices limitation is 32. and uid-s start from 1000.
>
> I meant it.
> If we support use-defined id and someone have used your idea so he can make zram
> per-user as uid. After a while, new application stats automatic id assignment
> so upcoming users can consume upcoming user id. yeah, automaic id will start
> from 0 so it's very rare to reach 1000 but who knows?
Why 1000?
The UID_MIN and UID_MAX is nothing strictly defined, it's just option
in /etc/login.defs. I guess it's nothing unusually to have system
where UID_MIN is 500 :-)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-03-05 12:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 14:16 [PATCH 0/2] make automatic device_id generation possible Sergey Senozhatsky
2015-03-04 14:16 ` [PATCH 1/2] zram: return zram device_id value from zram_add() Sergey Senozhatsky
2015-03-04 14:16 ` [PATCH 2/2] zram: introduce automatic device_id generation Sergey Senozhatsky
2015-03-04 22:13 ` Andrew Morton
2015-03-05 0:09 ` Sergey Senozhatsky
2015-03-05 0:20 ` [PATCH 0/2] make automatic device_id generation possible Minchan Kim
2015-03-05 0:58 ` Sergey Senozhatsky
2015-03-05 1:17 ` Minchan Kim
2015-03-05 1:36 ` Sergey Senozhatsky
2015-03-05 1:20 ` Sergey Senozhatsky
2015-03-05 1:33 ` Minchan Kim
2015-03-05 1:47 ` Sergey Senozhatsky
2015-03-05 2:04 ` Minchan Kim
2015-03-05 2:27 ` Sergey Senozhatsky
2015-03-05 2:35 ` Minchan Kim
2015-03-05 12:10 ` Karel Zak [this message]
2015-03-05 12:31 ` Sergey Senozhatsky
2015-03-05 12:02 ` Karel Zak
2015-03-05 12:26 ` Sergey Senozhatsky
2015-03-05 12:03 ` Sergey Senozhatsky
2015-03-06 3:31 ` Sergey Senozhatsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150305121010.GY8046@ws.net.home \
--to=kzak@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jmarchan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.