public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	syzbot <syzbot+c38e5e60d0041a99dbf5@syzkaller.appspotmail.com>,
	gregkh@linuxfoundation.org, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH v2 resend] media: dvb: usb: Fix WARNING in dib0700_i2c_xfer/usb_submit_urb
Date: Sat, 29 Mar 2025 10:31:52 -0400	[thread overview]
Message-ID: <a2bbdfbf-d7aa-4601-ae1e-18d75d011084@rowland.harvard.edu> (raw)
In-Reply-To: <Z-eNvcrFu0VSY23U@shikoro>

On Sat, Mar 29, 2025 at 07:05:49AM +0100, Wolfram Sang wrote:
> 
> > In the case of dib0700, it was clear from the source code that the 
> > driver uses USB Control transfers to tell the hardware about I2C 
> > messages.  I don't know if other bridges work in the same way.  In 
> > theory a bridge could use USB Bulk transfers instead; they aren't 
> > subject to this restriction on length-0 reads.  Or a bridge could use a 
> > Control read transfer but include extra header material along with the 
> > actual data, so that a length-0 message wouldn't end up generating a 
> > length-0 read.
> 
> Fully understood, thanks for your explanation.
> 
> > So the short answer is that you would need to find someone who really 
> > understands what's going on here -- which I don't.  Sorry.
> 
> No worries. There are only 5 drivers or so, I will manually check if
> they use a control_read and have no own header. Doesn't sound hard.

Good...  Feel free to ask me if you have any questions or need any other 
help.

Alan Stern


      reply	other threads:[~2025-03-29 14:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <67e1a1f5.050a0220.a7ebc.0029.GAE@google.com>
2025-03-24 19:08 ` [syzbot] [usb?] WARNING in dib0700_i2c_xfer/usb_submit_urb Alan Stern
2025-03-24 19:19   ` Wolfram Sang
2025-03-25 16:41     ` Alan Stern
2025-03-25 16:59       ` Wolfram Sang
2025-03-25 17:47         ` Alan Stern
2025-03-25 19:07           ` syzbot
2025-03-25 19:28             ` [PATCH] media: dvb: usb: Fix " Alan Stern
2025-03-25 19:56               ` Wolfram Sang
2025-03-25 21:47                 ` Alan Stern
2025-03-25 22:17                   ` Wolfram Sang
2025-03-26 15:28                     ` [PATCH v2] " Alan Stern
2025-03-26 15:54                       ` Wolfram Sang
2025-03-26 16:04                         ` Alan Stern
2025-03-26 21:32                           ` Wolfram Sang
2025-03-27 16:10                             ` [PATCH v2 resend] " Alan Stern
2025-03-28 15:45                               ` Wolfram Sang
2025-03-29  2:08                                 ` Alan Stern
2025-03-29  6:05                                   ` Wolfram Sang
2025-03-29 14:31                                     ` Alan Stern [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=a2bbdfbf-d7aa-4601-ae1e-18d75d011084@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=syzbot+c38e5e60d0041a99dbf5@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=wsa+renesas@sang-engineering.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