From: F6BVP <f6bvp@free.fr>
To: kartikey406@gmail.com
Cc: davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, linux-hams@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzbot+62360d745376b40120b5@syzkaller.appspotmail.com,
takamitz@amazon.co.jp, tglx@kernel.org
Subject: Re: [PATCH] rose: Fix use-after-free in rose_timer_expiry
Date: Mon, 19 Jan 2026 21:19:21 +0100 [thread overview]
Message-ID: <5a88b747-bb06-4ebd-99de-80ceb574cf22@free.fr> (raw)
In-Reply-To: <20260117063930.1256413-1-kartikey406@gmail.com>
Patch applied to rose_timer.c
Result is interesting even if
rose module cannot still be removed with rmmod command.
For a very long time rmmod would freeze the console and the task could
not be killed.
With the patch applied rmmod command is not blocked anymore.
However rose module is not removed probably because of a wrong refcount ?
lsmod | grep rose
rose 184320 -1
ax25 217088 1 rose
Bernard, f6bvp
next prev parent reply other threads:[~2026-01-19 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 6:39 [PATCH] rose: Fix use-after-free in rose_timer_expiry Deepanshu Kartikey
2026-01-19 20:19 ` F6BVP [this message]
2026-04-13 17:42 ` [PATCH net-next 1/3] rose: fix race between loopback timer and module removal f6bvp
2026-04-13 17:42 ` [PATCH net-next 2/3] rose: clear neighbour pointer after rose_neigh_put() in state machines f6bvp
2026-04-13 20:53 ` Jakub Kicinski
2026-04-13 17:42 ` [PATCH net-next 3/3] rose: guard rose_neigh_put() against NULL in timer expiry f6bvp
2026-04-13 21:21 ` [PATCH net-next 1/3] rose: fix race between loopback timer and module removal Andrew Lunn
2026-04-13 21:34 ` Jakub Kicinski
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=5a88b747-bb06-4ebd-99de-80ceb574cf22@free.fr \
--to=f6bvp@free.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kartikey406@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+62360d745376b40120b5@syzkaller.appspotmail.com \
--cc=takamitz@amazon.co.jp \
--cc=tglx@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