Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest -next
kernel I've stumbled on the following:
[ 1361.390880] WARNING: CPU: 10 PID: 24274 at lib/debugobjects.c:260
debug_print_object+0x8c/0xb0()
[ 1361.391203] ODEBUG: free active (active state 0) object type:
On 04/24/2014 03:24 PM, Greg KH wrote:
On Thu, Apr 24, 2014 at 01:40:14PM -0400, Sasha Levin wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest
-next
kernel I've stumbled on the following:
[ 1361.390880] WARNING: CPU: 10 PID: 24274 at lib
On 07/18/2014 01:34 PM, Nicholas Krause wrote:
I am removing two fix mes in this file as after dicussing then it seems
there is no reason to check against Null for usb_device as it can never
be NULL and this is check is therefore not needed.
Signed-off-by: Nicholas Krause
, Sasha Levin sas...@kernel.org wrote:
On 07/18/2014 01:34 PM, Nicholas Krause wrote:
I am removing two fix mes in this file as after dicussing then it seems
there is no reason to check against Null for usb_device as it can never
be NULL and this is check is therefore not needed.
Signed-off
Revert since the commit message is incorrect and the original author refuses
to fix/maintain it because it's in the kernel already.
Signed-off-by: Sasha Levin sas...@kernel.org
---
drivers/usb/core/hcd.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/core/hcd.c b/drivers/usb
On 07/23/2014 12:49 PM, Greg KH wrote:
On Wed, Jul 23, 2014 at 08:56:10AM -0400, Sasha Levin wrote:
Revert since the commit message is incorrect and the original author
refuses
to fix/maintain it because it's in the kernel already.
How can someone fix a commit message that is already
On 07/24/2014 12:04 PM, Greg KH wrote:
If you add a revert and leave the original broken commit in, wouldn't it
cause issues
for anyone trying to bisect a build breakage?
Yes it does.
I can not rebase my public trees, nor should any other kernel
maintainer. This has been true for _many_
On 04/27/2015 05:44 AM, Johan Hovold wrote:
Could you try updating to 3.19 (or later) or to cherry pick aa8e22128b40
(usb: serial: silence all non-critical read errors) and see if that
helps?
We should backport that one to stable either way.
You may want to add aa8e22128b40 (usb:
, which will panic the kernel.
Fix that by checking that the bus was indeed initialized before trying to
register drivers on top of it.
Signed-off-by: Sasha Levin sasha.le...@oracle.com
---
drivers/usb/common/ulpi.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/common
On 05/28/2015 01:39 AM, Sudip Mukherjee wrote:
diff --git a/drivers/base/driver.c b/drivers/base/driver.c
index 4eabfe2..1acae5b 100644
--- a/drivers/base/driver.c
+++ b/drivers/base/driver.c
@@ -150,6 +150,11 @@ int driver_register(struct device_driver *drv)
int ret;
struct
On 05/22/2015 06:16 AM, Heikki Krogerus wrote:
diff --git a/drivers/usb/common/ulpi.c b/drivers/usb/common/ulpi.c
index 0e6f968..0b0a5e7 100644
--- a/drivers/usb/common/ulpi.c
+++ b/drivers/usb/common/ulpi.c
@@ -132,6 +132,10 @@ int ulpi_register_driver(struct ulpi_driver
*drv)
On 11/25/2015 07:19 PM, Steinar H. Gunderson wrote:
> Add a new interface for userspace to preallocate memory that can be
> used with usbfs. This gives two primary benefits:
>
> - Zerocopy; data no longer needs to be copied between the userspace
>and the kernel, but can instead be read
Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Acked-by: John Youn <johny...@synopsys.com>
Signed-off-by: John Stultz <john.stu...@linaro.org>
Signed-off-by: Felipe Balbi <felipe.ba...@linux.intel.com>
Signed-off-by: Sasha Levin <al
Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Acked-by: John Youn <johny...@synopsys.com>
Signed-off-by: John Stultz <john.stu...@linaro.org>
Signed-off-by: Felipe Balbi <felipe.ba...@linux.intel.com>
Signed-off-by: Sasha Levin <al
Hi Yoshihiro Shimoda.
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag.
fixing commit: 279d4bc64060 usb: gadget: udc: renesas_usb3: add support for
generic phy.
The bot has also determined it's probably a bug fixing patch. (score: 99.1076)
The bot
Hi Yoshihiro Shimoda.
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag.
fixing commit: 279d4bc64060 usb: gadget: udc: renesas_usb3: add support for
generic phy.
The bot has also determined it's probably a bug fixing patch. (score: 96.8529)
The bot
Hi Yoshihiro Shimoda.
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag.
fixing commit: 43ba968b00ea usb: gadget: udc: renesas_usb3: add debugfs to set
the b-device mode.
The bot has also determined it's probably a bug fixing patch. (score: 94.9837)
Hi Yoshihiro Shimoda.
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag.
fixing commit: cf06df3fae28 usb: gadget: udc: renesas_usb3: move
pm_runtime_{en,dis}able().
The bot has also determined it's probably a bug fixing patch. (score: 98.8092)
The
Hi,
[This is an automated email]
This commit has been processed by the -stable helper bot and determined
to be a high probability candidate for -stable trees. (score: 8.8613)
The bot has tested the following trees: v4.16.1, v4.15.16, v4.14.33, v4.9.93,
v4.4.127.
v4.16.1: Build OK!
v4.15.16:
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has also determined it's probably a bug fixing patch. (score: 58.4237)
The bot has tested the following trees:
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has also determined it's probably a bug fixing patch. (score: 67.5935)
The bot has tested the following trees:
Hi.
[This is an automated email]
This commit has been processed by the -stable helper bot and determined
to be a high probability candidate for -stable trees. (score: 10.6103)
The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
v4.15.15: Build OK!
v4.14.32: Build
Hi.
[This is an automated email]
This commit has been processed by the -stable helper bot and determined
to be a high probability candidate for -stable trees. (score: 13.1846)
The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
v4.15.15: Build OK!
v4.14.32: Build
On Thu, Apr 05, 2018 at 10:54:59AM -0600, Shuah Khan wrote:
>On 04/05/2018 10:42 AM, Sasha Levin wrote:
>> Hi.
>>
>> [This is an automated email]
>>
>> This commit has been processed by the -stable helper bot and determined
>> to be a high probability candi
On Thu, Apr 05, 2018 at 09:11:02PM +0200, Greg KH wrote:
>On Thu, Apr 05, 2018 at 04:42:46PM +0000, Sasha Levin wrote:
>> Hi.
>>
>> [This is an automated email]
>
>Why are you running this against patches that are not yet in Linus's
>tree? That feels odd. Only about
Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Acked-by: John Youn <johny...@synopsys.com>
Signed-off-by: John Stultz <john.stu...@linaro.org>
Signed-off-by: Felipe Balbi <felipe.ba...@linux.intel.com>
Signed-off-by: Sasha Levin <al
Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Acked-by: John Youn <johny...@synopsys.com>
Signed-off-by: John Stultz <john.stu...@linaro.org>
Signed-off-by: Felipe Balbi <felipe.ba...@linux.intel.com>
Signed-off-by: Sasha Levin <al
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v4.18.8, v4.14.70, v4.9.127, v4.4.156,
v3.18.122,
v4.18.8: Failed to apply!
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v4.18.8, v4.14.70, v4.9.127, v4.4.156,
v3.18.122,
v4.18.8: Build OK!
v4.14.70:
29 matches
Mail list logo
