On Sun, Apr 14, 2013 at 10:53:27PM -0700, Joe Perches wrote:
> On Mon, 2013-04-15 at 07:48 +0200, Heiko Carstens wrote:
> > On Sat, Apr 13, 2013 at 11:06:14PM -0700, Joe Perches wrote:
> > > Commit ea81531d ("s390/uaccess: fix page table walk")
> > > added this code. It looks like it should have
On 04/14/2013 09:52 PM, HATAYAMA Daisuke wrote:
> This sounds like there's no such issue on x86 cache mechanism. Is it
> correct? If so, what is the difference between ia64 and x86 cache
> mechanisms?
I'm just going by the code comments:
drivers/char/mem.c
> /*
>
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
> Hi All,
>
> I hit the below crashed when doing memory related tests[1] on s390x:
>
> --- snip -
> � 15929.351639¨ � <0021c0a6>¨ shrink_inactive_list+0x1c6/0x56c
> � 15929.351647¨ �
On Mon, 2013-04-15 at 07:48 +0200, Heiko Carstens wrote:
> On Sat, Apr 13, 2013 at 11:06:14PM -0700, Joe Perches wrote:
> > Commit ea81531d ("s390/uaccess: fix page table walk")
> > added this code. It looks like it should have break;
> > for each case.
> no, the fallthrough is on purpose for
When hot removing a memory, a firmware_map_entry which has memory range
of the memory is released by release_firmware_map_entry(). If the entry
is allocated by bootmem, release_firmware_map_entry() adds the entry to
map_entires_bootmem list when firmware_map_find_entry() finds the entry
from
On Sat, Apr 13, 2013 at 11:06:14PM -0700, Joe Perches wrote:
> Hello Heiko.
>
> Commit ea81531d ("s390/uaccess: fix page table walk")
> added this code. It looks like it should have break;
> for each case.
Hi Joe,
no, the fallthrough is on purpose for each case statement.
> static unsigned
The latest r1p5-revision of the ARM PL011 UART has 32-byte FIFOs,
while all earlier ones have 16-byte FIFOs. This patch suggests
a way to set the FIFO-size correctly & flexibly by using a member
function named get_fifosize, rather than using the fifosize member
variable. The function takes the
Hi,
one of our servers keeps spitting GPF messages:
(sorry for long message)
[34110.179005] general protection fault: [#1] PREEMPT SMP
[34110.185000] CPU 0
[34110.186872] Modules linked in: ipmi_devintf ipmi_si ipmi_msghandler
ip6table_filter ip6_tables ipt_MASQUERADE ipt_REJECT
From: Lad, Prabhakar
As of now TI has no maintainer/supporter for davinci media
drivers, Until it has any I'll be maintaining it.
Signed-off-by: Lad, Prabhakar
Cc: Sekhar Nori
---
MAINTAINERS |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS
Quoting Tejun Heo (t...@kernel.org):
> Hello, Serge.
>
> On Sun, Apr 14, 2013 at 08:13:36PM -0500, Serge Hallyn wrote:
> > If I do
> >
> > cd /sys/fs/cgroup/memory
> > mkdir b
> > cd b
> > echo 1 > memory.use_hierarchy
> > echo 5000 > memory.limit_in_bytes
> > cat
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
drivers/staging/zcache/ramster/ramster.c between commit df735543008f
("staging: ramster: Move debugfs code out of ramster.c file") from the
staging tree and commit "staging: zcache: enable ramster to be
built/loaded as a
Add basic documentation for virtio-9p. I can expand more on device operation,
but I don't think there's anything significant enough for the spec to be
mentioned there. Please let me know if I'm wrong.
Signed-off-by: Sasha Levin
---
virtio-spec.lyx | 206
From: Namhyung Kim
We now have page_size field in struct pevent, save the actual size of
the system.
Signed-off-by: Namhyung Kim
---
tools/perf/util/trace-event-read.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/trace-event-read.c
Hello,
It seems some code that handle tracepoint events left unchanged when
they were copied from the trace-cmd. This series tries to cleanup
them by removing unnecessary function calls and variables and filling
up some missing pieces.
It's based on my previous patchset on libtraceevent [1] and
From: Namhyung Kim
Save size of long type of system to struct pevent. Since original
static variable was not used anywhere, just get rid of it.
Signed-off-by: Namhyung Kim
---
tools/perf/util/trace-event-read.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git
From: Namhyung Kim
The header_page file describes the format of the ring buffer page
which is used by ftrace (not perf). And size of "commit" field (I
guess it's older name was 'size') represents the real size of long
type used for kernel. So update the pevent's long size.
Signed-off-by:
From: Namhyung Kim
It seems perf does not parse header_event file so we can skip it as we
do for header_page file.
Signed-off-by: Namhyung Kim
---
tools/perf/util/trace-event-read.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/tools/perf/util/trace-event-read.c
From: Namhyung Kim
It's useless to call the read_trace_init() function at this time as we
don't need a returned pevent and it makes me confusing. :)
Signed-off-by: Namhyung Kim
---
tools/perf/util/trace-event-info.c | 2 --
1 file changed, 2 deletions(-)
diff --git
From: Namhyung Kim
They're internals of ftrace ring-buffer and not used in perf code
directly. As it now resides on libtraceevent/kbuffer.h, just get
rid of them.
Signed-off-by: Namhyung Kim
---
tools/perf/util/trace-event.h | 10 --
1 file changed, 10 deletions(-)
diff --git
From: Namhyung Kim
They're not used anywhere, just make them local variables.
Signed-off-by: Namhyung Kim
---
tools/perf/util/trace-event-read.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/tools/perf/util/trace-event-read.c
b/tools/perf/util/trace-event-read.c
From: Namhyung Kim
It's confusing to have same name for two difference functions which
does something opposite way. Since what they do in this file is read
*AND* writing some of tracing metadata files, rename them to
record_*() looks better to me.
Signed-off-by: Namhyung Kim
---
From: Namhyung Kim
It's the only user of the variable, so move it.
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-script.c | 1 +
tools/perf/util/trace-event-parse.c | 2 --
tools/perf/util/trace-event.h | 1 -
3 files changed, 1 insertion(+), 3 deletions(-)
diff --git
From: Namhyung Kim
They're not used anywhere and same information is kept in a pevent
already. So let's get rid of them.
Signed-off-by: Namhyung Kim
---
tools/perf/util/trace-event-parse.c | 4
tools/perf/util/trace-event.h | 4
2 files changed, 8 deletions(-)
diff --git
Hi Mike,
After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
ERROR: "of_clk_add_provider" [drivers/clk/clk-si5351.ko] undefined!
ERROR: "of_clk_src_onecell_get" [drivers/clk/clk-si5351.ko] undefined!
ERROR: "__clk_get_flags" [drivers/clk/clk-si5351.ko]
On Sat, Apr 13, 2013 at 11:36:20PM +0800, Jiang Liu wrote:
> Commit 600cc5b7f6 "mm: Kill NO_BOOTMEM version free_all_bootmem_node()"
> has kill free_all_bootmem_node() for NO_BOOTMEM.
>
> Currently the usage pattern for free_all_bootmem_node() is like:
> for_each_online_pgdat(pgdat)
>
(2013/04/13 7:17), Dave Hansen wrote:
On 04/12/2013 07:56 AM, H. Peter Anvin wrote:
On 04/12/2013 07:31 AM, Vivek Goyal wrote:
I also have to admit that I don't see the difference between /dev/mem
and /dev/oldmem, as the former allows access to memory ranges outside
the ones used by the
We don't export any symbols > 128 characters, but if we did then
kallsyms_expand_symbol() would overflow the buffer handed to it.
So we need check destination buffer length when copying.
the related test:
if we define an EXPORT function which name more than 128.
will panic when
On Mon, 2013-04-15 at 05:22 +0100, Hin-Tak Leung wrote:
> How is converting a few hundred lines of "print nothing" to
> another few hundred lines of "print nothing" functional?
> What does it achieve?
Standardization of output style when enabled.
Easier conversion to pr_debug/dynamic_debugging.
On Wed, Apr 10, 2013 at 7:37 PM, Jonghwan Choi wrote:
> hyp_hvc vector offset should be 0x14 and hyp_svc vector offset should be
> 0x8.
>
> Signed-off-by: Jonghwan Choi
> ---
> arch/arm/kvm/interrupts.S |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On 2013年04月15日 10:05, Rusty Russell wrote:
> Chen Gang writes:
>> > We don't export any symbols > 128 characters, but if we did then
>> > kallsyms_expand_symbol() would overflow the buffer handed to it.
>> > So we need check destination buffer length when copying.
>> >
>> > the related
The job ring init function creates a platform device for each job ring.
While the job ring is shutdown, e.g. while caam module removal, its
platform device was not being removed. This leads to failure while
reinsertion and then removal of caam module second time.
The following kernel crash dump
--- On Mon, 15/4/13, Joe Perches wrote:
> On Mon, 2013-04-15 at 04:46 +0100,
> Hin-Tak Leung wrote:
> > > By converting this dprint() to pr_debug(), it
> would
> > > print out on a multiple lines, one for each read.
> > >
> > > That's why it should use a mechanism like
> dbg_cont.
> > >
> > >
This patch adds preliminary support for the power8 PMU to perf.
Signed-off-by: Michael Ellerman
---
arch/powerpc/perf/Makefile |3 +-
arch/powerpc/perf/power8-pmu.c | 454
2 files changed, 456 insertions(+), 1 deletion(-)
create mode 100644
On Fri, Apr 12, 2013 at 03:40:42PM -0700, David Brown wrote:
> The following changes since commit 6dbe51c251a327e012439c4772097a13df43c5b8:
>
> Linux 3.9-rc1 (2013-03-03 15:11:05 -0800)
>
> are available in the git repository at:
>
>
On Mon, 2013-04-15 at 04:46 +0100, Hin-Tak Leung wrote:
> > By converting this dprint() to pr_debug(), it would
> > print out on a multiple lines, one for each read.
> >
> > That's why it should use a mechanism like dbg_cont.
> >
> > btw: there is no current pr_debug_cont mechanism.
>
> That's
Hey, Li.
On Mon, Apr 15, 2013 at 11:49:57AM +0800, Li Zefan wrote:
> But if id is invalid, idr_find() will return NULL. As long as root is not
> NULL,
> task_cgroup_from_root() will always return a valid cgroup.
I'm hopping across multiple devel branches quickly today and somewhat
tipsy. Sorry
On Fri, Apr 12, 2013 at 03:43:44PM -0700, David Brown wrote:
> The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9:
>
> Linux 3.9-rc2 (2013-03-10 16:54:19 -0700)
>
> are available in the git repository at:
>
>
--- On Mon, 15/4/13, Joe Perches wrote:
> On Mon, 2013-04-15 at 02:56 +0100,
> Hin-Tak Leung wrote:
> > --- On Mon, 15/4/13, Joe Perches
> wrote:
> > > On Mon, 2013-04-15 at 01:53 +0100,
> > > Hin-Tak Leung wrote:
> > > > --- On Mon, 8/4/13, Joe Perches
> wrote:
> > > > > Use a more current
Chen Gang writes:
> We don't export any symbols > 128 characters, but if we did then
> kallsyms_expand_symbol() would overflow the buffer handed to it.
> So we need check destination buffer length when copying.
>
> the related test:
> if we define an EXPORT function which name more
kdbus folks want a sane way to determine the cgroup path that a given
task belongs to on a given hierarchy, which is a reasonble thing to
expect from cgroup core.
Implement task_cgroup_path_from_hierarchy().
v2: Dropped unnecessary NULL check on the return value of
task_cgroup_from_root() as
On 2013/4/15 11:46, Tejun Heo wrote:
> On Mon, Apr 15, 2013 at 11:43:15AM +0800, Li Zefan wrote:
>>> +int task_cgroup_path_from_hierarchy(struct task_struct *task, int
>>> hierarchy_id,
>>> + char *buf, size_t buflen)
>>> +{
>>> + struct cgroupfs_root *root;
>>> +
Veaceslav Falico writes:
> On Wed, Apr 10, 2013 at 04:47:34PM +0930, Rusty Russell wrote:
>>That's a bug. We should be cleaning up sysfs before we unlike the
>>removed module from the list.
>>
>>Because the same thing applies to ddebug info, which is also keyed by
>>module name.
>>
>>Something
Hi,
On Fri, Apr 12, 2013 at 03:43:15PM -0700, David Brown wrote:
> The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9:
>
> Linux 3.9-rc2 (2013-03-10 16:54:19 -0700)
>
> are available in the git repository at:
>
>
On Sun, Apr 14, 2013 at 08:46:13PM -0700, Tejun Heo wrote:
> On Mon, Apr 15, 2013 at 11:43:15AM +0800, Li Zefan wrote:
> > > +int task_cgroup_path_from_hierarchy(struct task_struct *task, int
> > > hierarchy_id,
> > > + char *buf, size_t buflen)
> > > +{
> > > + struct
On Mon, Apr 15, 2013 at 11:43:15AM +0800, Li Zefan wrote:
> > +int task_cgroup_path_from_hierarchy(struct task_struct *task, int
> > hierarchy_id,
> > + char *buf, size_t buflen)
> > +{
> > + struct cgroupfs_root *root;
> > + struct cgroup *cgrp = NULL;
> > +
On 2013/4/15 2:36, Tejun Heo wrote:
> kdbus folks want a sane way to determine the cgroup path that a given
> task belongs to on a given hierarchy, which is a reasonble thing to
> expect from cgroup core.
>
> This patchset make hierarchy_id allocation use idr instead of ida and
> implement
> +int task_cgroup_path_from_hierarchy(struct task_struct *task, int
> hierarchy_id,
> + char *buf, size_t buflen)
> +{
> + struct cgroupfs_root *root;
> + struct cgroup *cgrp = NULL;
> + int ret = -ENOENT;
> +
> + mutex_lock(_mutex);
> +
> +
Hi All,
I hit the below crashed when doing memory related tests[1] on s390x:
--- snip -
� 15929.351639¨ � <0021c0a6>¨ shrink_inactive_list+0x1c6/0x56c
� 15929.351647¨ � <0021c69e>¨ shrink_lruvec+0x252/0x56c
� 15929.351654¨ �
Then make the comment so it is actually possible to understand that.
Yinghai Lu wrote:
>On Sun, Apr 14, 2013 at 6:59 PM, H. Peter Anvin wrote:
>> On 04/11/2013 11:54 PM, Yinghai Lu wrote:
>>
>>> + /*
>>> + * two parts from lib/swiotlb.c:
>>> + *
On Sun, Apr 14, 2013 at 11:36:55AM -0700, Tejun Heo wrote:
> kdbus folks want a sane way to determine the cgroup path that a given
> task belongs to on a given hierarchy, which is a reasonble thing to
> expect from cgroup core.
>
> This patchset make hierarchy_id allocation use idr instead of ida
On Fri, Apr 12, 2013 at 04:10:55PM -0700, Tejun Heo wrote:
> To make progress, those behaviors need to go but we can't simply drop
> or change the crazies as those are directly visible to userland. This
> patchset implements a mount option - sane_behavior - which turns on
> new saner behaviors,
On Sun, Apr 14, 2013 at 6:59 PM, H. Peter Anvin wrote:
> On 04/11/2013 11:54 PM, Yinghai Lu wrote:
>
>> + /*
>> + * two parts from lib/swiotlb.c:
>> + * swiotlb size: user specified with swiotlb= or default.
>> + * swiotlb overflow
On Mon, Apr 15, 2013 at 10:49:15AM +0800, Li Zefan wrote:
> > {
> > + .name = "cgroup.sane_behavior",
> > + .flags = CFTYPE_ONLY_ON_ROOT,
> > + .read_seq_string = cgroup_sane_behavior_show,
> > + .mode = S_IRUGO,
> > + },
>
> We don't have to set
This is the start of the stable review cycle for the 3.8.8 release.
There are 27 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.
Responses should be made by Wed Apr 17 02:41:37 UTC 2013.
Anything
> {
> + .name = "cgroup.sane_behavior",
> + .flags = CFTYPE_ONLY_ON_ROOT,
> + .read_seq_string = cgroup_sane_behavior_show,
> + .mode = S_IRUGO,
> + },
We don't have to set .mode explicitly.
--
To unsubscribe from this list: send the line
On 2013/4/13 7:10, Tejun Heo wrote:
> It's a sad fact that at this point various cgroup controllers are
> carrying so many idiosyncrasies and pure insanities that it simply
> isn't possible to reach any sort of sane consistent behavior while
> staying compatible with what already has been exposed
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Namhyung Kim
commit 83e03b3fe4daffdebbb42151d5410d730ae50bd1 upstream.
On the failure path, stat->start and stat->pages will refer same page.
So it'll attempt to free the same page again and
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Joonyoung Shim
commit 0eaa6cca1f75e12e4f5ec62cbe887330fe3b5fe9 upstream.
It can be 0 or 1 return value of snd_soc_update_bits_locked() when it is
success. So just check return value is
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Alban Bedel
commit f1ca493b0b5e8f42d3b2dc8877860db2983f47b6 upstream.
The Charge Pump needs the DSP clock to work properly, without it the
bypass to HP/LINEOUT is not working properly. This
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Nigel Roberts
commit 8f08d6667287241f6818d35e02b223fb5df97cf1 upstream.
In the conversion to pinctrl, an error in the pins for the rebuild
LED was introduced. This patch assigns the correct
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Markus Pargmann
commit 75498083e25e96932ad998ffdeadb17234c68d3a upstream.
The admux clock seems to be the audmux clock as tests show. audmux does
not work without this clock enabled. Currently
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Ujfalusi
commit 765024697807ad1e1cac332aa891253ca4a339da upstream.
cyclic DMA is only used by audio which needs DMA to be started without a
delay.
If the DMA for audio is started using
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Whitehouse
commit c2952d202f710d326ac36a8ea6bd216b20615ec8 upstream.
When withdraw occurs, we need to continue to allow unlocks of fcntl
locks to occur, however these will only be
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Yongjun
commit 441362d06be349430d06e37286adce4b90e6ce96 upstream.
The error code in gfs2_rs_alloc() is set to ENOMEM when error
but never be used, instead, gfs2_rs_alloc() always return 0.
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislav Kinsbursky
commit 2dc958fa2fe6987e7ab106bd97029a09a82fcd8d upstream.
Make sure that msg pointer is set back to error value in case of
MSG_COPY flag is set and desired message to copy
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Sachin Prabhu
commit c369c9a4a7c82d33329d869cbaf93304cc7a0c40 upstream.
Fixes a regression in cifs_parse_mount_options where a password
which begins with a delimitor is parsed incorrectly as
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit a49b7e82cab0f9b41f483359be83f44fbb6b4979 upstream.
Anatol Pomozov identified a race condition that hits module unloading
and re-loading. To quote Anatol:
"This is a
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Haojian Zhuang
commit ad4e1a7caf937ad395ced585ca85a7d14395dc80 upstream.
If index++ calculates from 0, the checking condition of "while
(index++)" fails & it doesn't check any more. It doesn't
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit a1cbcaa9ea87b87a96b9fc465951dcf36e459ca2 upstream.
The sched_clock_remote() implementation has the following inatomicity
problem on 32bit systems when accessing the
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Bellinger
commit 30f359a6f9da65a66de8cadf959f0f4a0d498bba upstream.
This patch fixes a bug where a handful of informational / control CDBs
that should be allowed during ALUA access
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
commit 1de14c3c5cbc9bb17e9dcc648cda51c0c85d54b9 upstream.
This patch attempts to fix:
https://bugzilla.kernel.org/show_bug.cgi?id=56461
The symptom is a crash and
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Airlie
commit 1baee58638fc58248625255f5c5fcdb987f11b1f upstream.
Don't oops seems proper.
Signed-off-by: Dave Airlie
Signed-off-by: Greg Kroah-Hartman
---
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Boris Ostrovsky
commit 511ba86e1d386f671084b5d0e6f110bb30b8eeb2 upstream.
Invoking arch_flush_lazy_mmu_mode() results in calls to
preempt_enable()/disable() which may have performance impact.
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Namhyung Kim
commit 6a76f8c0ab19f215af2a3442870eeb5f0e81998d upstream.
Currently set_ftrace_pid and set_graph_function files use seq_lseek
for their fops. However seq_open() is called only
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
commit 852e4a8152b427c3f318bb0e1b5e938d64dcdc32 upstream.
Since commit 89c8d91e31f2 ("tty: localise the lock") I see a dead lock
in one of my dummy_hcd + g_nokia test
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: "Steven Rostedt (Red Hat)"
commit 7f49ef69db6bbf756c0abca7e9b65b32e999eec8 upstream.
As ftrace_filter_lseek is now used with ftrace_pid_fops, it needs to
be moved out of the #ifdef
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Samu Kallio
commit 1160c2779b826c6f5c08e5cc542de58fd1f667d5 upstream.
In paravirtualized x86_64 kernels, vmalloc_fault may cause an oops
when lazy MMU updates are enabled, because set_pgd
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Lukasz Dorau
commit d4a2618fa77b5e58ec15342972bd3505a1c3f551 upstream.
If a result of the SMP discover function is PHY VACANT,
the content of discover response structure (dr) is not valid.
It
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Suleiman Souhlal
commit 5b55d708335a9e3e4f61f2dadf7511502205ccd1 upstream.
Revert commit 62a3ddef6181 ("vfs: fix spinning prevention in prune_icache_sb").
This commit doesn't look right:
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Eldad Zack
commit 889d66848b12d891248b03abcb2a42047f8e172a upstream.
The usb_control_msg() function expects __u16 types and performs
the endianness conversions by itself.
However, in three
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Huacai Chen
commit 6f389a8f1dd22a24f3d9afc2812b30d639e94625 upstream.
As commit 40dc166c (PM / Core: Introduce struct syscore_ops for core
subsystems PM) say, syscore_ops operations should be
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: "John W. Linville"
commit 54683441a92ebe20c5282465ea6f21e5e74d2974 upstream.
This reverts commit b6fc28a158076ca2764edc9a6d1e1402f56e1c0c.
This commit is reported to cause a regression in the
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Brown
commit f6f629f8332ea70255f6c60c904270640a21a114 upstream.
Reported-by: Ryo Tsutsui
Signed-off-by: Mark Brown
Signed-off-by: Greg Kroah-Hartman
---
sound/soc/codecs/wm5102.c |
Hello, Serge.
On Sun, Apr 14, 2013 at 08:13:36PM -0500, Serge Hallyn wrote:
> If I do
>
> cd /sys/fs/cgroup/memory
> mkdir b
> cd b
> echo 1 > memory.use_hierarchy
> echo 5000 > memory.limit_in_bytes
> cat memory.limit_in_bytes
> 8192
> mkdir c
>
On Sun 14-04-13 20:13:36, Serge Hallyn wrote:
> Quoting Tejun Heo (t...@kernel.org):
> > Turn on use_hierarchy by default if sane_behavior is specified and
> > don't create .use_hierarchy file.
> >
> > It is debatable whether to remove .use_hierarchy file or make it ro as
> > the former could
>> @@ -383,6 +383,7 @@ struct pci_bus *pci_acpi_scan_root(struct acpi_pci_root
>> *root)
>> }
>>
>> pci_scan_child_bus(pbus);
>> + pci_enable_bridges(pbus);
>> return pbus;
>>
>> out3:
>
> I think that with this patch, if you hot-add a PCI host bridge, you
> will
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alban Bedel
commit f1ca493b0b5e8f42d3b2dc8877860db2983f47b6 upstream.
The Charge Pump needs the DSP clock to work properly, without it the
bypass to HP/LINEOUT is not working properly. This
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eldad Zack
commit 889d66848b12d891248b03abcb2a42047f8e172a upstream.
The usb_control_msg() function expects __u16 types and performs
the endianness conversions by itself.
However, in three
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sachin Prabhu
commit c369c9a4a7c82d33329d869cbaf93304cc7a0c40 upstream.
Fixes a regression in cifs_parse_mount_options where a password
which begins with a delimitor is parsed incorrectly as
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Bellinger
commit 30f359a6f9da65a66de8cadf959f0f4a0d498bba upstream.
This patch fixes a bug where a handful of informational / control CDBs
that should be allowed during ALUA access
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Airlie
commit 1baee58638fc58248625255f5c5fcdb987f11b1f upstream.
Don't oops seems proper.
Signed-off-by: Dave Airlie
Signed-off-by: Greg Kroah-Hartman
---
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lukasz Dorau
commit d4a2618fa77b5e58ec15342972bd3505a1c3f551 upstream.
If a result of the SMP discover function is PHY VACANT,
the content of discover response structure (dr) is not valid.
It
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Suleiman Souhlal
commit 5b55d708335a9e3e4f61f2dadf7511502205ccd1 upstream.
Revert commit 62a3ddef6181 ("vfs: fix spinning prevention in prune_icache_sb").
This commit doesn't look right:
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Huacai Chen
commit 6f389a8f1dd22a24f3d9afc2812b30d639e94625 upstream.
As commit 40dc166c (PM / Core: Introduce struct syscore_ops for core
subsystems PM) say, syscore_ops operations should be
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Namhyung Kim
commit 83e03b3fe4daffdebbb42151d5410d730ae50bd1 upstream.
On the failure path, stat->start and stat->pages will refer same page.
So it'll attempt to free the same page again and
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Samu Kallio
commit 1160c2779b826c6f5c08e5cc542de58fd1f667d5 upstream.
In paravirtualized x86_64 kernels, vmalloc_fault may cause an oops
when lazy MMU updates are enabled, because set_pgd
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Hellstrom
commit 4b20db3de8dab005b07c74161cb041db8c5ff3a7 upstream.
This function is intended to simplify locking around refcounting for
objects that can be looked up from a lookup
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 9c603e53d380459fb62fec7cd085acb0b74ac18f upstream.
Sasha Levin has been running trinity in a KVM tools guest, and was able
to trigger the BUG_ON() at
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hayes Wang
commit e2409d83434d77874b461b78af6a19cd6e6a1280 upstream.
It would cause no link after suspending or shutdowning when the
nic changes the speed to 10M and connects to a link partner
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit a49b7e82cab0f9b41f483359be83f44fbb6b4979 upstream.
Anatol Pomozov identified a race condition that hits module unloading
and re-loading. To quote Anatol:
"This is a
1 - 100 of 444 matches
Mail list logo
