From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH] context_tracking: Have ct_state() use preempt_disable_notrace()
Date: Tue, 21 Mar 2023 17:58:21 -0700 [thread overview]
Message-ID: <20230322005821.oh4pbn4vdf4jrdsh@treble> (raw)
In-Reply-To: <20230321204524.44733a13@gandalf.local.home>
On Tue, Mar 21, 2023 at 08:45:24PM -0400, Steven Rostedt wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
>
> One of my tests triggered:
>
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 1 at include/trace/events/preemptirq.h:51 trace_preempt_off+0x7c/0x80
> Modules linked in:
> CPU: 0 PID: 1 Comm: init Not tainted 6.3.0-rc3-test-00011-ge11b521a7b69-dirty #31
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-debian-1.16.0-5 04/01/2014
> RIP: 0010:trace_preempt_off+0x7c/0x80
> Code: 74 0f 48 8b 78 08 48 89 f2 48 89 de e8 5d f9 ff ff 65 ff 0d 6e d6 ce 68 75 a2 0f 1f 44 00 00 eb 9b e8 28 ea f3 ff 84 c0 75 a5 <0f> 0b eb a1 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f
> RSP: 0000:ffffaf0880013f00 EFLAGS: 00010046
> RAX: 0000000000000000 RBX: ffffffff97fafe59 RCX: 0000000000000001
> RDX: 0000000000000000 RSI: ffffffff986f4b71 RDI: ffffffff986fa0dd
> RBP: ffffffff97fafe59 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
> R13: 0000000000000014 R14: 0000000000000000 R15: 0000000000000000
> FS: 0000000000000000(0000) GS:ffff8adf7bc00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f125de099c0 CR3: 000000010498a001 CR4: 0000000000170ef0
> Call Trace:
> <TASK>
> irqentry_enter_from_user_mode+0x39/0x80
> irqentry_enter+0x51/0x60
> exc_page_fault+0x3d/0x200
> asm_exc_page_fault+0x26/0x30
I think this was just fixed in -tip today:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=f87d28673b71b35b248231a2086f9404afbb7f28
--
Josh
next prev parent reply other threads:[~2023-03-22 0:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 0:45 Steven Rostedt
2023-03-22 0:58 ` Josh Poimboeuf [this message]
2023-03-22 1:20 ` Steven Rostedt
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=20230322005821.oh4pbn4vdf4jrdsh@treble \
--to=jpoimboe@kernel.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®