From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Boqun Feng <boqun.feng@gmail.com>,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, 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: Re: [PATCH v3 0/4] scftorture: Avoid kfree from IRQ context.
Date: Fri, 8 Nov 2024 19:45:10 +0100 [thread overview]
Message-ID: <20241108184510.O8w42_-e@linutronix.de> (raw)
In-Reply-To: <18b237cf-d510-49bf-b21b-78f9cebd1e3d@paulmck-laptop>
On 2024-11-08 10:33:29 [-0800], Paul E. McKenney wrote:
> Sebastian, I am guessing that the Kconfig change exposing the bugs fixed
> by your series is headed to mainline for the upcoming merge window?
Yes. It is in tip/locking/core.
> If so, I should of course push these in as well.
That would be nice ;)
> Thanx, Paul
Sebastian
next prev parent reply other threads:[~2024-11-08 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 10:39 Sebastian Andrzej Siewior
2024-11-08 10:39 ` [PATCH v3 1/4] scftorture: Avoid additional div operation Sebastian Andrzej Siewior
2024-11-08 10:39 ` [PATCH v3 2/4] scftorture: Wait until scf_cleanup_handler() completes Sebastian Andrzej Siewior
2024-11-08 10:39 ` [PATCH v3 3/4] scftorture: Move memory allocation outside of preempt_disable region Sebastian Andrzej Siewior
2024-11-08 10:39 ` [PATCH v3 4/4] scftorture: Use a lock-less list to free memory Sebastian Andrzej Siewior
2024-11-08 17:46 ` [PATCH v3 0/4] scftorture: Avoid kfree from IRQ context Boqun Feng
2024-11-08 18:33 ` Paul E. McKenney
2024-11-08 18:45 ` Sebastian Andrzej Siewior [this message]
2024-11-08 19:01 ` 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=20241108184510.O8w42_-e@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