From: Sven Eckelmann <sven@narfation.org>
To: "박수완 / 학생 / 컴퓨터공학부" <swan2718@snu.ac.kr>
Cc: b.a.t.m.a.n@lists.open-mesh.org, netdev@vger.kernel.org,
marek.lindner@mailbox.org, sw@simonwunderlich.de,
antonio@mandelbit.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] batman-adv: fix DAT purge use-after-free on teardown
Date: Tue, 26 May 2026 16:18:05 +0200 [thread overview]
Message-ID: <10856691.nUPlyArG6x@ripper> (raw)
In-Reply-To: <CAL3z5EbfEeMn-2_JrvcXRtuKTtruEf+8MX9tCmn-N9edvvrjwA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On Tuesday, 26 May 2026 15:56:58 CEST 박수완 / 학생 / 컴퓨터공학부 wrote:
> Hi Sven,
>
> You're right. I re-examined __cancel_work_sync() and confirmed that it
> internally disables the work before flushing, so the re-queue race I
> described does not exist. I'll withdraw this patch.
>
> Thanks for the review.
But you said that this was reported by syzkaller. I can't find the report in
the official list [1]. I am guessing you have a reproducer in a private
instance and tested with it. And if you tested your patch with it, you have
found that your patch fixes it, right?
Can you give us more information about this to let us figure out what is
actually going on?
Regards,
Sven
[1] https://syzkaller.appspot.com/upstream/s/batman
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-05-26 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 6:48 [PATCH] batman-adv: fix DAT purge use-after-free on teardown Soowan Park
2026-05-26 7:30 ` Sven Eckelmann
2026-05-26 13:56 ` 박수완 / 학생 / 컴퓨터공학부
2026-05-26 14:18 ` Sven Eckelmann [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=10856691.nUPlyArG6x@ripper \
--to=sven@narfation.org \
--cc=antonio@mandelbit.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=marek.lindner@mailbox.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sw@simonwunderlich.de \
--cc=swan2718@snu.ac.kr \
--cc=tj@kernel.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