From: "Michael S. Tsirkin" <mst@redhat.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Igor Skalkin <igor.skalkin@opensynergy.com>,
Jason Wang <jasowang@redhat.com>,
virtualization@lists.linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
mgo@opensynergy.com
Subject: Re: [PATCH] virtio_bt: Fix alignment in configuration struct
Date: Tue, 30 Aug 2022 09:44:58 -0400 [thread overview]
Message-ID: <20220830094441-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CABBYNZKZGxbt=jdpBL77x1mCeTPdDE-p-Pt8JjZN+KoRgR3Ohw@mail.gmail.com>
On Thu, Aug 11, 2022 at 10:02:31AM -0700, Luiz Augusto von Dentz wrote:
> Hi Michael,
>
> On Thu, Aug 11, 2022 at 1:00 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > On Mon, Aug 08, 2022 at 08:16:11AM -0400, Michael S. Tsirkin wrote:
> > > On Mon, Aug 08, 2022 at 02:04:43PM +0200, Igor Skalkin wrote:
> > > > On 8/8/22 01:00, Michael S. Tsirkin wrote:
> > > >
> > > > On Mon, Aug 08, 2022 at 12:11:52AM +0200, Igor Skalkin wrote:
> > > >
> > > > According to specification [1], "For the device-specific configuration
> > > > space, the driver MUST use 8 bit wide accesses for 8 bit wide fields,
> > > > 16 bit wide and aligned accesses for 16 bit wide fields and 32 bit wide
> > > > and aligned accesses for 32 and 64 bit wide fields.".
> > > >
> > > > Current version of the configuration structure:
> > > >
> > > > struct virtio_bt_config {
> > > > __u8 type;
> > > > __u16 vendor;
> > > > __u16 msft_opcode;
> > > > } __attribute__((packed));
> > > >
> > > > has both 16bit fields non-aligned.
> > > >
> > > > This commit fixes it.
> > > >
> > > > [1] https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fdocs.oasis%2dopen.org%2fvirtio%2fvirtio%2fv1.1%2fvirtio%2dv1.1.pdf&umid=d1786ace-e8ea-40e8-9665-96c0949174e5&auth=53c7c7de28b92dfd96e93d9dd61a23e634d2fbec-39b15885ceebe9fda9357320aec1ccbac416a470
> > > >
> > > > Signed-off-by: Igor Skalkin <Igor.Skalkin@opensynergy.com>
> > > >
> > > > This is all true enough, but the problem is
> > > > 1. changing uapi like this can't be done, will break userspace
> > > > 2. the driver has more issues and no one seems to want to
> > > > maintain it.
> > > > I posted a patch "Bluetooth: virtio_bt: mark broken" and intend
> > > > to merge it for this release.
> > > >
> > > > This is very sad. We already use this driver in our projects.
> > >
> > > Really? Can you step up to maintain it? Then we can fix the issues
> > > and it won't be broken.
> >
> > Just a reminder that I'm waiting for a response on that.
> > I just don't know enough about bluetooth.
>
> Just a heads up that Marcel is on vacation, he did mention that he had
> done some work to update virtio_bt thus why I didn't apply any of the
> changes yet.
Any update? when does Marcel return?
> > --
> > MST
> >
>
>
> --
> Luiz Augusto von Dentz
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
mgo@opensynergy.com, Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [PATCH] virtio_bt: Fix alignment in configuration struct
Date: Tue, 30 Aug 2022 09:44:58 -0400 [thread overview]
Message-ID: <20220830094441-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CABBYNZKZGxbt=jdpBL77x1mCeTPdDE-p-Pt8JjZN+KoRgR3Ohw@mail.gmail.com>
On Thu, Aug 11, 2022 at 10:02:31AM -0700, Luiz Augusto von Dentz wrote:
> Hi Michael,
>
> On Thu, Aug 11, 2022 at 1:00 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > On Mon, Aug 08, 2022 at 08:16:11AM -0400, Michael S. Tsirkin wrote:
> > > On Mon, Aug 08, 2022 at 02:04:43PM +0200, Igor Skalkin wrote:
> > > > On 8/8/22 01:00, Michael S. Tsirkin wrote:
> > > >
> > > > On Mon, Aug 08, 2022 at 12:11:52AM +0200, Igor Skalkin wrote:
> > > >
> > > > According to specification [1], "For the device-specific configuration
> > > > space, the driver MUST use 8 bit wide accesses for 8 bit wide fields,
> > > > 16 bit wide and aligned accesses for 16 bit wide fields and 32 bit wide
> > > > and aligned accesses for 32 and 64 bit wide fields.".
> > > >
> > > > Current version of the configuration structure:
> > > >
> > > > struct virtio_bt_config {
> > > > __u8 type;
> > > > __u16 vendor;
> > > > __u16 msft_opcode;
> > > > } __attribute__((packed));
> > > >
> > > > has both 16bit fields non-aligned.
> > > >
> > > > This commit fixes it.
> > > >
> > > > [1] https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fdocs.oasis%2dopen.org%2fvirtio%2fvirtio%2fv1.1%2fvirtio%2dv1.1.pdf&umid=d1786ace-e8ea-40e8-9665-96c0949174e5&auth=53c7c7de28b92dfd96e93d9dd61a23e634d2fbec-39b15885ceebe9fda9357320aec1ccbac416a470
> > > >
> > > > Signed-off-by: Igor Skalkin <Igor.Skalkin@opensynergy.com>
> > > >
> > > > This is all true enough, but the problem is
> > > > 1. changing uapi like this can't be done, will break userspace
> > > > 2. the driver has more issues and no one seems to want to
> > > > maintain it.
> > > > I posted a patch "Bluetooth: virtio_bt: mark broken" and intend
> > > > to merge it for this release.
> > > >
> > > > This is very sad. We already use this driver in our projects.
> > >
> > > Really? Can you step up to maintain it? Then we can fix the issues
> > > and it won't be broken.
> >
> > Just a reminder that I'm waiting for a response on that.
> > I just don't know enough about bluetooth.
>
> Just a heads up that Marcel is on vacation, he did mention that he had
> done some work to update virtio_bt thus why I didn't apply any of the
> changes yet.
Any update? when does Marcel return?
> > --
> > MST
> >
>
>
> --
> Luiz Augusto von Dentz
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-08-30 13:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220807221152.38948-1-Igor.Skalkin@opensynergy.com>
2022-08-07 23:00 ` [PATCH] virtio_bt: Fix alignment in configuration struct Michael S. Tsirkin
2022-08-07 23:00 ` Michael S. Tsirkin
2022-08-08 12:04 ` Igor Skalkin
2022-08-08 12:16 ` Michael S. Tsirkin
2022-08-08 12:16 ` Michael S. Tsirkin
2022-08-11 8:00 ` Michael S. Tsirkin
2022-08-11 8:00 ` Michael S. Tsirkin
2022-08-11 17:02 ` Luiz Augusto von Dentz
2022-08-30 13:44 ` Michael S. Tsirkin [this message]
2022-08-30 13:44 ` Michael S. Tsirkin
2022-09-08 16:40 ` Michael S. Tsirkin
2022-09-08 16:40 ` Michael S. Tsirkin
2022-10-07 13:03 ` Michael S. Tsirkin
2022-10-07 13:03 ` Michael S. Tsirkin
2022-10-07 19:33 ` Luiz Augusto von Dentz
2022-10-11 12:23 ` Igor Skalkin
2022-10-11 12:23 ` Igor Skalkin
2022-10-11 19:36 ` Luiz Augusto von Dentz
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=20220830094441-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=igor.skalkin@opensynergy.com \
--cc=jasowang@redhat.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mgo@opensynergy.com \
--cc=virtualization@lists.linux-foundation.org \
/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.