From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>, Marco Elver <elver@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Tomas Gleixner <tglx@linutronix.de>,
Vlastimil Babka <vbabka@suse.cz>,
akpm@linux-foundation.org, cl@linux.com, iamjoonsoo.kim@lge.com,
longman@redhat.com, penberg@kernel.org, rientjes@google.com,
sfr@canb.auug.org.au
Subject: [PATCH v2 0/3] scftorture: Avoid kfree from IRQ context.
Date: Thu, 7 Nov 2024 12:13:05 +0100 [thread overview]
Message-ID: <20241107111821.3417762-1-bigeasy@linutronix.de> (raw)
Hi,
Paul reported kfree from IRQ context in scftorture which is noticed by
lockdep since the recent PROVE_RAW_LOCK_NESTING switch.
The last patch in this series adresses the issues, the other things
happened on the way.
v1…v2:
- Remove kfree_bulk(). I get more invocations per report without it.
- Pass `cpu' to scf_cleanup_free_list in scftorture_invoker() instead
of scfp->cpu. The latter is the thread number which can be larger
than the number CPUs leading to a crash in such a case. Reported by
Boqun Feng.
- Clean up the per-CPU lists on module exit. Reported by Boqun Feng.
Sebastian
next reply other threads:[~2024-11-07 11:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 11:13 Sebastian Andrzej Siewior [this message]
2024-11-07 11:13 ` [PATCH v2 1/3] scftorture: Avoid additional div operation Sebastian Andrzej Siewior
2024-11-07 11:13 ` [PATCH v2 2/3] scftorture: Move memory allocation outside of preempt_disable region Sebastian Andrzej Siewior
2024-11-07 11:13 ` [PATCH v2 3/3] scftorture: Use a lock-less list to free memory Sebastian Andrzej Siewior
2024-11-07 18:31 ` Paul E. McKenney
2024-11-07 20:45 ` Boqun Feng
2024-11-07 21:53 ` Paul E. McKenney
2024-11-08 10:32 ` Sebastian Andrzej Siewior
2024-11-07 15:27 ` [PATCH v2 4/3] scftorture: Wait until scf_cleanup_handler() completes Sebastian Andrzej Siewior
2024-11-07 19:05 ` [PATCH v2 0/3] scftorture: Avoid kfree from IRQ context Paul E. McKenney
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=20241107111821.3417762-1-bigeasy@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--cc=cl@linux.com \
--cc=elver@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=paulmck@kernel.org \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
/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