From: joeyli <jlee@suse.com>
To: Weiteng Chen <wchen130@ucr.edu>, Yu Hao <yhao016@ucr.edu>
Cc: Yu Hao <yhao016@ucr.edu>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: How to reproduce the BUG general protection fault in hci_uart_tty_ioctl?
Date: Wed, 5 Jul 2023 16:41:48 +0800 [thread overview]
Message-ID: <20230705084148.GK5866@linux-l9pv.suse> (raw)
In-Reply-To: <191B9131-6E47-49B6-8089-108E2B12B9DC@ucr.edu>
Hi Weiteng Chen, Yu Hao,
On Mon, Jul 03, 2023 at 09:07:38PM -0700, Weiteng Chen wrote:
> Hi Joey,
>
> Sorry for my late response.
>
> https://elixir.bootlin.com/linux/v6.3-rc7/source/drivers/bluetooth/hci_ldisc.c#L764
>
> switch (cmd) {
> case HCIUARTSETPROTO:
> if (!test_and_set_bit(HCI_UART_PROTO_SET, &hu->flags)) {
> printk(“test_and_set_bit…”) // insert a prink to make the race easy to trigger
> err = hci_uart_set_proto(hu, arg);
> if (err)
> clear_bit(HCI_UART_PROTO_SET, &hu->flags);
> } else
> err = -EBUSY;
> break;
>
> case HCIUARTGETPROTO:
> if (test_bit(HCI_UART_PROTO_SET, &hu->flags))
> err = hu->proto->id; ←- null pointer deference
> else
> err = -EUNATCH;
> break;
>
> This is a race condition between HCIUARTSETPROTO and HCIUARTGETPROTO. HCI_UART_PROTO_SET is set before hu->proto is set and thus it may dereference a null pointer.
>
> To easily trigger this bug, I inserted a prink in the source code so that the C producer can easily trigger the bug. Please let me know if you have any questions.
>
Thanks! I can reproduce the issue now.
Weiteng, Yu Hao, do you have plan for sending patch to fix this problem?
Joey Lee
> Best,
> Weiteng Chen
>
> > On Jul 3, 2023, at 8:01 PM, joeyli <jlee@suse.com> wrote:
> >
> > Hi,
> >
> > On Wed, Jun 28, 2023 at 06:57:47PM -0700, Yu Hao wrote:
> >> Hi Weiteng,
> >>
> >> Could you give more info about the bug, e.g., kernel configuration,
> >> qemu arguments.
> >>
> >
> > Base on kernel code, looks that the HCIUARTSETPROTO and HCIUARTGETPROTO
> > blocks in hci_uart_tty_ioctl() should use hci_uart->proto_lock.
> >
> > I have run the C reproducer a couple of days in qemu, but it did not
> > reproduce issue until now.
> >
> > Does anyone know how to reproduce this issue easily?
> >
> > Thanks
> > Joey Lee
> >>
> >> On Wed, Jun 28, 2023 at 8:02 AM joeyli <jlee@suse.com> wrote:
> >>>
> >>> Hi Yu Hao,
> >>>
> >>> I am looking at your "BUG: general protection fault in hci_uart_tty_ioctl":
> >>>
> >>> https://lore.kernel.org/all/CA+UBctC3p49aTgzbVgkSZ2+TQcqq4fPDO7yZitFT5uBPDeCO2g@mail.gmail.com/
> >>>
> >>> I am trying the C reproducer in your URL, but it is not success yet:
> >>> https://gist.github.com/ZHYfeng/a3e3ff2bdfea5ed5de5475f0b54d55cb
> >>>
> >>> I am using v6.2 mainline kernel to run the C reproducer.
> >>>
> >>> Could you please provide suggestions for how to reproduce this issue?
> >>> And what is your qemu environment for reproducing issue?
> >>>
> >>> Thanks a lot!
> >>> Joey Lee
next prev parent reply other threads:[~2023-07-05 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 15:01 How to reproduce the BUG general protection fault in hci_uart_tty_ioctl? joeyli
2023-06-29 1:57 ` Yu Hao
2023-07-04 3:01 ` joeyli
2023-07-04 4:07 ` Weiteng Chen
2023-07-05 8:41 ` joeyli [this message]
2023-07-05 9:36 ` joeyli
2023-07-05 12:21 ` joeyli
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=20230705084148.GK5866@linux-l9pv.suse \
--to=jlee@suse.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wchen130@ucr.edu \
--cc=yhao016@ucr.edu \
/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