From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Hillf Danton <hdanton@sina.com>
Cc: "Wangshaobo (bobo)" <bobo.shaobowang@huawei.com>,
cj.chengjian@huawei.com, Wei Yongjun <weiyongjun1@huawei.com>,
yuehaibing@huawei.com, huawei.libin@huawei.com,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
syzbot <syzbot+664818c59309176d03ee@syzkaller.appspotmail.com>,
syzbot <syzbot+9a0875bc1b2ca466b484@syzkaller.appspotmail.com>
Subject: Re: [PATCH v2] Bluetooth: fix use-after-free error in lock_sock_nested()
Date: Tue, 20 Jul 2021 08:46:55 -0700 [thread overview]
Message-ID: <CABBYNZKaNM=koHZ1X=D1_jD9NvEdYN4Be5mH5hAghHG2tkgCHA@mail.gmail.com> (raw)
In-Reply-To: <20210720062100.819-1-hdanton@sina.com>
Hi Hillf,
On Mon, Jul 19, 2021 at 11:21 PM Hillf Danton <hdanton@sina.com> wrote:
>
> On Mon, 19 Jul 2021 21:24:30 -0700 Luiz Augusto von Dentz wrote:
> >
> >While Im fine adding a destroy callback the kfree shall be still in
> >l2cap_chan_destroy:
>
> Then feel free to send a tiny patchset to linux-bluetooth@vger.
What do you mean, we haven't applied your changes yet.
--
Luiz Augusto von Dentz
prev parent reply other threads:[~2021-07-20 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 2:49 [PATCH v2] Bluetooth: fix use-after-free error in lock_sock_nested() Wang ShaoBo
2021-07-19 3:13 ` [v2] " bluez.test.bot
[not found] ` <20210719074829.2554-1-hdanton@sina.com>
2021-07-19 9:03 ` [PATCH v2] " Wangshaobo (bobo)
[not found] ` <20210720021619.621-1-hdanton@sina.com>
2021-07-20 4:24 ` Luiz Augusto von Dentz
[not found] ` <20210720062100.819-1-hdanton@sina.com>
2021-07-20 15:46 ` Luiz Augusto von Dentz [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='CABBYNZKaNM=koHZ1X=D1_jD9NvEdYN4Be5mH5hAghHG2tkgCHA@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=bobo.shaobowang@huawei.com \
--cc=cj.chengjian@huawei.com \
--cc=hdanton@sina.com \
--cc=huawei.libin@huawei.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+664818c59309176d03ee@syzkaller.appspotmail.com \
--cc=syzbot+9a0875bc1b2ca466b484@syzkaller.appspotmail.com \
--cc=weiyongjun1@huawei.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 NNTP newsgroup(s).