From: Thomas Gleixner <tglx@linutronix.de>
To: Rik van Riel <riel@surriel.com>, Yury Norov <yury.norov@gmail.com>
Cc: Jann Horn <jannh@google.com>,
syzbot <syzbot+084b6e5bc1016723a9c4@syzkaller.appspotmail.com>,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, luto@kernel.org, mingo@redhat.com,
neeraj.upadhyay@kernel.org, paulmck@kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
x86@kernel.org, kernel-team <kernel-team@meta.com>,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH] smp: Wait for enqueued work regardless of IPI sent
Date: Thu, 03 Jul 2025 18:56:11 +0200 [thread overview]
Message-ID: <87ikk9tdqs.ffs@tglx> (raw)
In-Reply-To: <20250702135954.7a00497d@fangorn>
On Wed, Jul 02 2025 at 13:59, Rik van Riel wrote:
> Thomas, please let me know if you already reverted Yury's patch,
> and want me to re-send this without the last hunk.
I did so immediately after saying so in my previous reply. It's gone in
tip and next.
Thanks,
tglx
next prev parent reply other threads:[~2025-07-03 16:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 13:50 [syzbot] [kernel?] KASAN: slab-use-after-free Write in flush_tlb_func syzbot
2025-07-02 15:20 ` Rik van Riel
2025-07-02 16:53 ` Jann Horn
2025-07-02 17:00 ` Jann Horn
2025-07-02 17:12 ` Thomas Gleixner
2025-07-02 17:44 ` Yury Norov
2025-07-02 17:59 ` [PATCH] smp: Wait for enqueued work regardless of IPI sent Rik van Riel
2025-07-03 13:52 ` Yury Norov
2025-07-03 16:56 ` Thomas Gleixner [this message]
2025-07-04 0:30 ` [PATCH v2] " Rik van Riel
2025-07-06 10:01 ` [tip: smp/core] smp: Wait only if work was enqueued tip-bot2 for Rik van Riel
2025-07-02 17:09 ` [syzbot] [kernel?] KASAN: slab-use-after-free Write in flush_tlb_func Rik van Riel
2025-07-02 17:23 ` Jann Horn
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=87ikk9tdqs.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=syzbot+084b6e5bc1016723a9c4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=x86@kernel.org \
--cc=yury.norov@gmail.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