From: Kees Cook <keescook@chromium.org>
To: Chris Zankel <chris@zankel.net>, Max Filippov <jcmvbkbc@gmail.com>
Cc: linux-xtensa@linux-xtensa.org, linux-hardening@vger.kernel.org
Subject: How large is the xtensa pt_regs::areg array supposed to be?
Date: Wed, 2 Feb 2022 15:03:51 -0800 [thread overview]
Message-ID: <202202021501.DA6594BFC@keescook> (raw)
Hi,
When building with -Warray-bounds, I see this:
In file included from ./include/linux/uaccess.h:11,
from ./include/linux/sched/task.h:11,
from arch/xtensa/kernel/process.c:21:
arch/xtensa/kernel/process.c: In function 'copy_thread':
arch/xtensa/kernel/process.c:262:52: warning: array subscript 53 is above array bounds of 'long unsigned int[16]' [-Warray-bounds]
262 | put_user(regs->areg[caller_ars+1],
./arch/xtensa/include/asm/uaccess.h:171:18: note: in definition of macro '__put_user_asm'
171 | :[x] "r"(x_), [efault] "i"(-EFAULT))
| ^~
./arch/xtensa/include/asm/uaccess.h:89:17: note: in expansion of macro '__put_user_size'
89 | __put_user_size((x), __pu_addr, (size), __pu_err); \
| ^~~~~~~~~~~~~~~
./arch/xtensa/include/asm/uaccess.h:62:33: note: in expansion of macro '__put_user_check'
62 | #define put_user(x, ptr) __put_user_check((x), (ptr), sizeof(*(ptr)))
| ^~~~~~~~~~~~~~~~
arch/xtensa/kernel/process.c:262:33: note: in expansion of macro 'put_user'
262 | put_user(regs->areg[caller_ars+1],
| ^~~~~~~~
In file included from ./arch/xtensa/include/asm/processor.h:17,
from ./arch/xtensa/include/asm/thread_info.h:20,
from ./arch/xtensa/include/asm/current.h:14,
from ./include/linux/sched.h:12,
from arch/xtensa/kernel/process.c:19:
./arch/xtensa/include/asm/ptrace.h:80:23: note: while referencing 'areg'
80 | unsigned long areg[16];
| ^~~~
The code is:
int callinc = (regs->areg[0] >> 30) & 3;
int caller_ars = XCHAL_NUM_AREGS - callinc * 4;
put_user(regs->areg[caller_ars+1],
(unsigned __user*)(usp - 12));
It looks like XCHAL_NUM_AREGS is larger than "16", though?
struct pt_regs {
...
unsigned long areg[16];
What should be happening here?
Thanks!
--
Kees Cook
next reply other threads:[~2022-02-02 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 23:03 Kees Cook [this message]
2022-02-03 21:13 ` How large is the xtensa pt_regs::areg array supposed to be? Max Filippov
2022-02-03 21:56 ` Kees Cook
2022-02-04 0:05 ` Max Filippov
2022-03-05 20:43 ` Max Filippov
2022-03-06 1:50 ` Max Filippov
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=202202021501.DA6594BFC@keescook \
--to=keescook@chromium.org \
--cc=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox