From: patchwork-bot+bluetooth@kernel.org
To: Soenke Huster <soenke.huster@eknoes.de>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 RESEND] Bluetooth: virtio_bt: Use skb_put to set length
Date: Wed, 12 Oct 2022 20:00:15 +0000 [thread overview]
Message-ID: <166560481549.27468.13272780946907639506.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221012074507.8157-1-soenke.huster@eknoes.de>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 12 Oct 2022 09:45:06 +0200 you wrote:
> By using skb_put we ensure that skb->tail is set
> correctly. Currently, skb->tail is always zero, which
> leads to errors, such as the following page fault in
> rfcomm_recv_frame:
>
> BUG: unable to handle page fault for address: ffffed1021de29ff
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> RIP: 0010:rfcomm_run+0x831/0x4040 (net/bluetooth/rfcomm/core.c:1751)
>
> [...]
Here is the summary with links:
- [v2,RESEND] Bluetooth: virtio_bt: Use skb_put to set length
https://git.kernel.org/bluetooth/bluetooth-next/c/6ab8872f1976
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-10-12 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 7:05 [PATCH v2] Bluetooth: virtio_bt: Use skb_put to set length Soenke Huster
2022-07-27 8:05 ` [v2] " bluez.test.bot
2022-10-12 7:45 ` [PATCH v2 RESEND] " Soenke Huster
2022-10-12 8:21 ` [v2,RESEND] " bluez.test.bot
2022-10-12 20:00 ` patchwork-bot+bluetooth [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=166560481549.27468.13272780946907639506.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=soenke.huster@eknoes.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox