The orion watchdog is expecting to be passed the physcial address of
the hardware, and will ioremap() it to give a virtual address it will
use as the base address for the hardware. However, when creating the
platform resource record, a virtual address was being used.
Add the necassary #define's so
From: Marc Kleine-Budde
In commit:
98d9986 ARM: Kirkwood: Replace clock gating
the kirkwood clock gating has been reworked. A custom variant of
clock gating, that calls a custom function before gating the clock
off, has been introduced. However in clk_register_gate_fn() this
custom function "
The following crash results from cases where the end_device has been
removed before scsi_sysfs_add_sdev has had a chance to run.
BUG: unable to handle kernel NULL pointer dereference at 0098
IP: [] sysfs_create_dir+0x32/0xb6
...
Call Trace:
[] kobject_add_internal+0x120/0x1e3
[
commit 198439e4 [SCSI] libsas: do not set res = 0 in sas_ex_discover_dev()
commit 19252de6 [SCSI] libsas: fix wide port hotplug issues
The above commits seem to have confused the return value of
sas_ex_discover_dev which is non-zero on failure and
sas_ex_join_wide_port which just indicates short c
Continue running revalidation until no more broadcast devices are
discovered. Fixes cases where re-discovery completes too early in a
domain with multiple expanders with pending re-discovery events.
Servicing BCNs can get backed up behind error recovery.
Cc:
Signed-off-by: Dan Williams
---
dri
Rapid ata hotplug on a libsas controller results in cases where libsas
is waiting indefinitely on eh to perform an ata probe.
A race exists between scsi_schedule_eh() and scsi_restart_operations()
in the case when scsi_restart_operations() issues i/o to other devices
in the sas domain. When this
On Thu, 2012-06-21 at 16:18 +0800, Keng-Yu Lin wrote:
> From: wwang
>
> commit 0d05568ac79bfc595f1eadc3e0fd7a20a45f7b69 upstream.
>
> rtsx_transport.c (rtsx_transfer_sglist_adma_partial):
> pointer struct scatterlist *sg, which is mapped in dma_map_sg,
> is used as an iterator in later transfer
On Sun, 2012-06-17 at 23:02 -0700, Jeff Kirsher wrote:
> From: Chris Boot
>
> commit id 59aed95263bdd0e2b48eb9be5a94346d2d4abf90
> Backport to 3.2-3.4 kernels
>
> For the 82573, ASPM L1 gets disabled wholesale so this special-case code
> is not required. For the 82574 the previous patch does the
On Tue, 2012-06-19 at 15:52 +0300, Timo Aaltonen wrote:
> From: Eric Anholt
>
> As a workaround for IRQ synchronization issues in the gen7 BLT ring,
> we want to turn the two wait functions into polling loops.
>
> Signed-off-by: Eric Anholt
> Tested-by: Eugeni Dodonov
> Reviewed-by: Eugeni Dod
When poweroff machine, kernel_power_off() call disable_nonboot_cpus().
And if we have HOTPLUG_CPU configured, disable_nonboot_cpus() is not an
empty function but attempt to actually disable the nonboot cpus. Since
system state is SYSTEM_POWER_OFF, play_dead() won't be called and thus
disable_nonboo
commit: 30c1dc0ff30b5552e8af555265dbeac5637cbb48
From: Tushar Behera
Date: Wed, 23 May 2012 16:47:31 +0530
Subject: dmaengine: pl330: dont complete descriptor for cyclic dma
Commit eab215855803 ("dmaengine: pl330: dont complete descriptor for
cyclic dma") wrongly completes descriptor for cyclic d
commit: 967db0ea65b0bf8507a7643ac8f296c4f2c0a834
From: Salman Qazi
Date: Wed, 6 Jun 2012 18:51:35 -0700
Subject: cgroup: make sure that decisions in __css_put are atomic
__css_put is using atomic_dec on the ref count, and then
looking at the ref count to make decisions. This is prone
to races, a
commit: ac852edb47b15900886ba2564eeeb13b3b526e3e
From: Henrik Rydberg
Date: Thu, 7 Jun 2012 04:54:29 -0400
Subject: hwmon: (applesmc) Limit key length in warning messages
Key lookups may call read_smc() with a fixed-length key string,
and if the lookup fails, trailing stack content may appear in
From: Jeff Kirsher
Date: Thu, 21 Jun 2012 04:29:44 -0700
> From: Bruce Allan
>
> commit id 470a54207ccf7045a59df727573bd9d148988582
> Backport for 3.4 kernel
>
> commit 44abd5c12767a8c567dc4e45fd9aec3b13ca85e0 introduced NULL pointer
> dereferences when attempting to access the check_reset_blo
The patch titled
Subject: mm, thp: abort compaction if migration page cannot be charged to
memcg
has been added to the -mm tree. Its filename is
mm-thp-abort-compaction-if-migration-page-cannot-be-charged-to-memcg.patch
Before you just go and hit "reply", please:
a) Consider who el
The patch titled
Subject: mm/memblock: fix overlapping allocation when doubling reserved
array
has been removed from the -mm tree. Its filename was
mm-memblock-fix-overlapping-allocation-when-doubling-reserved-array.patch
This patch was dropped because it was merged into mainline or a
The patch titled
Subject: mm: correctly synchronize rss-counters at exit/exec
has been removed from the -mm tree. Its filename was
mm-correctly-synchronize-rss-counters-at-exit-exec.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tr
The patch titled
Subject: nilfs2: ensure proper cache clearing for gc-inodes
has been removed from the -mm tree. Its filename was
nilfs2-ensure-proper-cache-clearing-for-gc-inodes.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree
The patch titled
Subject: thp: avoid atomic64_read in pmd_read_atomic for 32bit PAE
has been removed from the -mm tree. Its filename was
thp-avoid-atomic64_read-in-pmd_read_atomic-for-32bit-pae.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The cu
The patch titled
Subject: mm: fix slab->page _count corruption when using slub
has been removed from the -mm tree. Its filename was
mm-fix-slab-page-_count-corruption-when-using-slub.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm t
On Thu, 21 Jun 2012, Oleg Nesterov wrote:
> On 06/20, Andrew Morton wrote:
> > On Wed, 20 Jun 2012 12:53:01 -0700
> > a...@linux-foundation.org wrote:
> >
> > > From: Konstantin Khlebnikov
> > > Subject: mm: correctly synchronize rss-counters at exit/exec
> > >
> > > do_exit() and exec_mmap() call
On Fri, Jun 22, 2012 at 12:12 AM, Alan Stern wrote:
> On Fri, 22 Jun 2012, Ming Lei wrote:
>
>> On Thu, Jun 21, 2012 at 9:49 PM, Greg Kroah-Hartman
>> wrote:
>>
>> > We also have not made the rule that a shutdown will complete in a
>> > specific amount of time either, so there is no problem if th
On Fri, 22 Jun 2012, Ming Lei wrote:
> On Thu, Jun 21, 2012 at 9:49 PM, Greg Kroah-Hartman
> wrote:
>
> > We also have not made the rule that a shutdown will complete in a
> > specific amount of time either, so there is no problem if that takes a
> > long time as well.
>
> OK, I will submit a n
On Thu, Jun 21, 2012 at 9:49 PM, Greg Kroah-Hartman
wrote:
> We also have not made the rule that a shutdown will complete in a
> specific amount of time either, so there is no problem if that takes a
> long time as well.
OK, I will submit a new patch which just holds device lock.
Alan, do you h
On 06/20, Andrew Morton wrote:
>
> On Wed, 20 Jun 2012 12:53:01 -0700
> a...@linux-foundation.org wrote:
>
> > From: Konstantin Khlebnikov
> > Subject: mm: correctly synchronize rss-counters at exit/exec
> >
> > do_exit() and exec_mmap() call sync_mm_rss() before mm_release() does
> > put_user(cle
On Wed, Jun 20, 2012 at 02:01:28PM -0400, Jeff Moyer wrote:
[...]
> This needs backporting to the stable trees where the offending commit
> was backported. I'm sure that includes 3.0 and 3.3, but not sure where
> else it was committed.
3.2 as well.
> Is there an easy way to tell what trees got t
On Thu, Jun 21, 2012 at 09:21:08AM +0800, Ming Lei wrote:
> On Thu, Jun 21, 2012 at 6:37 AM, Greg Kroah-Hartman
> wrote:
> > On Tue, Jun 19, 2012 at 10:00:36AM +0800, Ming Lei wrote:
>
> >> so I marked it as -stable because I have explained how the race can be
> >> exploited in reality.
> >
> > O
On Thu, 21 Jun 2012 14:55:22 +0200, Daniel Vetter
wrote:
> After banging my head against this for the past few months, I still
> don't see how this could possible race under the premise that once an
> irq bit is masked in PM_IMR and reset in PM_IIR it won't show up again
> until we unmask it in P
After banging my head against this for the past few months, I still
don't see how this could possible race under the premise that once an
irq bit is masked in PM_IMR and reset in PM_IIR it won't show up again
until we unmask it in PM_IMR.
Still, we have reports of this being seen in the wild. Now
On 06/20/2012 08:01 PM, Greg KH wrote:
Thanks, I've added this to the patch.
Hi Greg,
If you think it is important enough, you can add my
Tested-by: Wouter M. Koolen
At any rate, thank you!
Thanks
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message
From: Bruce Allan
commit id 470a54207ccf7045a59df727573bd9d148988582
Backport for 3.4 kernel
commit 44abd5c12767a8c567dc4e45fd9aec3b13ca85e0 introduced NULL pointer
dereferences when attempting to access the check_reset_block function
pointer on 8257x and 80003es2lan non-copper devices.
Signed-
This is a fix for v3.4 stable kernel. Mainline commit is
3568f2a46f2a73bab18c914df06afd98a97e0e0e. As a clarification to the original
commit description below: when the bug happens the display does not show
anything.
There is a problem related to DSS FIFO thresholds and power management
on OMAP3.
From: wwang
commit 0d05568ac79bfc595f1eadc3e0fd7a20a45f7b69 upstream.
rtsx_transport.c (rtsx_transfer_sglist_adma_partial):
pointer struct scatterlist *sg, which is mapped in dma_map_sg,
is used as an iterator in later transfer operation. It is corrupted and
passed to dma_unmap_sg, thus causing
33 matches
Mail list logo
