Re: [PATCH 1/3] mm: sl[aou]b: introduce kmem_cache_zalloc_node()

On Mon, 10 Nov 2014, Andrey Ryabinin wrote: > kmem_cache_zalloc_node() allocates zeroed memory for a particular > cache from a specified memory node. To be used for struct irq_desc. > Is there a reason to add this for such a specialized purpose to the slab allocator? I think it can just be

Re: [PATCH v5 1/4] mfd: rt5033: Add Richtek RT5033 driver core.

On 11/20/2014 01:37 AM, Lee Jones wrote: > On Wed, 19 Nov 2014, Beomho Seo wrote: > >> This patch adds a new driver for Richtek RT5033 driver. >> RT5033 is a Multifunction device which includes battery charger, fuel gauge, >> flash LED current source, LDO and synchronous Buck converter. It is >>

Re: [PATCHv9 4/5] sparc: Hook up execveat system call.

Hi David, On Wed, 19 Nov 2014 17:27:51 + David Drysdale wrote: > > diff --git a/arch/sparc/kernel/systbls_64.S b/arch/sparc/kernel/systbls_64.S > index 580cde9370c9..15069cb35dac 100644 > --- a/arch/sparc/kernel/systbls_64.S > +++ b/arch/sparc/kernel/systbls_64.S > @@ -88,6 +88,7 @@

Re: [PATCH v3 3/3] sched, x86: Check that we're on the right stack in schedule and __might_sleep

On Wed, Nov 19, 2014 at 3:32 PM, Thomas Gleixner wrote: > > preempt_count is a per cpu variable at least on x86 since: Oh, goodie. I hadn't tracked that it went in, I just remembered the discussion. I should have looked. And apparently we do it in nmi_enter too, so NMI is already ok. Don't know

RE: [PATCH v3] x86/mce: Try printing all machine check banks known before panic

>> No information besides that it is a machine check. This happens in two cases: >> 1) The CPU logs the error with the MCi_STATUS.EN bit set to zero, and Linux >>ignores EN=0 entries (as it should). > Well, I guess we shouldn't anymore. Apparently hw forgets to set the > bit when raising an

Re: [PATCH v3 3/3] sched, x86: Check that we're on the right stack in schedule and __might_sleep

On Wed, 19 Nov 2014, Linus Torvalds wrote: > On Wed, Nov 19, 2014 at 3:04 PM, Andy Lutomirski wrote: > > > > Does that include nmi? I'm a bit afraid of touching that code. > > NMI is kind of special, since it's really not supposed to touch > 'current' or anything like that, and that's how we

[for-next][PATCH 01/18] tracing: Fix race of function probes counting

From: "Steven Rostedt (Red Hat)" The function probe counting for traceon and traceoff suffered a race condition where if the probe was executing on two or more CPUs at the same time, it could decrement the counter by more than one when disabling (or enabling) the tracer only once. The way the

Re: [PATCH] zram: rely on the bi_end_io for zram_rw_page fails

Hello, On Wed, Nov 19, 2014 at 01:15:35PM -0800, Andrew Morton wrote: > On Wed, 19 Nov 2014 08:52:01 +0900 Minchan Kim wrote: > > > > > > > > > - /* > > > > -* Return 0 prevents I/O fallback trial caused by rw_page fail > > > > -* and upper layer can handle this IO error

[for-next][PATCH 02/18] ftrace/x86: Add frames pointers to trampoline as necessary

From: "Steven Rostedt (Red Hat)" When CONFIG_FRAME_POINTERS are enabled, it is required that the ftrace_caller and ftrace_regs_caller trampolines set up frame pointers otherwise a stack trace from a function call wont print the functions that called the trampoline. This is due to a check in

[for-next][PATCH 03/18] ftrace/x86/extable: Add is_ftrace_trampoline() function

From: "Steven Rostedt (Red Hat)" Stack traces that happen from function tracing check if the address on the stack is a __kernel_text_address(). That is, is the address kernel code. This calls core_kernel_text() which returns true if the address is part of the builtin kernel code. It also calls

[for-next][PATCH 09/18] ring-buffer: Remove check of trace_seq_{puts,printf}() return values

From: "Steven Rostedt (Red Hat)" Remove checking the return value of all trace_seq_puts(). It was wrong anyway as only the last return value mattered. But as the trace_seq_puts() is going to be a void function in the future, we should not be checking the return value of it anyway. Just return

[for-next][PATCH 06/18] tracing: Fix trace_seq_bitmask() to start at current position

From: "Steven Rostedt (Red Hat)" In trace_seq_bitmask() it calls bitmap_scnprintf() not from the current position of the trace_seq buffer (s->buffer + s->len), but instead from the beginning of the buffer (s->buffer). Luckily, the only user of this "ipi_raise tracepoint" uses it as the first

Re: [PATCH v5] sched/deadline: support dl task migration during cpu hotplug

Hi Juri, On Wed, Nov 19, 2014 at 01:49:20PM +, Juri Lelli wrote: [...] >> @@ -1185,8 +1223,9 @@ static int find_later_rq(struct task_struct *task) >> * We have to consider system topology and task affinity >> * first, then we can look for a suitable cpu. >>

[for-next][PATCH 08/18] blktrace/tracing: Use trace_seq_has_overflowed() helper function

From: "Steven Rostedt (Red Hat)" Checking the return code of every trace_seq_printf() operation and having to return early if it overflowed makes the code messy. Using the new trace_seq_has_overflowed() and trace_handle_return() functions allows us to clean up the code. In the future,

Re: [PATCH 0/7] Fixes for ALPS trackstick

On Monday 17 November 2014 08:39:14 Pali Rohár wrote: > On Friday 14 November 2014 21:59:31 Dmitry Torokhov wrote: > > Hi Pali, > > > > On Friday, November 14, 2014 08:38:19 PM Pali Rohár wrote: > > > This patch series fix detection and identifying trackstick > > > on machines with ALPS devices.

[for-next][PATCH 13/18] tracing: Do not check return values of trace_seq_p*() for mmio tracer

From: "Steven Rostedt (Red Hat)" The return values for trace_seq_printf() and friends are going to be removed and they will become void functions. The mmio tracer checked their return and even did so incorrectly. Some of the funtions which returned the values were never checked themselves.

[for-next][PATCH 07/18] tracing: Add trace_seq_has_overflowed() and trace_handle_return()

From: "Steven Rostedt (Red Hat)" Adding a trace_seq_has_overflowed() which returns true if the trace_seq had too much written into it allows us to simplify the code. Instead of checking the return value of every call to trace_seq_printf() and friends, they can all be called normally, and at the

[for-next][PATCH 05/18] RAS/tracing: Use trace_seq_buffer_ptr() helper instead of open coded

From: "Steven Rostedt (Red Hat)" Use the helper function trace_seq_buffer_ptr() to get the current location of the next buffer write of a trace_seq object, instead of open coding it. This facilitates the conversion of trace_seq to use seq_buf. Tested-by: Jiri Kosina Acked-by: Jiri Kosina

[for-next][PATCH 12/18] kprobes/tracing: Use trace_seq_has_overflowed() for overflow checks

From: "Steven Rostedt (Red Hat)" Instead of checking the return value of trace_seq_printf() and friends for overflowing of the buffer, use the trace_seq_has_overflowed() helper function. This cleans up the code quite a bit and also takes us a step closer to changing the return values of

[for-next][PATCH 15/18] tracing/uprobes: Do not use return values of trace_seq_printf()

From: "Steven Rostedt (Red Hat)" The functions trace_seq_printf() and friends will soon no longer have return values. Using trace_seq_has_overflowed() and trace_handle_return() should be used instead. Link: http://lkml.kernel.org/r/20141114011411.693008...@goodmis.org Link:

[for-next][PATCH 10/18] tracing: Have branch tracer use trace_handle_return() helper function

From: "Steven Rostedt (Red Hat)" The branch tracer should not be checking the trace_seq_printf() return value as that will soon be void. There's a new trace_handle_return() helper function that will return TRACE_TYPE_PARTIAL_LINE if the trace_seq overflowed and TRACE_TYPE_HANDLED otherwise.

[for-next][PATCH 11/18] tracing: Have function_graph use trace_seq_has_overflowed()

From: "Steven Rostedt (Red Hat)" Instead of doing individual checks all over the place that makes the code very messy. Just check trace_seq_has_overflowed() at the end or in strategic places. This makes the code much cleaner and also helps with getting closer to removing the return values of

[for-next][PATCH 18/18] tracing: Fix return value of ftrace_raw_output_prep()

From: "Steven Rostedt (Red Hat)" If the trace_seq of ftrace_raw_output_prep() is full this function returns TRACE_TYPE_PARTIAL_LINE, otherwise it returns zero. The problem is that TRACE_TYPE_PARTIAL_LINE happens to be zero! The thing is, the caller of ftrace_raw_output_prep() expects a success

[for-next][PATCH 17/18] tracing: Remove return values of most trace_seq_*() functions

From: "Steven Rostedt (Red Hat)" The trace_seq_printf() and friends are used to store strings into a buffer that can be passed around from function to function. If the trace_seq buffer fills up, it will not print any more. The return values were somewhat inconsistant and using

[for-next][PATCH 04/18] x86/kvm/tracing: Use helper function trace_seq_buffer_ptr()

From: "Steven Rostedt (Red Hat)" To allow for the restructiong of the trace_seq code, we need users of it to use the helper functions instead of accessing the internals of the trace_seq structure itself. Link: http://lkml.kernel.org/r/20141104160221.585025...@goodmis.org Tested-by: Jiri Kosina

[for-next][PATCH 00/18] tracing: Fixes and trace-seq updates

git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git for-next Head SHA1: 8e2e095cbecad21078332cd83ae7e61ecfe12c59 Steven Rostedt (Red Hat) (18): tracing: Fix race of function probes counting ftrace/x86: Add frames pointers to trampoline as necessary

[for-next][PATCH 14/18] tracing/probes: Do not use return value of trace_seq_printf()

From: "Steven Rostedt (Red Hat)" The functions trace_seq_printf() and friends will soon not have a return value and will only be a void function. Use trace_seq_has_overflowed() instead to know if the trace_seq operations succeeded or not. Link:

[for-next][PATCH 16/18] tracing: Do not use return values of trace_seq_printf() in syscall tracing

From: "Steven Rostedt (Red Hat)" The functions trace_seq_printf() and friends will not be returning values soon and will be void functions. To know if they succeeded or not, the functions trace_seq_has_overflowed() and trace_handle_return() should be used instead. Reviewed-by: Petr Mladek

Re: [PATCH v3 3/3] sched, x86: Check that we're on the right stack in schedule and __might_sleep

On Wed, Nov 19, 2014 at 3:04 PM, Andy Lutomirski wrote: > > Does that include nmi? I'm a bit afraid of touching that code. NMI is kind of special, since it's really not supposed to touch 'current' or anything like that, and that's how we do preempt-count (and that's where irq-count is) right

[PATCH 03/15] dt: binding: add binding for tz1090-pll clock

Add simple device tree binding for TZ1090 PLL clock. It takes a couple of registers, and has a single reference clock source. Signed-off-by: James Hogan Cc: Mike Turquette Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland Cc: Ian Campbell Cc: Kumar Gala Cc: linux-me...@vger.kernel.org Cc:

[PATCH 00/15] tz1090: add clock components

This patchset adds common clock framework support for the TZ1090 SoC. Patches 1 and 2 are generic and switch clk-divider to use masks internally instead of shifts and width. Patch 1 came from Mike's divider DT bindings patchset from a while back. This is required by the TZ1090 divider binding

[PATCH 04/15] clk: tz1090: add PLL clock driver

Add a driver for the main PLLs in the TZ1090 SoC, the system PLL and the ADC PLL. The system PLL is used to derive the core Meta clock, the DDR clock, and the system clock. The ADC PLL can be used for various purposes, but is usually used for the pixel clock. The PLL is a True Circuits PLL, but

[PATCH 01/15] clk: divider: replace bitfield width with mask

From: Mike Turquette The forthcoming Device Tree binding for the divider clock type will use a bitfield mask instead of bitfield width, which is what the current basic divider implementation uses. This patch replaces the u8 width in struct clk_divider with a u32 mask. The divider code is

[PATCH 02/15] clk: divider: expose new clk_register_divider_mask

Expose a new function clk_register_divider_mask to set up a mask based divider. This will be used by the upcoming TZ1090 divider driver whose DT binding takes a mask rather than a shift and width. Signed-off-by: James Hogan Cc: Mike Turquette --- drivers/clk/clk-divider.c| 25

[PATCH 07/15] dt: binding: add binding for TZ1090 mux bank

Add DT binding for a bank of clock muxes in the TZ1090 SoC. There are several such registers which contain only bits controlling clock muxes. The bit-mask property determines the mask of bits of the register which control muxes. The number of output clocks is equal to the number of set bits in

[PATCH 05/15] dt: binding: add binding for TZ1090 gate bank

Add DT binding for a bank of clock gates in the TZ1090 SoC. There are several such registers which contain only bits controlling clock gates. The bit-mask property determines the mask of bits of the register which control gates. The number of input (and output) clocks is equal to the number of

[PATCH 10/15] clk: tz1090: add deleter clock driver

Add driver for TZ1090 clock deleter, which deletes up to 1023 out of every 1024 clock pulses. Two of these exist, one for the Meta core and the other for the system clock. Signed-off-by: James Hogan Cc: Mike Turquette Cc: linux-me...@vger.kernel.org --- drivers/clk/tz1090/Makefile

[PATCH 11/15] dt: binding: add binding for TZ1090 PDC clock

The TZ1090 PDC (PowerDown Controller) clock should be at 32.768KHz, and is generated either directly from the XTAL3 clock or by dividing the XTAL1 clock. Both the divide and the mux are in a single register which also contains GPIO output data, and may need to be used by other non-Linux cores and

[PATCH 12/15] clk: tz1090: add PDC clock driver

The TZ1090 PDC (PowerDown Controller) clock should be at 32.768KHz, and is generated either directly from the XTAL3 clock or by dividing the XTAL1 clock. Both the divide and the mux are in a single register which also contains GPIO output data, and may need to be used by other non-Linux cores and

[PATCH 09/15] dt: binding: add binding for TZ1090 clock deleter

Add DT binding for the clock deleters in the TZ1090 SoC, which delete up to 1023 out of every 1024 clock pulses of the input clock. Signed-off-by: James Hogan Cc: Mike Turquette Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland Cc: Ian Campbell Cc: Kumar Gala Cc: linux-me...@vger.kernel.org

[PATCH 15/15] metag: tz1090: add TZ1090 clocks to device tree

Enable the common clock framework for the TZ1090 SoC, add a tz1090_clk device tree file describing the clocks, and connect the Meta core clock so that the rate of the Meta timer can be determined. Most of the clock tree is described apart from some AFE clocks which aren't usually of much interest

[PATCH 14/15] clk: tz1090: add divider clock driver

Add driver for TZ1090 clock divider, which divides an input clock by an integer. Two policy decisions are made depending on the MMIO address of the divider: - The UART clock divider sets CLK_SET_RATE_PARENT so that clock changes can propagate up to the CLK_UART_SW mux which allows more

[PATCH 13/15] dt: binding: add binding for TZ1090 divider clock

Add binding for TZ1090 divider clock. This supports a subset of the functionality of the generic divider, and by being specific to the TZ1090 SoC it allows policy decisions to be made from the driver. Signed-off-by: James Hogan Cc: Mike Turquette Cc: Rob Herring Cc: Pawel Moll Cc: Mark

[PATCH 06/15] clk: tz1090: add gate bank clock driver

Add a clock driver for banks of clock gates in the TZ1090 SoC. A single 32 bit register controls up to 32 separate clock gates. The driver instantiates separate generic clock gates. The clock operations are wrapped in order to acquire and release the Meta global exclusive lock (__global_lock2) to

[PATCH 08/15] clk: tz1090: add mux bank clock driver

Add a clock driver for banks of clock muxes in the TZ1090 SoC. A single 32 bit register controls up to 32 separate clock muxes. The driver instantiates separate generic clock muxes. The clock operations are wrapped in order to acquire and release the Meta global exclusive lock (__global_lock2) to

Re: [PATCH] Repeated fork() causes SLAB to grow without bound

On Wed, Nov 19, 2014 at 8:58 AM, Konstantin Khlebnikov wrote: > On Wed, Nov 19, 2014 at 7:09 PM, Vlastimil Babka wrote: >> Also from reading http://lwn.net/Articles/383162/ I understand that >> correctness >> also depends on the hierarchy and I wonder if there's a danger of >> reintroducing >>

RE: [PATCH v2 1/2] Tools: hv: vssdaemon: report freeze errors

> -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Monday, November 10, 2014 8:37 AM > To: KY Srinivasan; Haiyang Zhang; Greg Kroah-Hartman > Cc: de...@linuxdriverproject.org; linux-kernel@vger.kernel.org; Dexuan Cui > Subject: [PATCH v2 1/2] Tools: hv:

Re: frequent lockups in 3.18rc4

On Wed, Nov 19, 2014 at 03:07:17PM -0800, Andy Lutomirski wrote: > On Wed, Nov 19, 2014 at 3:00 PM, Frederic Weisbecker > wrote: > > Note that's non-sleeping faults. So probably most places are fine except > > a few of them that really don't want exception to mess up some state. I > > can

[PATCH 2/2] drm/msm: Add the eDP connector in msm drm driver

Modified the hard-coded hdmi connector/encoder implementations in msm drm driver to support both edp and hdmi. Signed-off-by: Hai Li --- drivers/gpu/drm/msm/mdp/mdp5/mdp5_encoder.c | 38 +-- drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c | 47 -

[PATCH 1/2] drm/msm: Initial add eDP support in msm drm driver

This change adds a new eDP connector in msm drm driver. With this change, eDP panel can work with msm platform under drm framework. Signed-off-by: Hai Li --- drivers/gpu/drm/msm/Makefile|6 + drivers/gpu/drm/msm/edp/edp.c | 211 drivers/gpu/drm/msm/edp/edp.h

Re: frequent lockups in 3.18rc4

On Wed, 19 Nov 2014, Frederic Weisbecker wrote: > On Wed, Nov 19, 2014 at 10:56:26PM +0100, Thomas Gleixner wrote: > > On Wed, 19 Nov 2014, Frederic Weisbecker wrote: > > > I got a report lately involving context tracking. Not sure if it's > > > the same here but the issue was that context

Re: 3.18-rc regression: drm/nouveau: use shared fences for readable objects

On 19.11.2014 09:10, Maarten Lankhorst wrote: ... On the EDITED patch from fixed-fences-for-bisect, can you do the following: In nouveau/nv84_fence.c function nv84_fence_context_new, remove fctx->base.sequence = nv84_fence_read(chan); and add back nouveau_bo_wr32(priv->bo, chan->chid * 16/4,

Re: frequent lockups in 3.18rc4

On Wed, Nov 19, 2014 at 3:00 PM, Frederic Weisbecker wrote: > On Wed, Nov 19, 2014 at 11:03:48AM -0800, Andy Lutomirski wrote: >> On Wed, Nov 19, 2014 at 11:02 AM, Frederic Weisbecker >> wrote: >> > On Wed, Nov 19, 2014 at 09:40:26AM -0800, Linus Torvalds wrote: >> >> On Wed, Nov 19, 2014 at

Re: frequent lockups in 3.18rc4

On Wed, Nov 19, 2014 at 02:59:01PM -0800, Andy Lutomirski wrote: > On Wed, Nov 19, 2014 at 2:56 PM, Frederic Weisbecker > wrote: > > On Wed, Nov 19, 2014 at 10:56:26PM +0100, Thomas Gleixner wrote: > >> On Wed, 19 Nov 2014, Frederic Weisbecker wrote: > >> > I got a report lately involving

Re: [PATCH v4 1/1] misc: st32fwu: Add stm32 upgrade protocol handling

Karol Wrona schrieb am 08.11.2014 14:29: > Adds stm32 bootloader protocol handling. > > SPI transfers are done using DMA safe buffer which is allocated once per > spi upgrade life cycle. Now it supports only SPI bus but it looks that UART > or I2C are quite similar and it can be used as start

Re: [PATCH v3 3/3] sched, x86: Check that we're on the right stack in schedule and __might_sleep

On Wed, Nov 19, 2014 at 11:44 AM, Linus Torvalds wrote: > On Wed, Nov 19, 2014 at 11:29 AM, Andi Kleen wrote: >> >> The exception handlers which use the IST stacks don't necessarily >> set irq count. Maybe they should. > > Hmm. I think they should. Since they clearly must not schedule, as > they

LED-LENSER flashlight

Hi Many thanks for your valuable time to read my letter. This is Hellen from JRS Technology Co.,Ltd. We do LED LENSER flashlight Wholesale business. Many models are available with competitive price. For more information, please contact us in any time it will be our honor to serve you well and

Re: [PATCH v4] clocksource: arch_timer: Allow the device tree to specify uninitialized timer registers

Daniel, On Wed, Oct 8, 2014 at 12:33 AM, Sonny Rao wrote: > From: Doug Anderson > > Some 32-bit (ARMv7) systems are architected like this: > > * The firmware doesn't know and doesn't care about hypervisor mode and > we don't want to add the complexity of hypervisor there. > > * The firmware

RE: [PATCH v2 2/2] Tools: hv: vssdaemon: skip all filesystems mounted readonly

> -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Monday, November 10, 2014 8:37 AM > To: KY Srinivasan; Haiyang Zhang; Greg Kroah-Hartman > Cc: de...@linuxdriverproject.org; linux-kernel@vger.kernel.org; Dexuan Cui > Subject: [PATCH v2 2/2] Tools: hv:

Re: frequent lockups in 3.18rc4

On Wed, Nov 19, 2014 at 11:03:48AM -0800, Andy Lutomirski wrote: > On Wed, Nov 19, 2014 at 11:02 AM, Frederic Weisbecker > wrote: > > On Wed, Nov 19, 2014 at 09:40:26AM -0800, Linus Torvalds wrote: > >> On Wed, Nov 19, 2014 at 9:22 AM, Linus Torvalds > >> wrote: > >> > > >> > So it hasn't

RE: [PATCH] hv: hv_fcopy: drop the obsolete message on transfer failure

> -Original Message- > From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On > Behalf Of Dexuan Cui > Sent: Tuesday, November 11, 2014 9:03 PM > To: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org; driverdev- > de...@linuxdriverproject.org; o...@aepfle.de;

Re: frequent lockups in 3.18rc4

On Wed, Nov 19, 2014 at 2:56 PM, Frederic Weisbecker wrote: > On Wed, Nov 19, 2014 at 10:56:26PM +0100, Thomas Gleixner wrote: >> On Wed, 19 Nov 2014, Frederic Weisbecker wrote: >> > I got a report lately involving context tracking. Not sure if it's >> > the same here but the issue was that

Re: frequent lockups in 3.18rc4

On Wed, Nov 19, 2014 at 10:58:14PM +0100, Borislav Petkov wrote: > On Wed, Nov 19, 2014 at 04:47:43PM -0500, Dave Jones wrote: > > This box is usually pretty solid, but it's been in service as a 24/7 > > fuzzing box for over a year now, so it's not outside the realm of > > possibility that

Re: frequent lockups in 3.18rc4

On Wed, Nov 19, 2014 at 10:56:26PM +0100, Thomas Gleixner wrote: > On Wed, 19 Nov 2014, Frederic Weisbecker wrote: > > I got a report lately involving context tracking. Not sure if it's > > the same here but the issue was that context tracking uses per cpu data > > and per cpu allocation use

Re: [PATCH 5/5] mm, compaction: more focused lru and pcplists draining

On 11/14/2014 08:05 AM, Joonsoo Kim wrote: >> What about this scenario, with pageblock order: >> >> - record cc->migrate_pfn pointing to pageblock X >> - isolate_migratepages() skips the pageblock due to e.g. skip bit, >> or the pageblock being a THP already... >> - loop to pageblock X+1,

[PATCH v2 1/2] pinctrl: rockchip: Handle wakeup pins

The rockchip pinctrl driver was using irq_gc_set_wake() as its implementation of irq_set_wake() but was totally ignoring everything that irq_gc_set_wake() did (which is to upkeep gc->wake_active). Let's fix that by setting gc->wake_active as GPIO_INTEN at suspend time and restoring GPIO_INTEN at

[PATCH v2 0/2] Pinctrl fixes for rockchip

These two patches fix some pinctrl issues on rockchip. The first fixes a real issue where interrupts were being left on in suspend/resume and waking the system up when they shouldn't. The second fixes purely theoretical problems but seems clean. I've tested these patches more extensively on a

[PATCH v2 2/2] pinctrl: rockchip: Fix enable/disable/mask/unmask

The Rockchip pinctrl driver was only implementing the "mask" and "unmask" operations though the hardware actually has two distinct things: enable/disable and mask/unmask. It was implementing the "mask" operations as a hardware enable/disable and always leaving all interrupts unmasked. I believe

Re: [PATCH 3/3] hugetlb: hugetlb_register_all_nodes(): add __init marker

On Wed, 12 Nov 2014, Luiz Capitulino wrote: > This function is only called during initialization. > > Signed-off-by: Luiz Capitulino Acked-by: David Rientjes And hugetlb_unregister_all_nodes() could be __exit. The !CONFIG_NUMA versions would be better off inline. -- To unsubscribe from

[PATCH 3.17 010/141] vxlan: Do not reuse sockets for a different address family

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Leitner [ Upstream commit 19ca9fc1445b76b60d34148f7ff837b055f5dcf3 ] Currently, we only match against local port number in order to reuse socket. But if this new vxlan wants an IPv6

Re: [PATCH 2/3] hugetlb: alloc_bootmem_huge_page(): use IS_ALIGNED()

On Wed, 12 Nov 2014, Luiz Capitulino wrote: > No reason to duplicate the code of an existing macro. > > Signed-off-by: Luiz Capitulino Acked-by: David Rientjes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More

[PATCH 3.17 011/141] net: ppp: Dont call bpf_prog_create() in ppp_lock

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai [ Upstream commit 5748eb8f8e989a9da1ac7c96dc73d68cbdedf7df ] In ppp_ioctl(), bpf_prog_create() is called inside ppp_lock, which eventually calls vmalloc() and hits BUG_ON() in

[PATCH 3.17 012/141] net: sctp: fix NULL pointer dereference in af->from_addr_param on malformed packet

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit e40607cbe270a9e8360907cb1e62ddf0736e4864 ] An SCTP server doing ASCONF will panic on malformed INIT ping-of-death in the form of: INIT[PARAM:

[PATCH 3.17 016/141] netlink: Properly unbind in error conditions.

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Hiroaki SHIMODA [ Upstream commit 6251edd932ce3faadbfe27b0a0fe79780e0972e9 ] Even if netlink_kernel_cfg::unbind is implemented the unbind() method is not called, because cfg->unbind is

[PATCH 3.17 015/141] net: ptp: fix time stamp matching logic for VLAN packets.

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Richard Cochran [ Upstream commit cca04b2854ecfb7cd1b8ee84ab38bc99af59f526 ] Commit ae5c6c6d "ptp: Classify ptp over ip over vlan packets" changed the code in two drivers that matches time

[PATCH 3.17 013/141] net: sctp: fix memory leak in auth key management

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit 4184b2a79a7612a9272ce20d639934584a1f3786 ] A very minimal and simple user space application allocating an SCTP socket, setting SCTP_AUTH_KEY setsockopt(2) on

[PATCH 3.17 014/141] ipv6: fix IPV6_PKTINFO with v4 mapped

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 5337b5b75cd9bd3624a6820e3c2a084d2480061c ] Use IS_ENABLED(CONFIG_IPV6), to enable this code if IPv6 is a module. Signed-off-by: Eric Dumazet Fixes:

[PATCH 3.17 001/141] x86/build: Add arch/x86/purgatory/ make generated files to gitignore

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan commit 4ea48a01bb1a99f4185b77cd90cf962730336cc4 upstream. The following generated files are missing from gitignore and show up in git status after x86_64 build. Add them to

Re: [PATCH 1/3] hugetlb: fix hugepages= entry in kernel-parameters.txt

On Wed, 12 Nov 2014, Luiz Capitulino wrote: > The hugepages= entry in kernel-parameters.txt states that > 1GB pages can only be allocated at boot time and not > freed afterwards. This is not true since commit > 944d9fec8d7aee, at least for x86_64. > > Instead of adding arch-specifc observations

[PATCH 3.17 022/141] sunvdc: dont call VD_OP_GET_VTOC

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Dwight Engen [ Upstream commit 85b0c6e62c48bb9179fd5b3e954f362fb346cbd5 ] The VD_OP_GET_VTOC operation will succeed only if the vdisk backend has a VTOC label, otherwise it will fail. In

[PATCH 3.17 024/141] sparc64: Do irq_{enter,exit}() around generic_smp_call_function*().

3.17-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit ab5c780913bca0a5763ca05dd5c2cb5cb08ccb26 ] Otherwise rcu_irq_{enter,exit}() do not happen and we get dumps like: [ 188.275021]

[PATCH 3.17 021/141] vio: fix reuse of vio_dring slot

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Dwight Engen [ Upstream commit d0aedcd4f14a22e23b313f42b7e6e6ebfc0fbc31 ] vio_dring_avail() will allow use of every dring entry, but when the last entry is allocated then dr->prod == dr->cons

[PATCH 3.17 023/141] sparc64: Fix crashes in schizo_pcierr_intr_other().

3.17-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 7da89a2a3776442a57e918ca0b8678d1b16a7072 ] Meelis Roos reports crashes during bootup on a V480 that look like this: [ 61.300577]

[PATCH 3.17 018/141] sunvdc: add cdrom and v1.1 protocol support

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Allen Pais [ Upstream commit 9bce21828d54a95143f1b74619705c2dd8e88b92 ] Interpret the media type from v1.1 protocol to support CDROM/DVD. For v1.0 protocol, a disk's size continues to be

[PATCH 3.17 025/141] sparc32: Implement xchg and atomic_xchg using ATOMIC_HASH locks

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Larsson [ Upstream commit 1a17fdc4f4ed06b63fac1937470378a5441a663a ] Atomicity between xchg and cmpxchg cannot be guaranteed when xchg is implemented with a swap and cmpxchg is

Re: [PATCH] iio: gyro: itg3200: add suspend/resume support.

NeilBrown schrieb am 08.11.2014 01:18: > > > Unless we put the device to sleep when not it use, it wastes > 6mA. > > If the device is asleep on probe, the 'id' register > sometimes mis-reads - so reset first. If the device responds > at all a command sent to the address, it is almost certainly

[PATCH 3.17 026/141] zram: avoid kunmap_atomic() of a NULL pointer

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Weijie Yang commit c406515239376fc93a30d5d03192182160cbd3fb upstream. zram could kunmap_atomic() a NULL pointer in a rare situation: a zram page becomes a full-zeroed page after a partial

[PATCH 3.17 027/141] mm/page_alloc: fix incorrect isolation behavior by rechecking migratetype

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Joonsoo Kim commit ad53f92eb416d81e469fa8ea57153e59455e7175 upstream. Before describing bugs itself, I first explain definition of freepage. 1. pages on buddy list are counted as freepage.

[PATCH 3.17 028/141] mm/page_alloc: add freepage on isolate pageblock to correct buddy list

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Joonsoo Kim commit 51bb1a4093cc68bc16b282548d9cee6104be0ef1 upstream. In free_pcppages_bulk(), we use cached migratetype of freepage to determine type of buddy list where freepage will be

[PATCH 2/3] f2fs: submit bio for node blocks in the reclaim path

If a node page is request to be written during the reclaiming path, we should submit the bio to avoid pending to recliam it. Signed-off-by: Jaegeuk Kim --- fs/f2fs/node.c | 4 1 file changed, 4 insertions(+) diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c index 478ce1e..dbf49cc 100644 ---

[PATCH 3/3] f2fs: write SSA pages under memory pressure

Under memory pressure, we don't need to skip SSA page writes. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c index 838e8ed..20a917b 100644 --- a/fs/f2fs/checkpoint.c +++

[PATCH 3.17 019/141] sunvdc: compute vdisk geometry from capacity

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Allen Pais [ Upstream commit de5b73f08468b4fc5e2f6d1505f650262622f78b ] The LDom diskserver doesn't return reliable geometry data. In addition, the types for all fields in the vio_disk_geom

[PATCH 3.17 030/141] mm/page_alloc: restrict max order of merging on isolated pageblock

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Joonsoo Kim commit 3c605096d3158216ba9326a16266f6ba128c2c8d upstream. Current pageblock isolation logic could isolate each pageblock individually. This causes freepage accounting problem if

[PATCH 3.17 029/141] mm/page_alloc: move freepage counting logic to __free_one_page()

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Joonsoo Kim commit 8f82b55dd558a74fc33d69a1f2c2605d0cd2c908 upstream. All the caller of __free_one_page() has similar freepage counting logic, so we can move it to __free_one_page(). This

[PATCH 1/3] f2fs: call flush_dcache_page when the page was updated

Whenever f2fs updates mapped pages, it needs to call flush_dcache_page. Signed-off-by: Jaegeuk Kim --- fs/f2fs/dir.c| 7 ++- fs/f2fs/inline.c | 4 +++- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c index 5a49995..312fbfc 100644 ---

[PATCH 3.17 003/141] inet: frags: remove the WARN_ON from inet_evict_bucket

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Aleksandrov [ Upstream commit d70127e8a942364de8dd140fe73893efda363293 ] The WARN_ON in inet_evict_bucket can be triggered by a valid case: inet_frag_kill and inet_evict_bucket can be

Re: [f2fs-dev] [PATCH 2/2] f2fs: put the inode page when error was occurred

On Tue, Nov 18, 2014 at 01:30:46PM +0800, Chao Yu wrote: > Hi Jaegeuk, > > > -Original Message- > > From: Jaegeuk Kim [mailto:jaeg...@kernel.org] > > Sent: Tuesday, November 18, 2014 9:58 AM > > To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org; > >

[PATCH 3.17 031/141] crypto: caam - fix missing dma unmap on error path

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Cristian Stoica commit 738459e3f88538f2ece263424dafe5d91799e46b upstream. If dma mapping for dma_addr_out fails, the descriptor memory is freed but the previous dma mapping for dma_addr_in

[PATCH 3.17 020/141] sunvdc: limit each sg segment to a page

3.17-stable review patch. If anyone has any objections, please let me know. -- From: Dwight Engen [ Upstream commit 5eed69ffd248c9f68f56c710caf07db134aef28b ] ldc_map_sg() could fail its check that the number of pages referred to by the sg scatterlist was <= the number of

Re: [PATCH 1/1] netfilter: Deletion of unnecessary checks before two function calls

Hello, On Tue, 18 Nov 2014, SF Markus Elfring wrote: > From: Markus Elfring > Date: Tue, 18 Nov 2014 20:37:05 +0100 > > The functions free_percpu() and module_put() test whether their argument > is NULL and then return immediately. Thus the test around the call is > not needed. > >

<    1   2   3   4   5   6   7   8   9   10   >