utsname.h: make new_utsname fields use the proper length constant
The members of the new_utsname structure are defined with magic numbers that *should* correspond to the constant __NEW_UTS_LEN+1. Everywhere else, code assumes this and uses the constant, so this patch makes the structure match. Originally suggested by Serge here: https://lists.linux-foundation.org/pipermail/containers/2009-March/016258.html Signed-off-by: Dan Smith <danms@us.ibm.com> Acked-by: Serge Hallyn <serue@us.ibm.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
b08cd961cc
commit
a7d932af06
|
@ -22,12 +22,12 @@ struct old_utsname {
|
|||
};
|
||||
|
||||
struct new_utsname {
|
||||
char sysname[65];
|
||||
char nodename[65];
|
||||
char release[65];
|
||||
char version[65];
|
||||
char machine[65];
|
||||
char domainname[65];
|
||||
char sysname[__NEW_UTS_LEN + 1];
|
||||
char nodename[__NEW_UTS_LEN + 1];
|
||||
char release[__NEW_UTS_LEN + 1];
|
||||
char version[__NEW_UTS_LEN + 1];
|
||||
char machine[__NEW_UTS_LEN + 1];
|
||||
char domainname[__NEW_UTS_LEN + 1];
|
||||
};
|
||||
|
||||
#ifdef __KERNEL__
|
||||
|
|
Loading…
Reference in New Issue