From: patchwork-bot+netdevbpf@kernel.org
To: Qingfang DENG <dqfext@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, yoshfuji@linux-ipv6.org, nakam@linux-ipv6.org,
vnuorval@tcs.hut.fi, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, qingfang.deng@siflower.com.cn
Subject: Re: [PATCH net v2] neighbour: fix unaligned access to pneigh_entry
Date: Fri, 02 Jun 2023 04:50:19 +0000 [thread overview]
Message-ID: <168568141998.21492.1839866290257514531.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230601015432.159066-1-dqfext@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 1 Jun 2023 09:54:32 +0800 you wrote:
> From: Qingfang DENG <qingfang.deng@siflower.com.cn>
>
> After the blamed commit, the member key is longer 4-byte aligned. On
> platforms that do not support unaligned access, e.g., MIPS32R2 with
> unaligned_action set to 1, this will trigger a crash when accessing
> an IPv6 pneigh_entry, as the key is cast to an in6_addr pointer.
>
> [...]
Here is the summary with links:
- [net,v2] neighbour: fix unaligned access to pneigh_entry
https://git.kernel.org/netdev/net/c/ed779fe4c9b5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-06-02 4:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANn89iKRX2QTgS44Ky6Jua-+UNrFY3E7RCT_7OfG=GnFvAzdFQ@mail.gmail.com>
2023-06-01 1:54 ` [PATCH net v2] neighbour: fix unaligned access to pneigh_entry Qingfang DENG
2023-06-02 4:50 ` patchwork-bot+netdevbpf [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=168568141998.21492.1839866290257514531.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nakam@linux-ipv6.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qingfang.deng@siflower.com.cn \
--cc=vnuorval@tcs.hut.fi \
--cc=yoshfuji@linux-ipv6.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