From: Marco Elver <elver@google.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@lists.01.org, kernel test robot <lkp@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [peterz-queue:perf/core 18/22] kernel/events/core.c:6418:22: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Wed, 14 Apr 2021 16:33:22 +0200 [thread overview]
Message-ID: <YHb9Mi1IwY5qtJxp@elver.google.com> (raw)
In-Reply-To: <202104142209.hLOfOONR-lkp@intel.com>
On Wed, Apr 14, 2021 at 10:10PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/core
> head: 0da503cd07380952599b67ded6efe030d78ea42d
> commit: c7d4112e9f0e69edd649665836ce72008b95ab9f [18/22] perf: Add support for SIGTRAP on perf events
[...]
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
[...]
> 6416 info.si_errno = event->attr.type;
> 6417 info.si_perf = event->attr.sig_data;
> > 6418 info.si_addr = (void *)event->sig_addr;
> 6419 force_sig_info(&info);
I think it wants the below (feel free to squash into "perf: Add support
for SIGTRAP on perf events").
Thanks,
-- Marco
------ >8 ------
From: Marco Elver <elver@google.com>
Date: Wed, 14 Apr 2021 16:26:26 +0200
Subject: [PATCH] perf: Fix cast to void __user pointer
sparse let us know that si_addr is 'void __user *', therefore add the
missing __user attribute to the cast.
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Marco Elver <elver@google.com>
---
kernel/events/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 1d2077389c0c..2677438ed668 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -6414,7 +6414,7 @@ static void perf_sigtrap(struct perf_event *event)
info.si_code = TRAP_PERF;
info.si_errno = event->attr.type;
info.si_perf = event->attr.sig_data;
- info.si_addr = (void *)event->sig_addr;
+ info.si_addr = (void __user *)event->sig_addr;
force_sig_info(&info);
}
--
2.31.1.295.g9ea45b61b8-goog
next parent reply other threads:[~2021-04-14 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202104142209.hLOfOONR-lkp@intel.com>
2021-04-14 14:33 ` Marco Elver [this message]
2021-04-15 8:48 ` Peter Zijlstra
2021-04-15 9:03 ` Marco Elver
2021-04-15 9:11 ` Peter Zijlstra
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=YHb9Mi1IwY5qtJxp@elver.google.com \
--to=elver@google.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=peterz@infradead.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
Powered by JetHome