From: syzbot <syzbot+4c0d0c4cde787116d465@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: [PATCH v1] Bluetooth: SCO: Use disable_delayed_work_sync
Date: Tue, 01 Oct 2024 12:50:10 -0700 [thread overview]
Message-ID: <66fc5272.050a0220.f28ec.04cb.GAE@google.com> (raw)
In-Reply-To: <000000000000797bd1060a457c08@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [PATCH v1] Bluetooth: SCO: Use disable_delayed_work_sync
Author: luiz.dentz@gmail.com
#syz test
On Tue, Oct 1, 2024 at 3:48 PM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This makes use of disable_delayed_work_sync instead
> cancel_delayed_work_sync as it not only cancel the ongoing work but also
> disables new submit which is disarable since the object holding the work
> is about to be freed.
>
> Reported-by: syzbot+4c0d0c4cde787116d465@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=4c0d0c4cde787116d465
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> ---
> net/bluetooth/sco.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/bluetooth/sco.c b/net/bluetooth/sco.c
> index a5ac160c592e..f0604d7834df 100644
> --- a/net/bluetooth/sco.c
> +++ b/net/bluetooth/sco.c
> @@ -208,7 +208,7 @@ static void sco_conn_del(struct hci_conn *hcon, int err)
> }
>
> /* Ensure no more work items will run before freeing conn. */
> - cancel_delayed_work_sync(&conn->timeout_work);
> + disable_delayed_work_sync(&conn->timeout_work);
>
> hcon->sco_data = NULL;
> kfree(conn);
> --
> 2.46.1
>
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2024-10-01 19:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 14:03 [syzbot] Test on mainline syzbot
2023-11-17 1:01 ` [syzbot] [PATCH] test uaf in sco_sock_timeout syzbot
2023-11-18 3:25 ` [syzbot] [PATCH] Test " syzbot
2023-12-06 3:58 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Write " syzbot
2024-10-01 19:50 ` syzbot [this message]
2024-10-02 18:27 ` [syzbot] Re: [PATCH v2] Bluetooth: SCO: Use disable_delayed_work_sync syzbot
2024-10-02 19:20 ` [syzbot] Re: [PATCH v3] " syzbot
2024-10-02 19:47 ` syzbot
2024-10-02 20:46 ` syzbot
2024-10-03 15:38 ` syzbot
2024-10-03 16:33 ` syzbot
2024-10-03 19:21 ` syzbot
2024-10-04 16:06 ` syzbot
2024-10-04 17:24 ` syzbot
2024-10-07 17:16 ` syzbot
2024-10-07 20:54 ` syzbot
2024-10-22 16:44 ` syzbot
2024-10-22 19:19 ` syzbot
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=66fc5272.050a0220.f28ec.04cb.GAE@google.com \
--to=syzbot+4c0d0c4cde787116d465@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 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.