I get below warning every day with 3.7,
one or two times per day.
[ 2235.186027] WARNING: at
/mnt/sda7/kernel/linux/arch/x86/kernel/apic/ipi.c:109
default_send_IPI_mask_logical+0x2f/0xb8()
[ 2235.186030] Hardware name: Aspire 4741
[ 2235.186032] empty IPI mask
[ 2235.186034] Modules linked in: v
On 01/25/2013 09:43 AM, John Stultz wrote:
On 01/25/2013 01:38 AM, Willy Tarreau wrote:
On Fri, Jan 25, 2013 at 10:16:50AM +0100, Romain Francoise wrote:
Hi,
John Stultz writes:
Of course, the xtime_cache is updated at the bottom of
update_wall_time(). So the early return on (offset <
timek
Properly initialize scatterlist before using it.
Signed-off-by: K. Y. Srinivasan
Cc: stable@vger.kernel.org
---
drivers/scsi/storvsc_drv.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/storvsc_drv.c b/drivers/scsi/storvsc_drv.c
index 270b3cf..5ada1d0 10064
On Fri, Jan 25, 2013 at 05:27:36PM -0800, K. Y. Srinivasan wrote:
> Properly initialize scatterlist before using it.
>
> Signed-off-by: K. Y. Srinivasan
> Cc: Stable
> ---
> drivers/scsi/storvsc_drv.c |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
This is not the correct way to
Properly initialize scatterlist before using it.
Signed-off-by: K. Y. Srinivasan
Cc: Stable
---
drivers/scsi/storvsc_drv.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/storvsc_drv.c b/drivers/scsi/storvsc_drv.c
index 270b3cf..5ada1d0 100644
--- a/drivers
On Wed, 2013-01-23 at 13:17 +, Ben Hutchings wrote:
> On Wed, 2013-01-23 at 07:52 +, Matt Fleming wrote:
> > On Wed, 2013-01-23 at 04:16 +, Ben Hutchings wrote:
> > > On Mon, 2013-01-21 at 21:12 +, Matt Fleming wrote:
> > > [...]
> > > > From 92e73f936e40a8c6562e47425d434a4e62d2b8e2
This is a note to let you know that I've just added the patch titled
USB: EHCI: fix timer bug affecting port resume
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-linus branch.
The patch will show up in the next release o
On Wed, 2013-01-23 at 07:52 +, Matt Fleming wrote:
> On Wed, 2013-01-23 at 04:16 +, Ben Hutchings wrote:
> > On Mon, 2013-01-21 at 21:12 +, Matt Fleming wrote:
> > [...]
> > > From 92e73f936e40a8c6562e47425d434a4e62d2b8e2 Mon Sep 17 00:00:00 2001
> > > From: Matt Fleming
> > > Date: We
This is a note to let you know that I've just added the patch titled
USB: EHCI: unlink one async QH at a time
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-linus branch.
The patch will show up in the next release of the
This is a note to let you know that I've just added the patch titled
USB: EHCI: remove ASS/PSS polling timeout
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-linus branch.
The patch will show up in the next release of the
[ v2 removes the extra whitespace before the comment line, problem reported
by Jerry Snitselaar ]
Patch for 3.0 tree, a backport of the below upstream commit.
commit 7b4f6ecacb14f384adc1a5a67ad95eb082c02bd1 upstream.
They don't always appear as AHCI class devices but instead as IDE class.
Ba
On Fri, Jan 25, 2013 at 01:45:21PM -0700, Jerry Snitselaar wrote:
>
> There is a whitespace error in this patch:
>
> Applying: ahci: Add identifiers for ASM106x devices
> /root/linux/linux/.git/rebase-apply/patch:12: space before tab in indent.
> /* Asmedia */
> warning: 1 line adds white
This is a note to let you know that I've just added the patch titled
USB: XHCI: fix memory leak of URB-private data
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-linus branch.
The patch will show up in the next release o
On Thu Jan 24 13, Greg Kroah-Hartman wrote:
> 3.0-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Alan Cox
>
> commit 7b4f6ecacb14f384adc1a5a67ad95eb082c02bd1 upstream.
>
> They don't always appear as AHCI class devices but instead as ID
From: Jim Somerville
Running the command:
inotifywait -e unmount /mnt/disk
immediately aborts with a -EINVAL return code. This is however
a valid parameter. This abort occurs only if unmount is the
sole event parameter. If other event parameters are supplied,
then the unmount event w
When a device was disconnected the driver may hang at waiting for urbs it never
will get. Fix this by using a timeout while waiting for the used semaphore.
There is still a memory leak if a timeout happens, but at least the driver
now continues his disconnect routine.
Cc:
Signed-off-by: Alexande
When a device was disconnected the driver may hang at waiting for urbs it never
will get. Fix this by using a timeout while waiting for the used semaphore.
There is still a memory leak if a timeout happens, but at least the driver
now continues his disconnect routine.
Cc:
Signed-off-by: Alexande
Hi,
Please take this patch for -stable in kernels 3.5-3.7. It doesn't have an
equivalent upstream commit because the code was removed before the bug was
discovered. See f661f1e0bf50 and 7e18530bef6a.
Thanks,
Ben
From: Dave Chinner
There is a logic inversion in xfssyncd_worker() which
On Fri, Jan 25, 2013 at 12:32:32PM -0500, Konrad Rzeszutek Wilk wrote:
> Check that the ring does not have an insane amount of requests
> (more than there could fit on the ring).
.. snip..
> diff --git a/drivers/block/xen-blkback/blkback.c
> b/drivers/block/xen-blkback/blkback.c
> index 2de3da9..4
On Fri, Jan 25, 2013 at 06:45:29PM +0100, Roger Pau Monné wrote:
> On 25/01/13 18:32, Konrad Rzeszutek Wilk wrote:
> > We want to be able to exit if the difference between the request
> > produced (what the frontend tells us) and the requests consumed
> > (what we have so far processed) is greater
On Fri, Jan 25, 2013 at 12:32:31PM -0500, Konrad Rzeszutek Wilk wrote:
> We want to be able to exit if the difference between the request
> produced (what the frontend tells us) and the requests consumed
> (what we have so far processed) is greater than the ring size.
>
> If so, we should terminat
On Fri, Jan 25, 2013 at 06:45:29PM +0100, Roger Pau Monné wrote:
> On 25/01/13 18:32, Konrad Rzeszutek Wilk wrote:
> > We want to be able to exit if the difference between the request
> > produced (what the frontend tells us) and the requests consumed
> > (what we have so far processed) is greater
On Thu, Jan 24, 2013 at 2:18 PM, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 3.0.61 release.
> There are 15 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Res
On Thu, Jan 24, 2013 at 2:12 PM, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 3.7.5 release.
> There are 46 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Resp
On Thu, Jan 24, 2013 at 2:15 PM, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 3.4.28 release.
> There are 22 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Res
On 25/01/13 18:32, Konrad Rzeszutek Wilk wrote:
> We want to be able to exit if the difference between the request
> produced (what the frontend tells us) and the requests consumed
> (what we have so far processed) is greater than the ring size.
>
> If so, we should terminate the loop as the reque
Arnd Bergmann wrote:
>
> Recent assembler versions complain about extraneous
> whitespace inside [] brackets. This fixes all of
> these instances for the samsung platforms. We should
> backport this to all kernels that might need to
> be built with new binutils.
>
> arch/arm/kernel/entry-armv.S:
On 01/25/2013 01:16 AM, Romain Francoise wrote:
Although the issue it addresses (inconsistencies in the _COARSE
clockids) would return, those had been present for quite some time
without complaint. So another possible solution would be the following
(fair warning, totally untested). Mind giving i
On 01/25/2013 01:38 AM, Willy Tarreau wrote:
On Fri, Jan 25, 2013 at 10:16:50AM +0100, Romain Francoise wrote:
Hi,
John Stultz writes:
Of course, the xtime_cache is updated at the bottom of
update_wall_time(). So the early return on (offset <
timekeeper.cycle_interval), causes the xtime_cach
Check that the ring does not have an insane amount of requests
(more than there could fit on the ring).
If we detect this case we will stop processing the requests
and wait until the XenBus disconnects the ring.
Looking at the code, one would expect that the existing check
RING_REQUEST_CONS_OVERF
We want to be able to exit if the difference between the request
produced (what the frontend tells us) and the requests consumed
(what we have so far processed) is greater than the ring size.
If so, we should terminate the loop as the request produced
is not trusted and it means it is bogus.
Cc:
The 'handle' is the device that the request is from. For the life-time
of the ring we copy it from a request to a response so that the frontend
is not surprised by it. But we do not need it - when we start processing
I/Os we have our own 'struct phys_req' which has only most essential
information a
This is a note to let you know that I've just added the patch titled
usb: dwc3: gadget: change HIRD threshold to 12
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the next release of
This is a note to let you know that I've just added the patch titled
usb: dwc3: gadget: req->queued must be forced to false in cleanup
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in
This is a note to let you know that I've just added the patch titled
usb: dwc3: gadget: fix isoc END TRANSFER Condition
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the next releas
This is a note to let you know that I've just added the patch titled
usb: dwc3: gadget: fix skip LINK_TRB on ISOC
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the next release of t
This is a note to let you know that I've just added the patch titled
usb: dwc3: gadget: fix missed isoc
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the next release of the linux-n
This is a note to let you know that I've just added the patch titled
usb: dwc3: Enable usb2 LPM only when connected as usb2.0
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the next
This is a note to let you know that I've just added the patch titled
usb: musb: core: fix failure path
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the next release of the linux-ne
This is a note to let you know that I've just added the patch titled
usb: musb: fix dependency on transceiver driver
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the next release o
This is a note to let you know that I've just added the patch titled
usb: musb: ux500: use clk_prepare_enable and clk_disable_unprepare
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in
Recent assembler versions complain about extraneous
whitespace inside [] brackets. This fixes all of
these instances for the samsung platforms. We should
backport this to all kernels that might need to
be built with new binutils.
arch/arm/kernel/entry-armv.S: Assembler messages:
arch/arm/kernel/en
From: Piotr Haber
In the event that tx packet can not be queued by the driver
the packet is dropped. Propagate that information to the .tx()
callback to make sure the freed packet is not accessed after
that.
This has happened causing slab corruptions as reported by
Stanislaw Gruszka.
Bug #47721
On 01/25/2013 03:57 PM, Arend van Spriel wrote:
> From: Piotr Haber
>
> In the event that tx packet can not be queued by the driver
> the packet is dropped. Propagate that information to the .tx()
> callback to make sure the freed packet is not accessed after
> that.
>
> This has happened causin
From: Piotr Haber
In the event that tx packet can not be queued by the driver
the packet is dropped. Propagate that information to the .tx()
callback to make sure the freed packet is not accessed after
that.
This has happened causing slab corruptions as reported by
Stanislaw Gruszka.
Bug #47721
From: YOSHIFUJI Hideaki
digsig_verify_rsa() does not free kmalloc'ed buffer returned by
mpi_get_buffer().
Signed-off-by: YOSHIFUJI Hideaki
Signed-off-by: Dmitry Kasatkin
Cc: stable@vger.kernel.org
---
lib/digsig.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/digsig.c b/lib/dig
On 01/25/2013 03:26 PM, Seth Forshee wrote:
> Also skimming the commits it strikes me that c4dea35 (brcmsmac: handle
> packet drop during transmit correctly) is a good stable candidate,
> though without the above patches it will require some backporting.
I actually had a patch submitted to John fo
Am 25.01.2013 12:57, schrieb Abdallah Chatila:
> On Thu, Jan 24, 2013 at 08:54:02PM -0800, Greg Kroah-Hartman wrote:
>>> However, I've got a build failure with a .config having no PCI:
>>
>> Is this something new that is not a problem in 3.7.4?
>
> No it's not new, a 3.7.4 build failed too with th
On store status we need to copy the current state of registers
into a save area. Currently we might save stale versions:
The sie state descriptor doesnt have fields for guest ACRS,FPRS,
those registers are simply stored in the host registers. The host
program must copy these away if needed. We do t
On Fri, Jan 25, 2013 at 10:37:14AM +0100, Arend van Spriel wrote:
> On 01/25/2013 07:56 AM, CAI Qian wrote:
> > OK, will do.
> >
> > Hello John, Seth etc,
> >
> > Could you please help ACK/NAK for those two commits to be included
> > into the stable?
>
> Hi CAI Qian,
>
> These two patches were
Enable hyperv_clocksource only if its advertised as a feature.
XenServer 6 returns the signature which is checked in
ms_hyperv_platform(), but it does not offer all features. Currently the
clocksource is enabled unconditionally in ms_hyperv_init_platform(), and
the result is a hanging guest.
Hyper
On Thu, Jan 24, 2013 at 08:54:02PM -0800, Greg Kroah-Hartman wrote:
> > However, I've got a build failure with a .config having no PCI:
>
> Is this something new that is not a problem in 3.7.4?
No it's not new, a 3.7.4 build failed too with the same config. I think it's
the same bug reported prev
On Fri, Jan 25, 2013 at 10:16:50AM +0100, Romain Francoise wrote:
> Hi,
>
> John Stultz writes:
>
> > Of course, the xtime_cache is updated at the bottom of
> > update_wall_time(). So the early return on (offset <
> > timekeeper.cycle_interval), causes the xtime_cache to not be updated.
> > Then
On 01/25/2013 07:56 AM, CAI Qian wrote:
> OK, will do.
>
> Hello John, Seth etc,
>
> Could you please help ACK/NAK for those two commits to be included
> into the stable?
Hi CAI Qian,
These two patches were part of a series of 24 (if I remember correctly).
Just taking these two patches will not
Hi,
John Stultz writes:
> Of course, the xtime_cache is updated at the bottom of
> update_wall_time(). So the early return on (offset <
> timekeeper.cycle_interval), causes the xtime_cache to not be updated.
> Then in hrtimer_get_softirq_time(), we pull current_kernel_time() which
> uses the non
Correct value for minimal voltage for ldo10 output is 95 uV. This
patch fixes the typo introduced by patch adf6178ad5552a7f2f742a8c85343c50
("regulator: max8998: Use uV in voltage_map_desc"), what solves broken
probe of max8998 in v3.8-rc4.
Signed-off-by: Marek Szyprowski
Cc: stable@vger.kern
56 matches
Mail list logo
