All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	b.a.t.m.a.n@lists.open-mesh.org, VEfanov@ispras.ru,
	stable@kernel.org
Subject: Re: [PATCH 1/1] batman-adv: Broken sync while rescheduling delayed work
Date: Thu, 08 Jun 2023 05:00:22 +0000	[thread overview]
Message-ID: <168620042291.23382.13609079860562597568.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230607155515.548120-2-sw@simonwunderlich.de>

Hello:

This patch was applied to netdev/net.git (main)
by Simon Wunderlich <sw@simonwunderlich.de>:

On Wed,  7 Jun 2023 17:55:15 +0200 you wrote:
> From: Vladislav Efanov <VEfanov@ispras.ru>
> 
> Syzkaller got a lot of crashes like:
> KASAN: use-after-free Write in *_timers*
> 
> All of these crashes point to the same memory area:
> 
> [...]

Here is the summary with links:
  - [1/1] batman-adv: Broken sync while rescheduling delayed work
    https://git.kernel.org/netdev/net/c/abac3ac97fe8

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



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	b.a.t.m.a.n@lists.open-mesh.org, VEfanov@ispras.ru,
	stable@kernel.org, sven@narfation.org
Subject: Re: [PATCH 1/1] batman-adv: Broken sync while rescheduling delayed work
Date: Thu, 08 Jun 2023 05:00:22 +0000	[thread overview]
Message-ID: <168620042291.23382.13609079860562597568.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230607155515.548120-2-sw@simonwunderlich.de>

Hello:

This patch was applied to netdev/net.git (main)
by Simon Wunderlich <sw@simonwunderlich.de>:

On Wed,  7 Jun 2023 17:55:15 +0200 you wrote:
> From: Vladislav Efanov <VEfanov@ispras.ru>
> 
> Syzkaller got a lot of crashes like:
> KASAN: use-after-free Write in *_timers*
> 
> All of these crashes point to the same memory area:
> 
> [...]

Here is the summary with links:
  - [1/1] batman-adv: Broken sync while rescheduling delayed work
    https://git.kernel.org/netdev/net/c/abac3ac97fe8

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



  reply	other threads:[~2023-06-08  6:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 15:55 [PATCH 0/1] pull request for net: batman-adv 2023-06-07 Simon Wunderlich
2023-06-07 15:55 ` Simon Wunderlich
2023-06-07 15:55 ` [PATCH 1/1] batman-adv: Broken sync while rescheduling delayed work Simon Wunderlich
2023-06-08  5:00   ` patchwork-bot+netdevbpf [this message]
2023-06-08  5:00     ` patchwork-bot+netdevbpf
2023-06-08  5:01   ` Jakub Kicinski
2023-06-08  5:01     ` Jakub Kicinski
2023-06-08  5:24     ` Keller, Jacob E
2023-06-08  5:24       ` Keller, Jacob E
2023-06-08  9:01       ` Vlad Efanov
2023-06-08  9:01         ` Vlad Efanov
2023-06-08  9:27     ` Paolo Abeni
2023-06-08  9:27       ` Paolo Abeni
2023-06-08 16:57       ` Sven Eckelmann

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=168620042291.23382.13609079860562597568.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=VEfanov@ispras.ru \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=sw@simonwunderlich.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.