linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Fernandes <joel@joelfernandes.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Xiao Yang <yangx.jy@cn.fujitsu.com>,
	linux-kselftest@vger.kernel.org,
	linux-trace-devel@vger.kernel.org,
	Xiao Yang <ice_yangxiao@163.com>
Subject: Re: preemptirq_delay_test module can trigger crash on arm64 vm
Date: Fri, 24 Apr 2020 18:19:50 -0400	[thread overview]
Message-ID: <20200424221950.GA162750@google.com> (raw)
In-Reply-To: <20200424100146.786bcd7f@gandalf.local.home>

On Fri, Apr 24, 2020 at 10:01:46AM -0400, Steven Rostedt wrote:
> On Fri, 24 Apr 2020 17:26:32 +0800
> Xiao Yang <yangx.jy@cn.fujitsu.com> wrote:
> 
> > Hi Steve, Joel
> > 
> > Sorry to bother you.
> > 
> > On my slow arm64 vm, inserting and removing preemptirq_delay_test module
> > in loops triggers kernel panic sometimes.
> > 
> > Reproduce steps:
> > Do the following steps in loops(more than 10 times):
> > [root@CentOS81-aarch64 ]# modprobe preemptirq_delay_test
> > test_mode=preempt delay=500000; rmmod preemptirq_delay_test
> > 
> >
> 
> Joel,
> 
> I never did really look at that module, but doing a quick scan, I see you
> never clean up the task you start.
> 
> Which means, you can remove the module and the task still exists, and when
> it runs, it will execute code that has been freed.
> 
> The module exit should still do a kthread_stop() on it. If anything, it
> will prevent the task existing after the module is removed.

Thanks Steve for taking a look, I will submit a fix for it ASAP and send it to you
for -rc cycle. Thanks Xiao for the report.

 - Joel


      reply	other threads:[~2020-04-24 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24  9:26 preemptirq_delay_test module can trigger crash on arm64 vm Xiao Yang
2020-04-24 14:01 ` Steven Rostedt
2020-04-24 22:19   ` Joel Fernandes [this message]

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=20200424221950.GA162750@google.com \
    --to=joel@joelfernandes.org \
    --cc=ice_yangxiao@163.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=yangx.jy@cn.fujitsu.com \
    /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;
as well as URLs for NNTP newsgroup(s).