Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Zhang Qilong <zhangqilong3@huawei.com>
Cc: ralf@linux-mips.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, f6bvp@free.fr,
	linux-hams@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] rose: Fix NULL pointer dereference in rose_send_frame()
Date: Wed, 02 Nov 2022 12:00:15 +0000	[thread overview]
Message-ID: <166739041570.9516.15064436041668449705.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221028161049.113625-1-zhangqilong3@huawei.com>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Sat, 29 Oct 2022 00:10:49 +0800 you wrote:
> The syzkaller reported an issue:
> 
> KASAN: null-ptr-deref in range [0x0000000000000380-0x0000000000000387]
> CPU: 0 PID: 4069 Comm: kworker/0:15 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
> Workqueue: rcu_gp srcu_invoke_callbacks
> RIP: 0010:rose_send_frame+0x1dd/0x2f0 net/rose/rose_link.c:101
> Call Trace:
>  <IRQ>
>  rose_transmit_clear_request+0x1d5/0x290 net/rose/rose_link.c:255
>  rose_rx_call_request+0x4c0/0x1bc0 net/rose/af_rose.c:1009
>  rose_loopback_timer+0x19e/0x590 net/rose/rose_loopback.c:111
>  call_timer_fn+0x1a0/0x6b0 kernel/time/timer.c:1474
>  expire_timers kernel/time/timer.c:1519 [inline]
>  __run_timers.part.0+0x674/0xa80 kernel/time/timer.c:1790
>  __run_timers kernel/time/timer.c:1768 [inline]
>  run_timer_softirq+0xb3/0x1d0 kernel/time/timer.c:1803
>  __do_softirq+0x1d0/0x9c8 kernel/softirq.c:571
>  [...]
>  </IRQ>
> 
> [...]

Here is the summary with links:
  - rose: Fix NULL pointer dereference in rose_send_frame()
    https://git.kernel.org/netdev/net/c/e97c089d7a49

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2022-11-02 12:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 16:10 [PATCH] rose: Fix NULL pointer dereference in rose_send_frame() Zhang Qilong
2022-11-02 12:00 ` patchwork-bot+netdevbpf [this message]
2022-11-05 19:07 ` F6BVP

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=166739041570.9516.15064436041668449705.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f6bvp@free.fr \
    --cc=kuba@kernel.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ralf@linux-mips.org \
    --cc=zhangqilong3@huawei.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