On Wed, Jun 04, 2014 at 05:16:18PM +0100, Peter Zijlstra wrote:
> On Wed, Jun 04, 2014 at 04:42:27PM +0100, Morten Rasmussen wrote:
> > On Tue, Jun 03, 2014 at 12:44:28PM +0100, Peter Zijlstra wrote:
> > > On Fri, May 23, 2014 at 07:16:33PM +0100, Morten Rasmussen wrote:
> > > > +static struct capa
Hi
I really do not want to complicate things here, both work course here.
But sptlcpy is definitely faster. But this is hardly time-critical
code, so maybe it looks better to use snprintf in both cases.
I vote for sptlcpy, but who decides?
Someone decides and I submit another patch :-)
Best rega
On 06/06/2014 01:45 AM, Stephen Rothwell wrote:
Hi all,
After merging the net-next tree, today's linux-next build (powerpc allyesconfig)
failed like this:
drivers/net/ethernet/amd/xgbe/xgbe-dev.c:119:25: fatal error: asm/cputype.h: No
such file or directory
#include
On Thu, 2014-06-05 at 16:58 +0200, Daniel Vetter wrote:
> The global gtt is setup up in 2 parts, so we need to be careful
> with the cleanup. For consistency shovel it all into the ->cleanup
> callback, like with ppgtt.
>
> Noticed because it blew up in the out_gtt: cleanup code while
> fiddling w
Currently, we count the number of pages allocated to a per memcg cache
in memcg_cache_params->nr_pages. We only use this counter to find out if
the cache is empty and can be destroyed. So let's rename it to refcnt
and make it count not pages, but slabs so that we can use atomic_inc/dec
instead of a
On Fri, Jun 06, 2014 at 03:16:56PM +0200, Rickard Strandqvist wrote:
> Hi
>
> I really do not want to complicate things here, both work course here.
> But sptlcpy is definitely faster. But this is hardly time-critical
> code, so maybe it looks better to use snprintf in both cases.
>
> I vote for
SLUB's kmem_cache_shrink not only removes empty slabs from the cache,
but also sorts slabs by the number of objects in-use to cope with
fragmentation. To achieve that, it tries to allocate a temporary array.
If it fails, it will abort the whole procedure.
This is unacceptable for kmemcg, where we
Since a dead memcg cache is destroyed only after the last slab allocated
to it is freed, we must disable caching of empty slabs for such caches,
otherwise they will be hanging around forever.
This patch makes SLAB discard dead memcg caches' slabs as soon as they
become empty. To achieve that, it d
This will be used by the next patches.
Signed-off-by: Vladimir Davydov
Acked-by: Christoph Lameter
---
include/linux/slab.h |2 ++
mm/memcontrol.c |1 +
mm/slab.h| 10 ++
3 files changed, 13 insertions(+)
diff --git a/include/linux/slab.h b/include/linux/slab
Since a dead memcg cache is destroyed only after the last slab allocated
to it is freed, we must disable caching of empty slabs for such caches,
otherwise they will be hanging around forever.
This patch makes SLUB discard dead memcg caches' slabs as soon as they
become empty. To achieve that, it d
When the memcg_cache_params->refcnt goes to 0, schedule the worker that
will unregister the cache. To prevent this from happening when the owner
memcg is alive, keep the refcnt incremented during memcg lifetime.
Note, this doesn't guarantee that the cache that belongs to a dead memcg
will go away
Since per memcg cache destruction is scheduled when the last slab is
freed, to avoid use-after-free in kmem_cache_free we should either
rearrange code in kmem_cache_free so that it won't dereference the cache
ptr after freeing the object, or wait for all kmem_cache_free's to
complete before proceed
kmem_cache_free doesn't expect that the cache can be destroyed as soon
as the object is freed, e.g. SLUB's implementation may want to update
cache stats after putting the object to the free list.
Therefore we should wait for all kmem_cache_free's to finish before
proceeding to cache destruction. S
Hi,
When a memcg is turned offline, some of its kmem caches can still have
active objects and therefore cannot be destroyed immediately. Currently,
we simply leak such caches along with the owner memcg, which is bad and
should be resolved.
It would be perfect if we could move all slab pages of su
From: Jeff Layton
Open file description locks have been merged into the Linux kernel for
v3.15. Add the appropriate command-value definitions and an update to
the manual that describes their usage.
ChangeLog:
2014-04-24 Jeff Layton
[BZ#16839]
* manual/llio.texi: add section
The feature will be governed by fc->close_wait. Userspace can enable it in
the same way as auto_inval_data or any other kernel fuse capability.
Signed-off-by: Maxim Patlasov
---
fs/fuse/fuse_i.h |3 +++
fs/fuse/inode.c |4 +++-
include/uapi/linux/fuse.h |3 +++
3 f
Hi,
There is a long-standing demand for synchronous behaviour of fuse_release:
http://sourceforge.net/mailarchive/message.php?msg_id=19343889
http://sourceforge.net/mailarchive/message.php?msg_id=29814693
A year ago Avati and me explained why such a feature would be useful:
http://sourceforge.n
The patch change arguments of fuse_send_readpages to give it access to inode
(will be used in the next patch of patch-set). The change is cosmetic,
no logic changed.
Signed-off-by: Maxim Patlasov
---
fs/fuse/file.c | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
There are two types of I/O activity that can be "in progress" at the time
of fuse_release() execution: asynchronous read-ahead and write-back. The
patch ensures that they are completed before fuse_release_common sends
FUSE_RELEASE to userspace.
So far as fuse_release() waits for end of async I/O,
The patch enables feature by passing 'true' to fuse_file_put in
fuse_release_common.
Previously, this was safe only in special cases when we sure that
multi-threaded userspace won't deadlock if we'll synchronously send
FUSE_RELEASE in the context of read-ahead or write-back callback. Now, it's
alw
If fuse_file_put() is called with sync==true, the user may be blocked for
a while, until userspace ACKs our FUSE_RELEASE request. This blocking must be
uninterruptible. Otherwise request could be interrupted, but file association
in user space remains.
Signed-off-by: Maxim Patlasov
---
fs/fuse/f
On Thu, Jun 05, 2014 at 06:54:35PM +0800, Lai Jiangshan wrote:
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 268a45e..d05a5a1 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -1474,20 +1474,24 @@ static int ttwu_remote(struct task_struct *p, int
> wake_flags)
On Fri, Jun 06, 2014 at 02:15:10PM +0100, Morten Rasmussen wrote:
> > > ARM TC2 has on-chip energy counters for counting energy consumed by the
> > > A7 and A15 clusters. They are fairly accurate.
> >
> > Recent Intel chips have that too; they come packaged as:
> >
> > perf stat -a -e "power/e
On Fri, Jun 6, 2014 at 6:59 AM, Magnus Damm wrote:
> From: Magnus Damm
>
> Add a stub for the CONFIG_OF_ADDRESS=n case of
> of_translate_address(). The return value for the
> stub is false which is in sync with when the full
> version of the function does not support address
> translation. Added
The include of asm/cputype.h breaks the powerpc build. This
include was accidentally left in from driver debugging and
can be removed.
Signed-off-by: Tom Lendacky
---
drivers/net/ethernet/amd/xgbe/xgbe-dev.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/ethernet/amd/xgbe/xgbe
Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com):
> [CC += Eric and containers@]
>
> Hi Manfred,
>
> On Thu, May 29, 2014 at 8:46 PM, Manfred Spraul
> wrote:
> > Right now, each IPC namespace starts with the kernel boot standard
> > settings.
> > This patch changes that:
> > Now each
On Thu, Jun 05, 2014 at 09:42:54PM -0700, Guenter Roeck wrote:
> On Thu, Jun 05, 2014 at 04:19:24PM -0700, Greg Kroah-Hartman wrote:
> > On Wed, Jun 04, 2014 at 09:16:03PM -0700, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 3.4.92 release.
> > > There are 214
On 2014.06.06, at 15:27 , Maxim Patlasov wrote:
> The patch-set resolves the problem by making fuse_release synchronous:
> wait for ACK from userspace for FUSE_RELEASE if the feature is ON.
Why not make this feature per-file with a new flag bit in struct fuse_file_info
rather than as a file-sys
Hi Linus,
Please pull the arm64 patches below for 3.16. In addition, there are
core ftrace patches required for arm64 support which were pulled from
branch provided by Steve Rostedt (https://lkml.org/lkml/2014/5/27/289)
so they'll go into mainline either via the arm64 or the ftrace tree.
There ar
On Fri, Jun 06, 2014 at 06:56:57AM -0700, Greg KH wrote:
> On Fri, Jun 06, 2014 at 12:47:07PM +0200, Jiri Slaby wrote:
> > On 06/04/2014 07:48 AM, Greg KH wrote:
> > > On Wed, May 14, 2014 at 03:11:22PM -0400, Konrad Rzeszutek Wilk wrote:
> > >> Hey Greg
> > >>
> > >> This email is in regards to ba
At Fri, 6 Jun 2014 07:00:22 +0800,
Ming Lei wrote:
>
> On Thu, Jun 5, 2014 at 11:15 PM, Tom Gundersen wrote:
> > On Thu, Jun 5, 2014 at 4:54 PM, Ming Lei wrote:
> >>> Ubuntu currently enables the firmware loader in both the kernel and in
> >>> udev, so would not yet have a problem here at the mo
On 06/04/2014 02:32 PM, Ed Swarthout wrote:
> 6712d2931933ada259b82f06c03a855b19937074 (cpufreq:
> ppc-corenet-cpufreq: Fix __udivdi3 modpost error) used the remainder
> from do_div instead of the quotient. Fix that and add one to ensure
> minimum is met.
>
> Signed-off-by: Ed Swarthout
> ---
>
On Fri, Jun 06, 2014 at 12:47:07PM +0200, Jiri Slaby wrote:
> On 06/04/2014 07:48 AM, Greg KH wrote:
> > On Wed, May 14, 2014 at 03:11:22PM -0400, Konrad Rzeszutek Wilk wrote:
> >> Hey Greg
> >>
> >> This email is in regards to backporting two patches to stable that
> >> fall under the 'performance
On 06/06/2014 04:02 PM, Konrad Rzeszutek Wilk wrote:
> On Fri, Jun 06, 2014 at 06:56:57AM -0700, Greg KH wrote:
>> On Fri, Jun 06, 2014 at 12:47:07PM +0200, Jiri Slaby wrote:
>>> On 06/04/2014 07:48 AM, Greg KH wrote:
On Wed, May 14, 2014 at 03:11:22PM -0400, Konrad Rzeszutek Wilk wrote:
>
On Fri, 6 Jun 2014 01:57:42 +, liyi 00215672
wrote:
> Please see below:
>
> -é®ä»¶å件-
> å件人: Mark Rutland [mailto:mark.rutl...@arm.com]
> åéæ¶é´: 2014å¹´6æ5æ¥ 23:34
> æ¶ä»¶äºº: Yi Li
> æé: ard.biesheu...@linaro.org; Catalin Marinas; Will Deacon; Sudeep
> Ho
The clock driver usually complains when a clock is being prepared
before setting its rate. It is the case here for "core_clk" which
needs to be set at 19.2 MHz before we attempt a prepare_enable().
Signed-off-by: Stephane Viau
---
drivers/gpu/drm/msm/hdmi/hdmi.c | 2 ++
drivers/gpu/drm
On Thu, Jun 05, 2014 at 11:31:01AM -0400, Trond Myklebust wrote:
> This commit reverts the addition of lockdep checking to raw_seqcount_begin
> for the following reasons:
>
> 1) It violates the naming convention that raw_* functions should not
>do lockdep checks (a convention that is also foll
From: Arnaldo Carvalho de Melo
Before:
[acme@zoo linux]$ make -C tools/perf -f tests/make make_static
make: Entering directory `/home/git/linux/tools/perf'
- make_static: cd . && make -f Makefile DESTDIR=/tmp/tmp.JcWuM4Zu9f
LDFLAGS=-static
make: *** [make_static] Error 1
make: Leaving
On Fri, Jun 06, 2014 at 01:27:40PM +0100, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
> > * Peter Zijlstra wrote:
> >
> > > > Voltage is combined with frequency, roughly, voltage is
> > > > proportional to freuquecy, so roughly, power is proportionaly to
> > > > voltage^3. You
> > >
> > >
Hi Jiri,
Experimenting with more topic branches, this time for things you're the
are the original developer and de facto maintainer, the tools/perf/tests/
harness.
This was done on top of your perf/core branch, please let me know if
all is
ok and then you can try pulling from it
From: Arnaldo Carvalho de Melo
When the user does:
make -C tools/perf LDFLAGS=-static
asking for a static build, and the glibc-static (or equivalent) is not
found, the message wasn't clear, stating that one of glibc-devel or
glibc-static wasn't installed, clarify it checking if -static is
pre
On Fri, Jun 6, 2014 at 4:03 PM, Takashi Iwai wrote:
> At Fri, 6 Jun 2014 07:00:22 +0800,
> Ming Lei wrote:
>>
>> On Thu, Jun 5, 2014 at 11:15 PM, Tom Gundersen wrote:
>> > On Thu, Jun 5, 2014 at 4:54 PM, Ming Lei wrote:
>> >>> Ubuntu currently enables the firmware loader in both the kernel and i
On 06/06/2014 03:29 AM, Peter Zijlstra wrote:
>
> Don't think that's useful. If you really want to go do something, try
> the annotation I suggested to get the parisc/sparc32 things correct
> again. Add the __atomic sparse address space and the store()/load()
> accessors.
>
OK. I am not sure wh
On 2014-06-06 05:46, Matias Bjørling wrote:
Hi Jens,
The blk_rq_set_block_pc() overwrites rq->__data_len after its being set in
blk_rq_map_kern().
It leads to some interesting error messages when booted with SCSI device.
Christoph beat you to it, I folded it in with the previous one.
--
Jens
Facilitate getting required 3.3V and 1.0V VDD supply for
OHCI controller on Exynos.
With patches for regulators' nodes merged in 3.15:
c8c253f ARM: dts: Add regulator entries to smdk5420
275dcd2 ARM: dts: add max77686 pmic node for smdk5250,
certain perripherals will now need to ensure that,
they
Facilitate getting required 3.3V and 1.0V VDD supply for
EHCI controller on Exynos.
With patches for regulators' nodes merged in 3.15:
c8c253f ARM: dts: Add regulator entries to smdk5420
275dcd2 ARM: dts: add max77686 pmic node for smdk5250,
certain perripherals will now need to ensure that,
they
On 06/06/14 15:56, Peter Zijlstra wrote:
> On Fri, Jun 06, 2014 at 03:30:55PM +0400, Andrey Ryabinin wrote:
>> While working address sanitizer for kernel I've discovered use-after-free
>> bug in __put_anon_vma.
>> For the last anon_vma, anon_vma->root freed before child anon_vma.
>> Later in anon_v
On Thu, 05 Jun 2014 15:28:33 -
Thomas Gleixner wrote:
> @@ -536,8 +569,9 @@ static int task_blocks_on_rt_mutex(struc
> {
> struct task_struct *owner = rt_mutex_owner(lock);
> struct rt_mutex_waiter *top_waiter = waiter;
> + struct rt_mutex *next_lock = NULL;
> unsigned
On 06/06/2014 06:55 AM, Peter Hurley wrote:
>
> This won't work either, and should generate a compile or link error
> on CONFIG_X86_32.
>
> The auto-sizing done by __cmpxchg() does not substitute the cmpxchg8b
> instruction for the cmpxchg instruction. __X86_CASE_Q is defined as -1 for
> CONFIG_X
On Fri, Jun 06, 2014 at 02:43:03PM +0100, Peter Zijlstra wrote:
> On Fri, Jun 06, 2014 at 02:15:10PM +0100, Morten Rasmussen wrote:
> > > > ARM TC2 has on-chip energy counters for counting energy consumed by the
> > > > A7 and A15 clusters. They are fairly accurate.
> > >
> > > Recent Intel chips
On Fri, Jun 06, 2014 at 10:17:20AM -0400, Pranith Kumar wrote:
> On 06/06/2014 03:29 AM, Peter Zijlstra wrote:
>
> >
> > Don't think that's useful. If you really want to go do something, try
> > the annotation I suggested to get the parisc/sparc32 things correct
> > again. Add the __atomic sparse
On Fri, 2014-06-06 at 11:29 +0100, Leif Lindholm wrote:
> __early_set_fixmap does not do any synchronization when called to set a
> fixmap entry. Add call to flush_vmap_cache().
>
> Tested on hardware.
>
> Signed-off-by: Leif Lindholm
> Tested-by: Graeme Gregory
> Cc: Steve Capper
> ---
> arc
On Thu 05-06-14 14:23:36, Johannes Weiner wrote:
> On Thu, Jun 05, 2014 at 06:43:55PM +0200, Michal Hocko wrote:
> > On Thu 05-06-14 12:10:35, Johannes Weiner wrote:
[...]
> > > It's not about whether hard guarantees are necessary, it's about
> > > getting away without additional fallback semantics
On Fri, 6 Jun 2014, Vladimir Davydov wrote:
> This patch makes SLUB's implementation of kmem_cache_free
> non-preemptable. As a result, synchronize_sched() will work as a barrier
> against kmem_cache_free's in flight, so that issuing it before cache
> destruction will protect us against the use-af
Some users (e.g. Google) would like to have stronger semantic than low
limit offers currently. The fallback mode is not desirable and they
prefer hitting OOM killer rather than ignoring low limit for protected
groups. There are other possible usecases which can benefit from hard
guarantees. I can i
If there is no memcg eligible for reclaim because all groups under the
reclaimed hierarchy are within their guarantee then the global direct
reclaim would end up in the endless loop because zones in the zonelists
are not considered unreclaimable (as per all_unreclaimable) and so the
OOM killer woul
On Fri, 6 Jun 2014, Vladimir Davydov wrote:
> Since a dead memcg cache is destroyed only after the last slab allocated
> to it is freed, we must disable caching of empty slabs for such caches,
> otherwise they will be hanging around forever.
Acked-by: Christoph Lameter
--
To unsubscribe from thi
On Thu, 05 Jun 2014 15:28:33 -
Thomas Gleixner wrote:
> /**
> @@ -764,7 +802,7 @@ __rt_mutex_slowlock(struct rt_mutex *loc
> }
>
> static void rt_mutex_handle_deadlock(int res, int detect_deadlock,
> - struct rtmutex_waiter *w)
> +
On Fri, Jun 06, 2014 at 11:11:49AM -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> Before:
>
> [acme@zoo linux]$ make -C tools/perf -f tests/make make_static
> make: Entering directory `/home/git/linux/tools/perf'
> - make_static: cd . && make -f Makefile DESTDI
Hi Greg,
At Fri, 6 Jun 2014 00:53:10 -0700,
Guenter Roeck wrote:
>
> On Thu, Jun 05, 2014 at 04:20:08PM -0700, Greg Kroah-Hartman wrote:
> > On Wed, Jun 04, 2014 at 04:20:29PM -0700, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 3.14.6 release.
> > > There a
On Fri, Jun 06, 2014 at 11:11:47AM -0300, Arnaldo Carvalho de Melo wrote:
> Hi Jiri,
>
> Experimenting with more topic branches, this time for things you're the
> are the original developer and de facto maintainer, the tools/perf/tests/
> harness.
>
> This was done on top of your per
On Fri, 6 Jun 2014, Vladimir Davydov wrote:
> @@ -740,7 +740,8 @@ static void start_cpu_timer(int cpu)
> }
> }
>
> -static struct array_cache *alloc_arraycache(int node, int entries,
> +static struct array_cache *alloc_arraycache(struct kmem_cache *cachep,
> +
On Fri, Jun 06, 2014 at 10:37:29AM -0400, Mark Salter wrote:
> On Fri, 2014-06-06 at 11:29 +0100, Leif Lindholm wrote:
> > __early_set_fixmap does not do any synchronization when called to set a
> > fixmap entry. Add call to flush_vmap_cache().
> >
> > Tested on hardware.
> >
> > Signed-off-by: L
On Mon, Jun 02, 2014 at 10:09:35AM -0700, Linus Torvalds wrote:
> On Mon, Jun 2, 2014 at 9:25 AM, Peter Zijlstra wrote:
> >
> > And I can't say I'm a particular fan of these ops either, as alternative
> > I'm almost inclined to just exclude parisc from using opt spinning.
>
> Please do.
Somethin
Em Fri, Jun 06, 2014 at 04:51:11PM +0200, Jiri Olsa escreveu:
> On Fri, Jun 06, 2014 at 11:11:47AM -0300, Arnaldo Carvalho de Melo wrote:
> > Hi Jiri,
> >
> > Experimenting with more topic branches, this time for things you're the
> > are the original developer and de facto maintainer, the too
> -Original Message-
> From: Joe Perches [mailto:j...@perches.com]
> Sent: Thursday, June 05, 2014 6:36 PM
> To: Allan, Bruce W
> Cc: a...@canonical.com; linux-kernel@vger.kernel.org; postmaster
> Subject: Re: [PATCH] checkpatch: warn when patch exceeds a maximum
> message size
>
> On Thu,
Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest -next
kernel I've stumbled on the following spew:
[ 269.531162] BUG: unable to handle kernel NULL pointer dereference at
021e
[ 269.531217] IP: llc_ui_sendmsg (net/llc/af_llc.c:912)
[ 269.531232] PGD b6
While working address sanitizer for kernel I've discovered use-after-free
bug in __put_anon_vma.
For the last anon_vma, anon_vma->root freed before child anon_vma.
Later in anon_vma_free(anon_vma) we are referencing to already freed
anon_vma->root
to check rwsem.
This patch puts freeing of child a
On 6/5/2014 9:42 PM, Serge Hallyn wrote:
> Quoting Greg KH (gre...@linuxfoundation.org):
>> On Thu, Jun 05, 2014 at 06:39:09PM -0400, Paul Moore wrote:
>>> On Thursday, June 05, 2014 11:59:11 PM Jiri Kosina wrote:
On Thu, 5 Jun 2014, Greg KH wrote:
> James has had to step back from doing k
On Fri, Jun 06, 2014 at 05:06:07PM +0200, Peter Zijlstra wrote:
> On Mon, Jun 02, 2014 at 10:09:35AM -0700, Linus Torvalds wrote:
> > On Mon, Jun 2, 2014 at 9:25 AM, Peter Zijlstra wrote:
> > >
> > > And I can't say I'm a particular fan of these ops either, as alternative
> > > I'm almost inclined
On Fri, 2014-06-06 at 15:53 +0100, Leif Lindholm wrote:
> On Fri, Jun 06, 2014 at 10:37:29AM -0400, Mark Salter wrote:
> > On Fri, 2014-06-06 at 11:29 +0100, Leif Lindholm wrote:
> > > __early_set_fixmap does not do any synchronization when called to set a
> > > fixmap entry. Add call to flush_vmap
On Fri, Jun 6, 2014 at 10:15 PM, Tom Gundersen wrote:
> On Fri, Jun 6, 2014 at 4:03 PM, Takashi Iwai wrote:
>> At Fri, 6 Jun 2014 07:00:22 +0800,
>> Ming Lei wrote:
>>>
>>> On Thu, Jun 5, 2014 at 11:15 PM, Tom Gundersen wrote:
>>> > On Thu, Jun 5, 2014 at 4:54 PM, Ming Lei wrote:
>>> >>> Ubuntu
Tomi/Jean can you please ack merging this through drm-intel trees? It
just exports the vga and dummy consoles so that i915 can do what it
needs to do.
Thanks, Daniel
On Thu, Jun 5, 2014 at 4:58 PM, Daniel Vetter wrote:
> Touching the VGA resources on an IVB EFI machine causes hard hangs when
> w
On Fri, 6 Jun 2014 02:51:41 -0400
"Chen, Gong" wrote:
> +/*
> + * MCE Extended Error Log trace event
> + *
> + * These events are generated when hardware detects a corrected or
> + * uncorrected event.
> + */
> +
> +/* memory trace event */
> +
> +TRACE_EVENT(extlog_mem_event,
> + TP_PROTO(s
On Fri, Jun 06, 2014 at 04:15:03PM +0200, Tom Gundersen wrote:
> How about:
>
> "If you rely on a customized udev (or other userspace tool) to load
> firmware from a non-standard path, say Y. Otherwise, say N. If your
> udev version does not support firmware loading (which is currently the
> upstr
Quoting Casey Schaufler (ca...@schaufler-ca.com):
> On 6/5/2014 9:42 PM, Serge Hallyn wrote:
> > Quoting Greg KH (gre...@linuxfoundation.org):
> >> On Thu, Jun 05, 2014 at 06:39:09PM -0400, Paul Moore wrote:
> >>> On Thursday, June 05, 2014 11:59:11 PM Jiri Kosina wrote:
> On Thu, 5 Jun 2014,
On Fri, Jun 6, 2014 at 11:19 AM, Ming Lei wrote:
> On Fri, Jun 6, 2014 at 10:15 PM, Tom Gundersen wrote:
>> On Fri, Jun 6, 2014 at 4:03 PM, Takashi Iwai wrote:
>>> At Fri, 6 Jun 2014 07:00:22 +0800,
>>> Ming Lei wrote:
On Thu, Jun 5, 2014 at 11:15 PM, Tom Gundersen wrote:
> On Th
On Fri, 2014-06-06 at 15:08 +, Allan, Bruce W wrote:
> > -Original Message-
> > From: Joe Perches [mailto:j...@perches.com]
> > Sent: Thursday, June 05, 2014 6:36 PM
> > To: Allan, Bruce W
> > Cc: a...@canonical.com; linux-kernel@vger.kernel.org; postmaster
> > Subject: Re: [PATCH] chec
At Fri, 6 Jun 2014 08:22:40 -0700,
Greg KH wrote:
>
> This is all bikeshedding, right?
Of course, what else? :)
Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
y_sel {
>>> + rmii-clock-ext;
>>> +};
>>> +
>>> &i2c0 {
>>> status = "okay";
>>> pinctrl-names = "default";
>>>
>> Where does this apply on?
>> With linux-next next-20140506 tag, and this p
Laxman,
This patch has already been applied, but ...
> The ams AS3722 is a compact system PMU suitable for mobile phones,
> tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
> controller, 11 LDOs, RTC, automatic battery, temperature and
> over-current monitoring, 8 GPIOs, ADC an
Hello, Michal.
On Fri, Jun 06, 2014 at 04:46:50PM +0200, Michal Hocko wrote:
> +choice
> + prompt "Memory Resource Controller reclaim protection"
> + depends on MEMCG
> + help
Why is this necessary?
- This doesn't affect boot.
- memcg requires runtime config *anyway*.
- The config
On Fri, Jun 06, 2014 at 07:09:30PM +0400, Andrey Ryabinin wrote:
> While working address sanitizer for kernel I've discovered use-after-free
> bug in __put_anon_vma.
> For the last anon_vma, anon_vma->root freed before child anon_vma.
> Later in anon_vma_free(anon_vma) we are referencing to already
On Fri, Jun 06, 2014 at 11:51:42PM +0900, Satoru Takeuchi wrote:
> Hi Greg,
>
> At Fri, 6 Jun 2014 00:53:10 -0700,
> Guenter Roeck wrote:
> >
> > On Thu, Jun 05, 2014 at 04:20:08PM -0700, Greg Kroah-Hartman wrote:
> > > On Wed, Jun 04, 2014 at 04:20:29PM -0700, Greg Kroah-Hartman wrote:
> > > > T
On Fri, 2014-06-06 at 08:26 -0700, Joe Perches wrote:
> On Fri, 2014-06-06 at 15:08 +, Allan, Bruce W wrote:
> > From: Joe Perches [mailto:j...@perches.com]
> > Sent: Thursday, June 05, 2014 6:36 PM
> > > On Thu, 2014-06-05 at 17:00 -0700, Bruce Allan wrote:
> > > > the maximum message size (10
A bit of addition.
Let's *please* think through how memcg should be configured and
different knobs / limits interact with each other and come up with a
consistent scheme before adding more shits on top. This "oh I know
this use case and maybe that behavior is necessary too, let's add N
different
> -Original Message-
> From: Joe Perches [mailto:j...@perches.com]
> Sent: Friday, June 06, 2014 8:34 AM
> To: Allan, Bruce W
> Cc: a...@canonical.com; linux-kernel@vger.kernel.org; postmaster
> Subject: Re: [PATCH] checkpatch: warn when patch exceeds a maximum
> message size
>
> On Fri, 2
On 6/6/2014 8:23 AM, Serge E. Hallyn wrote:
> Quoting Casey Schaufler (ca...@schaufler-ca.com):
>> On 6/5/2014 9:42 PM, Serge Hallyn wrote:
>>> Quoting Greg KH (gre...@linuxfoundation.org):
On Thu, Jun 05, 2014 at 06:39:09PM -0400, Paul Moore wrote:
> On Thursday, June 05, 2014 11:59:11 PM
On Fri, Jun 06, 2014 at 11:08:33AM -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 spew:
>
> [ 269.531162] BUG: unable to handle kernel NULL pointer dereference at
> 0
On Fri, 2014-06-06 at 17:06 +0200, Peter Zijlstra wrote:
> On Mon, Jun 02, 2014 at 10:09:35AM -0700, Linus Torvalds wrote:
> > On Mon, Jun 2, 2014 at 9:25 AM, Peter Zijlstra wrote:
> > >
> > > And I can't say I'm a particular fan of these ops either, as alternative
> > > I'm almost inclined to jus
On Wed, Jun 04, 2014 at 04:09:42PM -0400, Rik van Riel wrote:
> The first thing task_numa_migrate does is check to see if there is
> CPU capacity available on the preferred node, in order to move the
> task there.
>
> However, if the preferred node is all busy, we would skip considering
> that nod
On Fri, Jun 06, 2014 at 05:35:58PM +0200, Tom Gundersen wrote:
>
> On 6 Jun 2014 17:22, "Greg KH" wrote:
> >
> > On Fri, Jun 06, 2014 at 04:15:03PM +0200, Tom Gundersen wrote:
> > > How about:
> > >
> > > "If you rely on a customized udev (or other userspace tool) to load
> > > firmware from a no
> -Original Message-
> From: Joe Perches [mailto:j...@perches.com]
> Sent: Friday, June 06, 2014 8:27 AM
> To: Allan, Bruce W
> Cc: a...@canonical.com; linux-kernel@vger.kernel.org; postmaster
> Subject: Re: [PATCH] checkpatch: warn when patch exceeds a maximum
> message size
>
> On Fri, 2
On Fri, 2014-06-06 at 15:35 +, Allan, Bruce W wrote:
> > Message size exceeding 100 000 characters causes blocking.
> >
> > But I believe that info is out of date.
> >
> If it is out of date, can you explain how/why we got stung by it?
Dunno.
Too many recipients maybe?
cc'ing more than
Em Fri, Jun 06, 2014 at 04:50:23PM +0200, Jiri Olsa escreveu:
> On Fri, Jun 06, 2014 at 11:11:49AM -0300, Arnaldo Carvalho de Melo wrote:
> > From: Arnaldo Carvalho de Melo
> > +++ b/tools/perf/tests/make
> > @@ -205,8 +205,7 @@ $(run):
> > ( eval $$cmd ) >> $@ 2>&1; \
> > echo " test: $(
On Thu, 5 Jun 2014 08:55:20 +0200
Peter Zijlstra wrote:
> On Wed, Jun 04, 2014 at 01:58:12AM -0700, Jacob Pan wrote:
> > On Wed, 4 Jun 2014 10:54:18 +0200
> > Peter Zijlstra wrote:
> >
> > >
> > > I'm still sitting on this patch. Jacub you were going to make it
> > > play nice with QoS?
> > >
On Fri, Jun 06, 2014 at 07:44:08PM +0900, Magnus Damm wrote:
> staging: Emma Mobile USB driver and KZM9D board code V3
>
> [PATCH v3 01/05] staging: emxx_udc: Add Emma Mobile USB Gadget driver
> [PATCH v3 02/05] staging: emxx_udc: I/O memory and IRQ resource support
> [PATCH v3 03/05] staging: emx
On 05/06/14 13:55, Mauro Carvalho Chehab wrote:
> Linus,
>
> Please pull from:
> git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
> topic/adv76xx
>
> For adv7604 driver updates, including DT support.
Can we use the adv7611 for the adv7612 with these?
--
Ben Dooks
urceforge.net
> Cc: net...@vger.kernel.org
> Cc: de...@driverdev.osuosl.org
> Cc: linux-fsde...@vger.kernel.org
> Cc: b.a.t.m@lists.open-mesh.org
> Cc: bri...@lists.linux-foundation.org
> ---
> Patch based on "Add linux-next specific files for 20140606"
>
> driver
On Fri, Jun 06, 2014 at 11:40:50AM +0200, Daniel Vetter wrote:
> On Fri, Jun 06, 2014 at 10:47:25AM +0200, David Herrmann wrote:
> > Hi
> >
> > On Fri, Jun 6, 2014 at 9:56 AM, Daniel Vetter wrote:
> > > On Fri, Jun 06, 2014 at 09:24:35AM +0200, David Herrmann wrote:
> > >> Hi
> > >>
> > >> On Thu
201 - 300 of 673 matches
Mail list logo
