From: patchwork-bot+netdevbpf@kernel.org
To: Zhengchao Shao <shaozhengchao@huawei.com>
Cc: linux-x25@vger.kernel.org, netdev@vger.kernel.org, ms@dev.tdt.de,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, xie.he.0141@gmail.com, weiyongjun1@huawei.com,
yuehaibing@huawei.com
Subject: Re: [PATCH net] net: lapbether: fix issue of invalid opcode in lapbeth_open()
Date: Tue, 08 Nov 2022 12:30:15 +0000 [thread overview]
Message-ID: <166791061529.27754.528965881676739737.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221107011445.207372-1-shaozhengchao@huawei.com>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 7 Nov 2022 09:14:45 +0800 you wrote:
> If lapb_register() failed when lapb device goes to up for the first time,
> the NAPI is not disabled. As a result, the invalid opcode issue is
> reported when the lapb device goes to up for the second time.
>
> The stack info is as follows:
> [ 1958.311422][T11356] kernel BUG at net/core/dev.c:6442!
> [ 1958.312206][T11356] invalid opcode: 0000 [#1] PREEMPT SMP KASAN
> [ 1958.315979][T11356] RIP: 0010:napi_enable+0x16a/0x1f0
> [ 1958.332310][T11356] Call Trace:
> [ 1958.332817][T11356] <TASK>
> [ 1958.336135][T11356] lapbeth_open+0x18/0x90
> [ 1958.337446][T11356] __dev_open+0x258/0x490
> [ 1958.341672][T11356] __dev_change_flags+0x4d4/0x6a0
> [ 1958.345325][T11356] dev_change_flags+0x93/0x160
> [ 1958.346027][T11356] devinet_ioctl+0x1276/0x1bf0
> [ 1958.346738][T11356] inet_ioctl+0x1c8/0x2d0
> [ 1958.349638][T11356] sock_ioctl+0x5d1/0x750
> [ 1958.356059][T11356] __x64_sys_ioctl+0x3ec/0x1790
> [ 1958.365594][T11356] do_syscall_64+0x35/0x80
> [ 1958.366239][T11356] entry_SYSCALL_64_after_hwframe+0x46/0xb0
> [ 1958.377381][T11356] </TASK>
>
> [...]
Here is the summary with links:
- [net] net: lapbether: fix issue of invalid opcode in lapbeth_open()
https://git.kernel.org/netdev/net/c/3faf7e14ec0c
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:[~2022-11-08 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 1:14 [PATCH net] net: lapbether: fix issue of invalid opcode in lapbeth_open() Zhengchao Shao
2022-11-08 12:30 ` 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=166791061529.27754.528965881676739737.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=ms@dev.tdt.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaozhengchao@huawei.com \
--cc=weiyongjun1@huawei.com \
--cc=xie.he.0141@gmail.com \
--cc=yuehaibing@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).