tree-wide: "<n>bit" → "<n>-bit"
In some places, "<n> bits" is used when more appropriate.
This commit is contained in:
committed by
Luca Boccassi
parent
221332ee13
commit
da89046643
@@ -37,7 +37,7 @@ bool uid_is_valid(uid_t uid) {
|
||||
if (uid == (uid_t) UINT32_C(0xFFFFFFFF))
|
||||
return false;
|
||||
|
||||
/* A long time ago UIDs where 16bit, hence explicitly avoid the 16bit -1 too */
|
||||
/* A long time ago UIDs where 16 bit, hence explicitly avoid the 16-bit -1 too */
|
||||
if (uid == (uid_t) UINT32_C(0xFFFF))
|
||||
return false;
|
||||
|
||||
@@ -765,14 +765,14 @@ bool valid_user_group_name(const char *u, ValidUserFlags flags) {
|
||||
if (in_charset(u, "0123456789")) /* Don't allow fully numeric strings, they might be confused
|
||||
* with UIDs (note that this test is more broad than
|
||||
* the parse_uid() test above, as it will cover more than
|
||||
* the 32bit range, and it will detect 65535 (which is in
|
||||
* the 32-bit range, and it will detect 65535 (which is in
|
||||
* invalid UID, even though in the unsigned 32 bit range) */
|
||||
return false;
|
||||
|
||||
if (u[0] == '-' && in_charset(u + 1, "0123456789")) /* Don't allow negative fully numeric
|
||||
* strings either. After all some people
|
||||
* write 65535 as -1 (even though that's
|
||||
* not even true on 32bit uid_t
|
||||
* not even true on 32-bit uid_t
|
||||
* anyway) */
|
||||
return false;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user