Jakub Kicinski [mailto:jakub.kicin...@netronome.com]
> Sent: Wednesday, August 07, 2019 6:10 AM
[...]
> Please don't expose those via sysfs. Ethtool's copybreak and descriptor
> count should be applicable here, I think.
Excuse me.
I find struct ethtool_tunable for ETHTOOL_RX_COPYBREAK.
How about t
> -Original Message-
> From: Peter Chen
> Sent: 2019年8月7日 10:41
> To: Jun Li ; Peter Chen
> Cc: Greg Kroah-Hartman ; dl-linux-imx
> ; USB list
> Subject: RE: [PATCH 2/5] usb: chipidea: add role switch class support
>
>
>
> > >
> > >
> > > > >
> > > > > You may use connect bit at port
From: Li Jun
Since there is usb_role which has similar definition like ci_role,
switch to use usb_role, then we can directly compare usb role
with a common definition, this can benifit on usb role switch
class support.
Signed-off-by: Li Jun
---
v1 -> v2
No change for this patch.
drivers/usb/c
From: Li Jun
USB role is fully controlled by usb role switch consumer(e.g. typec),
usb port can be at host mode(USB_ROLE_HOST), device mode connected to
host(USB_ROLE_DEVICE), or not connecting any parter(USB_ROLE_NONE).
Signed-off-by: Li Jun
---
Change for v2:
- Support USB_ROLE_NONE, which f
Am Dienstag, den 06.08.2019, 15:46 -0400 schrieb Alan Stern:
> +static int proc_wait_for_resume(struct usb_dev_state *ps)
> +{
> + int ret;
> +
> + usb_unlock_device(ps->dev);
> + ret = wait_event_interruptible(ps->wait_for_resume,
> + READ_ONCE(ps->not_yet_r
Hi,
Peter Chen writes:
>> (Pinging Mathias regarding xHCI support of the USB 2.0 test modes)
>>
>> On Mon, Aug 05, 2019 at 02:07:23PM +0800, Peter Chen wrote:
>> > On Sun, Aug 4, 2019 at 10:45 AM Evan Gates wrote:
>> > >
>> > > I'm trying to get my device to pass the EHSET tests. I found the
te to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Greg-Kroah-Hartman/USB-phy-fsl-usb-convert-platform-driver-to-use-dev_groups/20190807-021855
> base:
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/gregkh/usb.git
> usb-test
Yes, it does. Thanks
Thiebaud
On Tue, Aug 6, 2019 at 1:37 PM Greg Kroah-Hartman
wrote:
>
> On Tue, Aug 06, 2019 at 01:00:50PM +0200, Thiébaud Weksteen wrote:
> > Currently, the authorized_default and interface_authorized_default
> > attributes for HCD are set up after the uevent has been sent to
On 05/07/2019 14:44, Pawel Laszczak wrote:
>
>> EXTERNAL MAIL
>>
>>
>>
>> Hi,
>>
>> Pawel Laszczak writes:
>>> diff --git a/include/linux/usb/ch9.h b/include/linux/usb/ch9.h
>>> index da82606be605..d388a3a5ab7e 100644
>>> --- a/include/linux/usb/ch9.h
>>> +++ b/include/linux/usb/ch9.h
>>> @@ -
Hi,
Roger Quadros writes:
+extern const char *usb_decode_ctrl(char *str, size_t size, __u8
bRequestType,
+ __u8 bRequest, __u16 wValue, __u16 wIndex,
+ __u16 wLength);
+
>>>
>>> where's the stub when !TRACING?
>>
Hi,
Pawel Laszczak writes:
>>> +static int cdns3_gadget_start(struct cdns3 *cdns)
>>> +{
>>> + struct cdns3_device *priv_dev;
>>> + u32 max_speed;
>>> + int ret;
>>> +
>>> + priv_dev = kzalloc(sizeof(*priv_dev), GFP_KERNEL);
>>> + if (!priv_dev)
>>> + return -ENOMEM;
>>> +
>
Pawel,
On 23/07/2019 07:32, Pawel Laszczak wrote:
> Hi,
>
>> On Mon 2019-07-22 13:56:44, Pavel Machek wrote:
>>> Hi!
>>>
>>> This patch introduce new Cadence USBSS DRD driver to linux kernel.
>>>
>>> The Cadence USBSS DRD Controller is a highly configurable IP Core which
>>> can
On 7.8.2019 7.25, Rob Weber wrote:
Hi Everyone,
(Pinging Mathias regarding xHCI support of the USB 2.0 test modes)
On Mon, Aug 05, 2019 at 02:07:23PM +0800, Peter Chen wrote:
On Sun, Aug 4, 2019 at 10:45 AM Evan Gates wrote:
I'm trying to get my device to pass the EHSET tests. I found the
Hello,
syzbot found the following crash on:
HEAD commit:ae0c578a kmsan: include gfp.h from kmsan.h
git tree: kmsan
console output: https://syzkaller.appspot.com/x/log.txt?x=10e4f47460
kernel config: https://syzkaller.appspot.com/x/.config?x=27abc558ecb16a3b
dashboard link: https:/
Pawel,
On 21/07/2019 21:32, Pawel Laszczak wrote:
> This patch introduce new Cadence USBSS DRD driver to Linux kernel.
>
> The Cadence USBSS DRD Controller is a highly configurable IP Core which
> can be instantiated as Dual-Role Device (DRD), Peripheral Only and
> Host Only (XHCI)configurations.
On Wed, 7 Aug 2019 07:12:32 +
Hayes Wang wrote:
> Jakub Kicinski [mailto:jakub.kicin...@netronome.com]
> > Sent: Wednesday, August 07, 2019 6:10 AM
> [...]
> > Please don't expose those via sysfs. Ethtool's copybreak and descriptor
> > count should be applicable here, I think.
>
> Excuse
Am Dienstag, den 06.08.2019, 15:13 -0400 schrieb Alan Stern:
> On Thu, 1 Aug 2019, syzbot wrote:
>
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:7f7867ff usb-fuzzer: main usb gadget fuzzer driver
> > git tree: https://github.com/google/kasan.git usb-fuzzer
Am Dienstag, den 06.08.2019, 14:50 +0200 schrieb Andrey Konovalov:
> On Tue, Aug 6, 2019 at 2:36 PM Oliver Neukum wrote:
> >
> > Am Donnerstag, den 01.08.2019, 14:47 -0400 schrieb Alan Stern:
> > >
> > > I think this must be caused by an unbalanced refcount. That is,
> > > something must drop o
On Wed, Aug 7, 2019 at 3:38 PM Oliver Neukum wrote:
>
> Am Dienstag, den 06.08.2019, 14:50 +0200 schrieb Andrey Konovalov:
> > On Tue, Aug 6, 2019 at 2:36 PM Oliver Neukum wrote:
> > >
> > > Am Donnerstag, den 01.08.2019, 14:47 -0400 schrieb Alan Stern:
> > > >
> > > > I think this must be caused
On Wed, Aug 7, 2019 at 3:44 PM Andrey Konovalov wrote:
>
> On Wed, Aug 7, 2019 at 3:38 PM Oliver Neukum wrote:
> >
> > Am Dienstag, den 06.08.2019, 14:50 +0200 schrieb Andrey Konovalov:
> > > On Tue, Aug 6, 2019 at 2:36 PM Oliver Neukum wrote:
> > > >
> > > > Am Donnerstag, den 01.08.2019, 14:47
On Wed, Aug 7, 2019 at 3:44 PM Andrey Konovalov wrote:
>
> On Wed, Aug 7, 2019 at 3:44 PM Andrey Konovalov wrote:
> >
> > On Wed, Aug 7, 2019 at 3:38 PM Oliver Neukum wrote:
> > >
> > > Am Dienstag, den 06.08.2019, 14:50 +0200 schrieb Andrey Konovalov:
> > > > On Tue, Aug 6, 2019 at 2:36 PM Oliv
On Tue, Aug 6, 2019 at 5:34 PM Oliver Neukum wrote:
>
> Am Dienstag, den 06.08.2019, 10:19 -0400 schrieb Alan Stern:
> > In any case, I don't know if this missing "get" would cause the
> > problem, but it might well.
>
> Hi,
>
> upon further thought, this should be automated. Checking for
> refcou
On Tue, Aug 6, 2019 at 9:13 PM Alan Stern wrote:
>
> On Thu, 1 Aug 2019, syzbot wrote:
>
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:7f7867ff usb-fuzzer: main usb gadget fuzzer driver
> > git tree: https://github.com/google/kasan.git usb-fuzzer
> > console
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
KASAN: use-after-free Read in device_release_driver_internal
usb 4-1: USB disconnect, device number 2
==
BUG: KASAN: use-after-free in __lock_a
On Wed, 7 Aug 2019, Andrey Konovalov wrote:
> On Tue, Aug 6, 2019 at 9:13 PM Alan Stern wrote:
> >
> > On Thu, 1 Aug 2019, syzbot wrote:
> >
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:7f7867ff usb-fuzzer: main usb gadget fuzzer driver
> > > git tree:
On Fri, Apr 12, 2019 at 1:32 PM Andrey Konovalov wrote:
>
> On Fri, Apr 12, 2019 at 1:29 AM syzbot
> wrote:
> >
> > syzbot has found a reproducer for the following crash on:
> >
> > HEAD commit:9a33b369 usb-fuzzer: main usb gadget fuzzer driver
> > git tree: https://github.com/google/ka
On Fri, Apr 12, 2019 at 1:46 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:9a33b369 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan/tree/usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=101
On Wed, 7 Aug 2019, Oliver Neukum wrote:
> Am Dienstag, den 06.08.2019, 15:13 -0400 schrieb Alan Stern:
> > On Thu, 1 Aug 2019, syzbot wrote:
> >
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:7f7867ff usb-fuzzer: main usb gadget fuzzer driver
> > > gi
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+1b2449b7b5dc240d1...@syzkaller.appspotmail.com
Tested on:
commit: 6a3599ce usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasa
Am Mittwoch, den 07.08.2019, 16:07 +0200 schrieb Andrey Konovalov:
> On Fri, Apr 12, 2019 at 1:46 PM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:9a33b369 usb-fuzzer: main usb gadget fuzzer driver
> > git tree: https://github.com/goog
Oliver Neukum writes:
> Am Mittwoch, den 07.08.2019, 16:07 +0200 schrieb Andrey Konovalov:
>> On Fri, Apr 12, 2019 at 1:46 PM syzbot
>> wrote:
>> >
>> > Hello,
>> >
>> > syzbot found the following crash on:
>> >
>> > HEAD commit:9a33b369 usb-fuzzer: main usb gadget fuzzer driver
>> > git
On Wed, Aug 7, 2019 at 4:01 PM Alan Stern wrote:
>
> On Wed, 7 Aug 2019, Andrey Konovalov wrote:
>
> > On Tue, Aug 6, 2019 at 9:13 PM Alan Stern wrote:
> > >
> > > On Thu, 1 Aug 2019, syzbot wrote:
> > >
> > > > Hello,
> > > >
> > > > syzbot found the following crash on:
> > > >
> > > > HEAD comm
Hello,
syzbot found the following crash on:
HEAD commit:e96407b4 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=162e635260
kernel config: https://syzkaller.appspot.com/x/.
Hello,
syzbot found the following crash on:
HEAD commit:e96407b4 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=14f54e2660
kernel config: https://syzkaller.appspot.com/x/.
It has been requested that usbfs should implement runtime power
management, instead of forcing the device to remain at full power as
long as the device file is open. This patch introduces that new
feature.
It does so by adding three new usbfs ioctls:
USBDEVFS_FORBID_SUSPEND: Prevents the
On Wed, Aug 7, 2019 at 4:24 PM Andrey Konovalov wrote:
>
> On Wed, Aug 7, 2019 at 4:01 PM Alan Stern wrote:
> >
> > On Wed, 7 Aug 2019, Andrey Konovalov wrote:
> >
> > > On Tue, Aug 6, 2019 at 9:13 PM Alan Stern
> > > wrote:
> > > >
> > > > On Thu, 1 Aug 2019, syzbot wrote:
> > > >
> > > > > He
On Wed, Aug 7, 2019 at 4:34 PM Andrey Konovalov wrote:
>
> On Wed, Aug 7, 2019 at 4:24 PM Andrey Konovalov wrote:
> >
> > On Wed, Aug 7, 2019 at 4:01 PM Alan Stern wrote:
> > >
> > > On Wed, 7 Aug 2019, Andrey Konovalov wrote:
> > >
> > > > On Tue, Aug 6, 2019 at 9:13 PM Alan Stern
> > > > wro
On Wed, 7 Aug 2019, Andrey Konovalov wrote:
> On Wed, Aug 7, 2019 at 4:01 PM Alan Stern wrote:
> >
> > On Wed, 7 Aug 2019, Andrey Konovalov wrote:
> >
> > > On Tue, Aug 6, 2019 at 9:13 PM Alan Stern
> > > wrote:
> > > >
> > > > On Thu, 1 Aug 2019, syzbot wrote:
> > > >
> > > > > Hello,
> > > >
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+74c65761783d66a9c...@syzkaller.appspotmail.com
Tested on:
commit: 9a33b369 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasa
On Wed, Aug 7, 2019 at 4:39 PM Alan Stern wrote:
>
> On Wed, 7 Aug 2019, Andrey Konovalov wrote:
>
> > On Wed, Aug 7, 2019 at 4:01 PM Alan Stern wrote:
> > >
> > > On Wed, 7 Aug 2019, Andrey Konovalov wrote:
> > >
> > > > On Tue, Aug 6, 2019 at 9:13 PM Alan Stern
> > > > wrote:
> > > > >
> > >
Hello,
On Wed, Aug 07, 2019 at 02:11:03PM +0300, Mathias Nyman wrote:
> On 7.8.2019 7.25, Rob Weber wrote:
> > Hi Everyone,
> >
> > (Pinging Mathias regarding xHCI support of the USB 2.0 test modes)
> >
> > On Mon, Aug 05, 2019 at 02:07:23PM +0800, Peter Chen wrote:
> > > On Sun, Aug 4, 2019 at
Hi Felipe and Peter,
On Wed, Aug 07, 2019 at 10:47:49AM +0300, Felipe Balbi wrote:
> Peter Chen writes:
> >> (Pinging Mathias regarding xHCI support of the USB 2.0 test modes)
> >>
> >> On Mon, Aug 05, 2019 at 02:07:23PM +0800, Peter Chen wrote:
> >> > On Sun, Aug 4, 2019 at 10:45 AM Evan Gates
On Wed, 7 Aug 2019, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered
> crash:
> KASAN: use-after-free Read in device_release_driver_internal
>
> usb 4-1: USB disconnect, device number 2
>
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
KASAN: use-after-free Read in device_release_driver_internal
==
BUG: KASAN: use-after-free in __lock_acquire+0x3a5d/0x5340
kernel/locking/loc
On Wed, 7 Aug 2019, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered
> crash:
> KASAN: use-after-free Read in device_release_driver_internal
> Tested on:
>
> commit: 6a3599ce usb-fuzzer: main usb gadget fuzzer driver
> git tree:
On Wed, 7 Aug 2019 04:34:24 +, Hayes Wang wrote:
> Jakub Kicinski [mailto:jakub.kicin...@netronome.com]
> > > static int rtl_stop_rx(struct r8152 *tp)
> > > {
> > > - int i;
> > > + struct list_head *cursor, *next, tmp_list;
> > > + unsigned long flags;
> > > +
> > > + INIT_LIST_HEAD(&tmp_lis
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+1b2449b7b5dc240d1...@syzkaller.appspotmail.com
Tested on:
commit: 6a3599ce usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasa
On Mon, Aug 05, 2019 at 09:36:32PM +0200, Greg Kroah-Hartman wrote:
> Platform drivers now have the option to have the platform core create
> and remove any needed sysfs attribute files. So take advantage of that
> and do not register "by hand" any sysfs files.
>
> Cc: Bin Liu
> Signed-off-by: G
On Wed, 7 Aug 2019, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger
> crash:
>
> Reported-and-tested-by:
> syzbot+1b2449b7b5dc240d1...@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: 6a3599ce usb-fuzzer: main usb gadget fuzzer
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3-rc3 next-20190807]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/jun-li
On Tue, Aug 06, 2019 at 12:34:58PM +0100, Mans Rullgard wrote:
> In order for devicetree nodes to be correctly associated with attached
> devices, the controller node needs to be propagated to the glue device.
>
> Signed-off-by: Mans Rullgard
Applied. Thanks.
-Bin.
Hello,
syzbot found the following crash on:
HEAD commit:e96407b4 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=151b292660
kernel config: https://syzkaller.appspot.com/x/.
On Thu, Aug 08, 2019 at 12:11:46AM +0530, Saurav Girepunje wrote:
> Without pm_runtime_{get,put}_sync calls in place, writing
> vbus value via /sys causes the error
>
> "Unhandled fault external abort on non-linefetch"
>
> Signed-off-by: Saurav Girepunje
Thanks for the patch. Can you please mer
On Wed, Aug 07, 2019 at 12:28:06PM -0700, syzbot wrote:
> usercopy: Kernel memory exposure attempt detected from wrapped address
> (offset 0, size 0)!
> [ cut here ]
> kernel BUG at mm/usercopy.c:98!
This report is confusing because the arguments to usercopy_abort() are wro
On Mon, Aug 05, 2019 at 11:43:21PM +0530, Saurav Girepunje wrote:
> Update the function description of musb_stage0_irq in musb_core.c
I modified this to:
usb: musb: core: Update the function description
Update the function description of musb_stage0_irq() to remove unused
parameter.
and applied
On Mon, Jul 29, 2019 at 05:04:28PM +0800, Jia-Ju Bai wrote:
> In musb_handle_intr_connect(), there is an if statement on line 783 to
> check whether musb->hcd is NULL:
> if (musb->hcd)
>
> When musb->hcd is NULL, it is used on line 797:
> musb_host_poke_root_hub(musb);
> if (musb->
Maciej Fijalkowski [mailto:maciejromanfijalkow...@gmail.com]
> Sent: Wednesday, August 07, 2019 8:44 PM
[...]
> > Excuse me.
> > I find struct ethtool_tunable for ETHTOOL_RX_COPYBREAK.
> > How about the descriptor count?
>
> Look how drivers implement ethtool's set_ringparam ops.
I would check it
>
> On Wed, Aug 07, 2019 at 10:47:49AM +0300, Felipe Balbi wrote:
> > Peter Chen writes:
> > >> (Pinging Mathias regarding xHCI support of the USB 2.0 test modes)
> > >>
> > >> On Mon, Aug 05, 2019 at 02:07:23PM +0800, Peter Chen wrote:
> > >> > On Sun, Aug 4, 2019 at 10:45 AM Evan Gates wrote
On Wed, Aug 07, 2019 at 12:58:21PM -0700, Matthew Wilcox wrote:
> On Wed, Aug 07, 2019 at 12:28:06PM -0700, syzbot wrote:
> > usercopy: Kernel memory exposure attempt detected from wrapped address
> > (offset 0, size 0)!
> > [ cut here ]
> > kernel BUG at mm/usercopy.c:98!
>
Justin,
> Attached 2 x brand new Western Digital 8TB USB 3.0 drives awhile back and
> ran some file copy tests and was getting these warnings-- is there any way
> to avoid these warnings? I did confirm with parted that the partition was
> aligned but this appears to be something related to the
Hi,
>
>Roger Quadros writes:
> +extern const char *usb_decode_ctrl(char *str, size_t size, __u8
> bRequestType,
> +__u8 bRequest, __u16 wValue, __u16 wIndex,
> +__u16 wLength);
> +
where's the stub when !TRACIN
Hi Roger,
>
>
>On 23/07/2019 07:32, Pawel Laszczak wrote:
>
>> Hi,
>
>>
>
>>> On Mon 2019-07-22 13:56:44, Pavel Machek wrote:
>
Hi!
>
>
This patch introduce new Cadence USBSS DRD driver to linux kernel.
>
>
The Cadence USBSS DRD Controller is a highly configura
Hi,
Yinbo Zhu writes:
> layerscape board sometimes reported some usb call trace, that is due to
> kernel sent LPM tokerns automatically when it has no pending transfers
> and think that the link is idle enough to enter L1, which procedure will
> ask usb register has a recovery,then kernel will
Hi,
"Yang, Fei" writes:
>> I need tracepoints to see what's going on, please collect tracepoints.
>
> See attached. Search for "length 16384/16384" to the USB request using
> sg list. And the transfer stalls at a request with "length 512/512".
which gadget driver is this btw? Let's look at wha
Hi!
Machine is thinkpad x220. BFQ related?
[ 8224.904413] usb 2-1.1.4: Product: Intenso Twister Line
[ 8224.904421] usb 2-1.1.4: Manufacturer: Alcor Tech
[ 8224.904428] usb 2-1.1.4: SerialNumber: 12102500210755
[ 8224.905778] usb-storage 2-1.1.4:1.0: USB Mass Storage device
detected
[ 8
Hi,
I hope this has to do with the failure reported by Doug. I'm
finalizing my fix. I'd appreciate if you could retry with my fix
applied.
Thanks,
Paolo
> Il giorno 7 ago 2019, alle ore 12:10, Pavel Machek ha scritto:
>
> Hi!
>
> Machine is thinkpad x220. BFQ related?
>
>
>
> [ 8224
Hi!
> I hope this has to do with the failure reported by Doug. I'm
> finalizing my fix. I'd appreciate if you could retry with my fix
> applied.
Ok, just cc me with the fix ;-).
This happened once so far, but I have other crash (when closing
chromium) that happens a bit too often, might be rel
67 matches
Mail list logo
