Commit a84a79e4d369a73c0130b5858199e949432da4c6

Authored by Linus Torvalds
1 parent 8bc03e8f3a

Avoid using variable-length arrays in kernel/sys.c

The size is always valid, but variable-length arrays generate worse code
for no good reason (unless the function happens to be inlined and the
compiler sees the length for the simple constant it is).

Also, there seems to be some code generation problem on POWER, where
Henrik Bakken reports that register r28 can get corrupted under some
subtle circumstances (interrupt happening at the wrong time?).  That all
indicates some seriously broken compiler issues, but since variable
length arrays are bad regardless, there's little point in trying to
chase it down.

"Just don't do that, then".

Reported-by: Henrik Grindal Bakken <henribak@cisco.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Showing 1 changed file with 1 additions and 1 deletions Side-by-side Diff

... ... @@ -1172,7 +1172,7 @@
1172 1172 static int override_release(char __user *release, int len)
1173 1173 {
1174 1174 int ret = 0;
1175   - char buf[len];
  1175 + char buf[65];
1176 1176  
1177 1177 if (current->personality & UNAME26) {
1178 1178 char *rest = UTS_RELEASE;