Michal Hocko wrote:
> +/*
> + * Checks whether the given task is dying or exiting and likely to
> + * release its address space. This means that all threads and processes
> + * sharing the same mm have to be killed or exiting.
> + */
> +static inline bool task_will_free_mem(struct task_struct
Provide the cmpwait() primitive, which will 'spin' wait for a variable
to change and use it to implement smp_cond_load_acquire().
This primitive can be implemented with hardware assist on some
platforms (ARM64, x86).
Suggested-by: Will Deacon
Signed-off-by: Peter Zijlstra
This new form allows using hardware assisted waiting.
Requested-by: Will Deacon
Suggested-by: Linus Torvalds
Signed-off-by: Peter Zijlstra (Intel)
---
include/linux/compiler.h | 25 +++--
Code is more readable when using kmem_cache_zalloc instead of
kmem_cache_alloc/memset.
Signed-off-by: Salah Triki
---
fs/ubifs/super.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c
index 7034995..f509200 100644
Michal Hocko wrote:
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 5bb2f7698ad7..0e33e912f7e4 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -820,6 +820,13 @@ void oom_kill_process(struct oom_control *oc, struct
> task_struct *p,
> task_unlock(victim);
>
> /*
> +
On 26/05/16 12:42, Dmitry Osipenko wrote:
> On 26.05.2016 11:42, Jon Hunter wrote:
>>
>> On 25/05/16 19:51, Dmitry Osipenko wrote:
>>> On 25.05.2016 18:09, Jon Hunter wrote:
>>
>> ...
>>
If you are able to reproduce this on v3.18, then it would be good if
you
could trace the CCF
Introduce smp_acquire__after_ctrl_dep(), this construct is not
uncommen, but the lack of this barrier is.
Signed-off-by: Peter Zijlstra (Intel)
---
include/linux/compiler.h | 15 ++-
ipc/sem.c| 14 ++
2 files changed, 12
This patch updates/fixes all spin_unlock_wait() implementations.
The update is in semantics; where it previously was only a control
dependency, we now upgrade to a full load-acquire to match the
store-release from the spin_unlock() we waited on. This ensures that
when spin_unlock_wait() returns,
Am 2016-05-26 um 02:29 schrieb Dmitry Torokhov:
> Hi Martin,
>
> On Wed, May 25, 2016 at 09:44:34AM +0200, Martin Kepplinger wrote:
>> This adds a driver for the Pegasus Notetaker Pen. When connected,
>> this uses the Pen as an input tablet.
>>
>> This device was sold in various different
On Thu 26-05-16 23:11:47, Tetsuo Handa wrote:
[...]
> > + if (mm) {
> > + rcu_read_lock();
> > + for_each_process(p) {
> > + bool vfork;
> > +
> > + /*
> > +* skip over vforked tasks because they are mostly
> > +
Hi Greg,
On Thu, May 05, 2016 at 02:07:24PM -0500, Reza Arbab wrote:
$ echo online > /sys/devices/system/memory/memory0/state
-bash: echo: write error: Invalid argument
Fix the return value of store_mem_state() so this doesn't happen.
I can't find where this might have been committed. Am I
On 26/05/16 15:20, Catalin Marinas wrote:
> While writing the above, I realised the current ILP32 patches still miss
> on converting pointers passed from user space (unless I got myself
> confused in macros). The new __SC_WRAP() and COMPAT_SYSCALL_WRAPx()
> macros take care of zero or sign
On Wed, May 25, 2016 at 02:28:21PM -0700, David Miller wrote:
> From: Arnd Bergmann
> Date: Wed, 25 May 2016 23:01:06 +0200
>
> > On Wednesday, May 25, 2016 1:50:39 PM CEST David Miller wrote:
> >> From: Arnd Bergmann
> >> Date: Wed, 25 May 2016 22:47:33 +0200
> >>
On Thu, 2016-05-26 at 16:59 +0300, Vladimir Davydov wrote:
> On Thu, May 26, 2016 at 04:04:55PM +0900, Minchan Kim wrote:
> > On Wed, May 25, 2016 at 01:30:11PM +0300, Vladimir Davydov wrote:
> > > On Tue, May 24, 2016 at 01:04:33PM -0700, Eric Dumazet wrote:
> > > > On Tue, 2016-05-24 at 19:13
With the modified semantics of spin_unlock_wait() a number of
explicit barriers can be removed. And update the comment for the
do_exit() usecase, as that was somewhat stale/obscure.
Signed-off-by: Peter Zijlstra (Intel)
---
ipc/sem.c |1 -
kernel/exit.c |
This version rewrites all spin_unlock_wait() implementations to provide the
acquire order against the spin_unlock() release we wait on, ensuring we can
fully observe the critical section we waited on.
It pulls in the smp_cond_acquire() rewrite because it introduces a lot more
users of it. All
nf_conntrack_lock{,_all}() is borken as it misses a bunch of memory
barriers to order the whole global vs local locks scheme.
Even x86 (and other TSO archs) are affected.
Signed-off-by: Peter Zijlstra (Intel)
---
net/netfilter/nf_conntrack_core.c | 18 +-
Am 26.05.2016 um 16:28 schrieb Salah Triki:
> Code is more readable when using kmem_cache_zalloc instead of
> kmem_cache_alloc/memset.
I don't fully agree. You also have ignored my other comment on this patch.
Please note that the path you are patching is a hot path.
Thanks,
//richard
Michal Hocko wrote:
> +/*
> + * Checks whether the given task is dying or exiting and likely to
> + * release its address space. This means that all threads and processes
> + * sharing the same mm have to be killed or exiting.
> + */
> +static inline bool task_will_free_mem(struct task_struct
On 05/26/2016 12:23 AM, Ming Lin wrote:
From: Ming Lin
blk_mq_init_queue() calls blk_mq_init_allocated_queue(), but q->mq_ops
was not cleared when blk_mq_init_allocated_queue() fails.
Then blk_cleanup_queue() calls blk_mq_free_queue() which will crash because:
-
On 26.05.2016 17:32, Jon Hunter wrote:
On 26/05/16 12:42, Dmitry Osipenko wrote:
On 26.05.2016 11:42, Jon Hunter wrote:
On 25/05/16 19:51, Dmitry Osipenko wrote:
On 25.05.2016 18:09, Jon Hunter wrote:
...
If you are able to reproduce this on v3.18, then it would be good if
you
could
On Thu 26-05-16 23:30:06, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> > index 5bb2f7698ad7..0e33e912f7e4 100644
> > --- a/mm/oom_kill.c
> > +++ b/mm/oom_kill.c
> > @@ -820,6 +820,13 @@ void oom_kill_process(struct oom_control *oc, struct
> >
On Thu 26-05-16 23:41:54, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > +/*
> > + * Checks whether the given task is dying or exiting and likely to
> > + * release its address space. This means that all threads and processes
> > + * sharing the same mm have to be killed or exiting.
> > + */
> >
On 05/12/2016 10:49 AM, James Morse wrote:
Hi David, Pratyush
On 27/04/16 19:53, David Long wrote:
From: Pratyush Anand
Entry symbols are not kprobe safe. So blacklist them for kprobing.
Signed-off-by: Pratyush Anand
diff --git
On Fri 27-05-16 00:25:23, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > On Thu 26-05-16 23:30:06, Tetsuo Handa wrote:
> > > Michal Hocko wrote:
> > > > diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> > > > index 5bb2f7698ad7..0e33e912f7e4 100644
> > > > --- a/mm/oom_kill.c
> > > > +++ b/mm/oom_kill.c
From: Thierry Reding
Override the compatible string of the first USB controller to enable
device mode.
Signed-off-by: Thierry Reding
---
arch/arm/boot/dts/tegra20-trimslice.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git
Michal Hocko wrote:
> On Fri 27-05-16 00:25:23, Tetsuo Handa wrote:
> > I think that remembering whether this mm might be shared between
> > multiple thread groups at clone() time (i.e. whether
> > clone(CLONE_VM without CLONE_SIGHAND) was ever requested on this mm)
> > is safe (given that that
Hi Neil,
On 26/05/16 10:38, Neil Armstrong wrote:
Since the current SCPI implementation, based on [0]:
- is (at leat) JUNO specific
Agreed.
- does not specify a strong "standard"
Not exactly, it's extensible. Refer section 3.2.2. Get SCP capability
Extended Set Enabled bit.
- does not
On 26.05.2016 18:27, Jon Hunter wrote:
On 26/05/16 15:57, Dmitry Osipenko wrote:
On 26.05.2016 17:32, Jon Hunter wrote:
On 26/05/16 12:42, Dmitry Osipenko wrote:
On 26.05.2016 11:42, Jon Hunter wrote:
On 25/05/16 19:51, Dmitry Osipenko wrote:
On 25.05.2016 18:09, Jon Hunter wrote:
...
On Thu, May 26, 2016 at 02:41:19PM +0530, Rajneesh Bhardwaj wrote:
> This patch adds the Power Management Controller driver as a PCI driver
> for Intel Core SoC architecture.
>
> This driver can utilize debugging capabilities and supported features
> as exposed by the Power Management Controller.
Hi Ravikumar
Some sanity comments, just good to have.
> +#ifdef CONFIG_I2C_SLAVE
> +static int omap_i2c_slave_irq(struct omap_i2c_dev *omap)
> +{
> + u16 stat_raw;
> + u16 stat;
> + u16 bits;
> + u8 value;
> +
> + stat_raw = omap_i2c_read_reg(omap,
Hello, Ingo,
This series changes a number of event tracepoints to their _rcuidle() form
to allow use from idle without lockdep-RCU complaints, a straightforward
modification that has been successfully applied many times. These splats
were found in testing by Guenter Roeck and Tony Lindgren, who
The driver's init function is called at subsys init call level but the
dependencies provided by the driver are looked up by drivers that have
probe deferral support, so manual ordering of init calls isn't needed.
Suggested-by: Krzysztof Kozlowski
Signed-off-by: Javier
Hello,
This series is similar to [0] and allows the max14577 PMIC MFD driver to
be built as a module. Currently the Kconfig symbol for the driver is a
boolean but there isn't really a reason for this restriction.
Chanwoo Choi tried to test the original post but found a build issue [1].
The fix
The driver's Kconfig symbol is a boolean but nothing prevents the driver
to be built as a module instead of built-in. It is true that most system
integrators will choose the latter but the config should not restrict it.
Suggested-by: Krzysztof Kozlowski
Signed-off-by:
From: Andrew Bresticker
Move the UTMIPLL initialization code form clk-tegra.c files into
clk-pll.c. UTMIPLL was being configured and set in HW control right
after registration. However, when the clock init_table is processed and
child clks of PLLU are enabled, it will call
On Thu, May 26, 2016 at 06:47:29PM +0200, Peter Zijlstra wrote:
> On Wed, May 25, 2016 at 04:18:08PM +0800, Pan Xinhui wrote:
> > cmpxchg_release is light-wight than cmpxchg, we can gain a better
> > performace then. On some arch like ppc, barrier impact the performace
> > too much.
> >
> >
On 26/05/16 15:57, Dmitry Osipenko wrote:
> On 26.05.2016 17:32, Jon Hunter wrote:
>>
>> On 26/05/16 12:42, Dmitry Osipenko wrote:
>>> On 26.05.2016 11:42, Jon Hunter wrote:
On 25/05/16 19:51, Dmitry Osipenko wrote:
> On 25.05.2016 18:09, Jon Hunter wrote:
...
>>
On Thu, May 26, 2016 at 11:38:29AM +0100, Mark Rutland wrote:
> On Wed, May 25, 2016 at 07:04:08PM -0400, Rich Felker wrote:
> > On Wed, May 25, 2016 at 11:22:15AM +0100, Mark Rutland wrote:
> > > > +Optional properties:
> > > > +
> > > > +- enable-method: Required only for SMP systems. If
On Thu, May 26, 2016 at 09:43:04AM -0500, Reza Arbab wrote:
> Hi Greg,
>
> On Thu, May 05, 2016 at 02:07:24PM -0500, Reza Arbab wrote:
> > $ echo online > /sys/devices/system/memory/memory0/state
> > -bash: echo: write error: Invalid argument
> >
> > Fix the return value of store_mem_state() so
From: Thierry Reding
All Tegra SoC generations from Tegra20 through Tegra124 have a ChipIdea
USB device controller. This set of patches adds very rudimentary support
for it to the existing ChipIdea driver and enables them on the set of
boards that I could easily test on.
I'm
From: Thierry Reding
Override the compatible string of the first USB controller to enable
device mode.
Signed-off-by: Thierry Reding
---
arch/arm/boot/dts/tegra30-beaver.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git
On 05/17/2016 04:58 AM, Huang Shijie wrote:
On Wed, Apr 27, 2016 at 02:53:00PM -0400, David Long wrote:
+
+/*
+ * Interrupts need to be disabled before single-step mode is set, and not
+ * reenabled until after single-step mode ends.
+ * Without disabling interrupt on local CPU, there is a
From: Thierry Reding
Override the compatible string of the first USB controller to enable
device mode.
Signed-off-by: Thierry Reding
---
arch/arm/boot/dts/tegra124-jetson-tk1.dts | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff
Hello,
On 5/25/2016 3:31 AM, rajeev kumar wrote:
On Fri, May 20, 2016 at 3:14 AM, Austin Christ wrote:
From: Naveen Kaje
I2C QUP driver relies on SMBus emulation support from the framework.
To handle SMBus block reads, the driver should check
[[PATCH 0/4] sh: fix up modular use in non-modular code] On 22/04/2016 (Fri
14:07) Paul Gortmaker wrote:
> For anyone new to the underlying goal of this cleanup, we are trying to
> make kernel code consistent with the Makefiles/Kconfigs that control them.
Ping -- wondering if there are any
On Wed, May 25, 2016 at 04:18:03PM +0800, Pan Xinhui wrote:
> I do several tests on pseries IBM,8408-E8E with 32cpus, 64GB memory.
> benchmark test results are below.
> _testspinlcok__pv-qspinlcok_
> | compiling takes|22m | 22m
From: Michal Hocko
oom_reaper relies on the mmap_sem for read to do its job. Many places
which might block readers have been converted to use down_write_killable
and that has reduced chances of the contention a lot. Some paths where
the mmap_sem is held for write can take other
Hi Linus,
The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99:
Linux 4.6-rc7 (2016-05-08 14:38:32 -0700)
are available in the git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.7-1
for you to fetch changes up to
On Thursday 26 May 2016 17:39:57 Thorsten Leemhuis wrote:
> > I need to know if this patch fixes problem on Dell Studio XPS 8000
> > and Dell Studio XPS 8100 machines, so we can revert git commits:
> > 6220f4ebd7b4 ("hwmon: (dell-smm) Blacklist Dell Studio XPS 8000")
> > a4b45b25f18d ("hwmon:
On Thu, May 26, 2016 at 03:50:01PM +0100, Szabolcs Nagy wrote:
> On 26/05/16 15:20, Catalin Marinas wrote:
> > While writing the above, I realised the current ILP32 patches still miss
> > on converting pointers passed from user space (unless I got myself
> > confused in macros). The new
On Thu, May 26, 2016 at 05:23:30PM +0200, Thierry Reding wrote:
> From: Thierry Reding
>
> Starting with commit 0b52297f2288 ("reset: Add support for shared reset
> controls") there is a reference count for reset control assertions. The
> goal is to allow resets to be shared
On Tue, 2016-05-24 at 20:37 +0300, Andy Shevchenko wrote:
> Below results doesn't show DMA case (by the way, how did you disable
> DMA
> in 3.8.7?) for stock kernel.
The stock kernel on SPI flash for my early Gen1 is a non-DMA 8250
driver, so nothing needs to be done to that, it's basically just
On Tue, 2016-05-24 at 21:08 +0300, Andy Shevchenko wrote:
> On Tue, 2016-05-24 at 20:37 +0300, Andy Shevchenko wrote:
> > On Thu, 2016-05-19 at 02:18 +0100, Bryan O'Donoghue wrote:
> > > On Thu, 2016-05-12 at 18:06 +0300, Andy Shevchenko wrote:
> > > > On Fri, 2016-05-06 at 18:17 +0300, Andy
On Thu, May 26, 2016 at 12:45:57PM -0400, Paul Gortmaker wrote:
> [[PATCH 0/4] sh: fix up modular use in non-modular code] On 22/04/2016 (Fri
> 14:07) Paul Gortmaker wrote:
>
> > For anyone new to the underlying goal of this cleanup, we are trying to
> > make kernel code consistent with the
On Tue, May 24, 2016 at 12:50:28PM +0300, Laurent Pinchart wrote:
Hey Laurent,
> On Saturday 14 May 2016 13:27:31 Vinod Koul wrote:
> > On Fri, Apr 22, 2016 at 01:50:04AM +, Kuninori Morimoto wrote:
> > > From: Kuninori Morimoto
> > >
> > > Current
Lo!
Pali Rohár wrote on 21.05.2016 16:46:
> […] Thorsten […] can you test this patch if it fixes your freeze problem at
> boottime and when using "sensors" program?
FWIW, I never saw either of those problems. I only saw the third issue
that was mentioned: the CPU fan speed is going up and down
On Thu, May 26, 2016 at 09:26:06AM -0700, Paul E. McKenney wrote:
> Hello, Ingo,
>
> This series changes a number of event tracepoints to their _rcuidle() form
> to allow use from idle without lockdep-RCU complaints, a straightforward
> modification that has been successfully applied many times.
>>> Boris Ostrovsky 05/25/16 9:17 PM >>>
>On 05/05/2016 12:58 AM, Lv Zheng wrote:
>> +static u8
>> +acpi_hw_get_access_bit_width(struct acpi_generic_address *reg, u8
>> max_bit_width)
>> +{
>> +u64 address;
>> +
>> +if (!reg->access_width) {
>> +/*
>>
On Thu, 2016-05-26 at 09:22 -0700, Ganapatrao Kulkarni wrote:
> On Wed, May 25, 2016 at 7:43 PM, Zhen Lei wrote:
> > numa_init(of_numa_init) may returned error because of numa configuration
> > error. So "No NUMA configuration found" is inaccurate. In fact, specific
>
On Thu, May 26, 2016 at 07:46:11PM +0800, Leizhen (ThunderTown) wrote:
> On 2016/5/25 18:50, Catalin Marinas wrote:
> > What happens is that __sync_icache_dcache() only takes care of the first
> > time a page is mapped in user space and flushes the caches, marking it
> > as "clean"
On Wed, May 25, 2016 at 04:18:08PM +0800, Pan Xinhui wrote:
> cmpxchg_release is light-wight than cmpxchg, we can gain a better
> performace then. On some arch like ppc, barrier impact the performace
> too much.
>
> Suggested-by: Boqun Feng
> Signed-off-by: Pan Xinhui
From: Thierry Reding
Starting with commit 0b52297f2288 ("reset: Add support for shared reset
controls") there is a reference count for reset control assertions. The
goal is to allow resets to be shared by multiple devices and an assert
will take effect only when all instances
On Thu, May 26, 2016 at 08:34:12AM -0700, Greg Kroah-Hartman wrote:
> On Thu, May 26, 2016 at 09:43:04AM -0500, Reza Arbab wrote:
> > Hi Greg,
> >
> > On Thu, May 05, 2016 at 02:07:24PM -0500, Reza Arbab wrote:
> > > $ echo online > /sys/devices/system/memory/memory0/state
> > > -bash: echo:
On Wed, May 25, 2016 at 7:43 PM, Zhen Lei wrote:
> numa_init(of_numa_init) may returned error because of numa configuration
> error. So "No NUMA configuration found" is inaccurate. In fact, specific
> configuration error information can be immediately printed by the
>
On Wed, May 25, 2016 at 06:27:07PM +0100, Russell King - ARM Linux wrote:
> On Wed, May 25, 2016 at 04:22:55PM +0100, Catalin Marinas wrote:
> > That's when we realised that the CoW problem no longer exists for
> > non-aliasing VIPT caches. However, the I-cache counterpart 6060e8df5178
> > has not
On Wed, May 25, 2016 at 04:18:03PM +0800, Pan Xinhui wrote:
> _testspinlcok__pv-qspinlcok_
> |futex hash | 556370 ops | 629634 ops |
> |futex lock-pi| 362 ops | 367 ops |
>
> scheduler test:
> Test
On 05/26/2016 12:26 PM, Jan Beulich wrote:
Boris Ostrovsky 05/25/16 9:17 PM >>>
>> On 05/05/2016 12:58 AM, Lv Zheng wrote:
>>> +static u8
>>> +acpi_hw_get_access_bit_width(struct acpi_generic_address *reg, u8
>>> max_bit_width)
>>> +{
>>> +u64 address;
>>> +
Michal Hocko wrote:
> On Thu 26-05-16 23:30:06, Tetsuo Handa wrote:
> > Michal Hocko wrote:
> > > diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> > > index 5bb2f7698ad7..0e33e912f7e4 100644
> > > --- a/mm/oom_kill.c
> > > +++ b/mm/oom_kill.c
> > > @@ -820,6 +820,13 @@ void oom_kill_process(struct
From: Thierry Reding
There are three EHCI controllers on Tegra SoCs, each with its own reset
line. However, the first controller contains a set of UTMI configuration
registers that are shared with its siblings. These registers will only
be reset as part of the first
From: Thierry Reding
Override the compatible string of the first USB controller to enable
device mode.
Signed-off-by: Thierry Reding
---
arch/arm/boot/dts/tegra114-dalmore.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git
From: Thierry Reding
All of these Tegra SoC generations have a ChipIdea UDC IP block that can
be used for device mode communication with a host. Implement rudimentary
support that doesn't allow switching between host and device modes.
Signed-off-by: Thierry Reding
Add the Microsoft _DSM command set to the white list of NVDIMM command sets.
This command set is documented at
https://msdn.microsoft.com/library/windows/hardware/mt604741.
Signed-off-by: Stuart Hayes
---
drivers/acpi/nfit.c| 9 ++---
drivers/acpi/nfit.h
On Wed, May 25, 2016 at 11:13 PM, Dave Chinner wrote:
>
> Just yell if this is not OK and I'll drop those branches for this
> merge and resend the pull request
i'm ok with the late branches, it's not like xfs has been a problem spot.
However:
> are available in the git
On Tue, May 24, 2016 at 09:20:27AM +, He Kuang wrote:
> Use thread specific unwind ops to unwind cross-platform callchains.
>
> Currently, unwind methods is suitable for local unwind, this patch
> changes the fixed methods to thread/map related. Each time a map is
> inserted, we find the
blkdev_issue_zeroout try discard/writesame first, if they fail, zeroout
fallback to regular write. The problem is discard/writesame doesn't
return error for -EOPNOTSUPP, then zeroout can't do fallback and leave
disk data not changed. zeroout should have guaranteed zero-fill
behavior.
BTW, I saw
From: Dave Hansen
The 32-bit siginfo is a different binary format than the 64-bit
one. So, when running 32-bit binaries on 64-bit kernels, we have
to convert the kernel's 64-bit version to a 32-bit version that
userspace can grok.
We've added a few features to
Philipp Zabel writes:
> Am Mittwoch, den 25.05.2016, 19:42 -0700 schrieb Kevin Hilman:
>> Neil Armstrong writes:
>>
>> > This patch adds the platform driver for the Amlogic Meson SoC Reset
>> > Controller.
>> >
>> > The Meson8b and GXBB SoCs are
On Tue, May 24, 2016 at 02:52:19PM -0600, Ross Zwisler wrote:
> Hi Linus, please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
> tags/dax-locking-for-4.7
>
> ... to receive filesystem DAX locking changes for v4.7.
>
> These current version of these changes have
Currently, the trace_printk code chooses which static buffer to use based
on what type of atomic context (NMI, IRQ, etc) it's in. Simplify the
code and make it more robust: simply count the nesting depth and choose
a buffer based on the current nesting depth.
The new code will only drop an event
Hello,
Nice catch. I added more details to the changelog, tagged it for
-stable and applied it to cgroup/for-4.7-fixes.
Thanks!
-- 8< --
>From b00c52dae6d9ee8d0f2407118ef6544ae5524781 Mon Sep 17 00:00:00 2001
From: Wenwei Tao
Date: Fri, 13 May 2016 22:59:20 +0800
The current patch to correct this problem is here:
https://lkml.org/lkml/2016/5/24/679
Since v7 of the ACPI/NUMA patches are likely going to be added to
linux-next as soon as the current merge window ends, further
simplifications of the informational prints should probably be rebased
on top
Hi Linus,
Please pull the following Ceph updates from
git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus
This changeset has a few main parts:
* Ilya has finished a huge refactoring effort to sync up the client-side
logic in libceph with the user-space client code,
We have not been updating the x86 compat_siginfo when updating the
generic one. These patches fix the issue, and then add a bunch
of build-time checks to try to avoid this happening again in the
future (suggested by Ingo).
From: Dave Hansen
I've had this code for a while, but never submitted it upstream. Now
that Skylake hardware is out in the wild, folks can actually run this
for real. It tests the following:
1. The MPX hardware is enabled by the kernel and doing what it
From: Dave Hansen
There were at least 3 features added to the __SI_FAULT area of the
siginfo struct that did not make it to the compat siginfo:
1. The si_addr_lsb used in SIGBUS's sent for machine checks
2. The upper/lower bounds for MPX SIGSEGV
On Fri, May 27, 2016 at 12:15:17AM +0530, Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_workqueue().
>
> kfd_process_wq is used for delay destruction. A work item embedded in
> kfd_process gets queued to kfd_process_wq and when it executes it
> destroys and frees the
Linus,
The following changes since commit 9842df62004f366b9fed2423e24df10542ee0dc5:
KVM: MTRR: remove MSR 0x2f8 (2016-05-18 18:04:32 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to
On Wed, May 25, 2016 at 6:09 PM, Joonsoo Kim wrote:
> On Tue, May 24, 2016 at 02:15:22PM -0700, Thomas Garnier wrote:
>> This commit reorganizes the previous SLAB freelist randomization to
>> prepare for the SLUB implementation. It moves functions that will be
>> shared to
On Mon, May 16, 2016 at 07:41:28PM +0300, Pantelis Antoniou wrote:
> The changeset helpers are easier to use, use them instead of
> using the static property.
>
> Signed-off-by: Pantelis Antoniou
If you think this is worthwhile, then it's fine with me :)
Hi Boris,
On Thu, May 26, 2016 at 1:04 AM, Boris Brezillon
wrote:
> I think the MTD partition -> nvmem connection could benefit to non-OTP
> partitions too.
Yeah, I thought about that, too. Would you use the _read, and _write
callbacks in that case?
> So,
On Wed, May 25, 2016 at 10:39:21AM +, Wang Nan wrote:
SNIP
>
> +static int string_set_value(struct bt_ctf_field *field, const char *string)
> +{
> + char *buffer;
> + size_t len = strlen(string), i, p;
> + int err;
> +
> + buffer = zalloc(len * 4 + 2);
> + if (!buffer)
On Thu, May 26, 2016 at 11:18 AM, Sage Weil wrote:
>
> Please pull the following Ceph updates from
Why was that branch rebased yesterday?
What has been in next, if anything?
And if something has been in next, why was _that_ not sent to me?
Pulled and then immediately
On Wed, May 25, 2016 at 04:51:21PM -0700, Linus Torvalds wrote:
> On Wed, May 25, 2016 at 10:56 AM, Josh Poimboeuf wrote:
> >
> > I used to have a STACKTOOL_IGNORE_INSN macro that would tell the tool to
> > skip warnings for specific instructions in inline asm:
> >
> > Here's
On Thu, 26 May 2016, Linus Torvalds wrote:
> On Thu, May 26, 2016 at 11:18 AM, Sage Weil wrote:
> >
> > Please pull the following Ceph updates from
>
> Why was that branch rebased yesterday?
>
> What has been in next, if anything?
>
> And if something has been in next, why
> RK3399 has a PCIe controller which can be used as Root Complex.
> This driver supports a PCIe controller as Root Complex mode.
1 general feedback I have is that there are a lot of magic constants.
I'd appreciate if they could be converted into macros for easy readability.
>
> Signed-off-by:
Your patch makes code a little clearer, so I don't mind merging it,
but the two values are the same so this patch should have no effect.
On Thu, May 26, 2016 at 4:52 AM, Jerome Marchand wrote:
> In sess_auth_rawntlmssp_authenticate(), the ntlmssp blob is allocated
>
On Wed, May 25, 2016 at 3:25 PM, Kees Cook wrote:
> On Tue, May 24, 2016 at 2:15 PM, Thomas Garnier wrote:
>> Implements Freelist randomization for the SLUB allocator. It was
>> previous implemented for the SLAB allocator. Both use the same
>>
alloc_workqueue replaces deprecated create_workqueue().
kfd_process_wq is used for delay destruction. A work item embedded in
kfd_process gets queued to kfd_process_wq and when it executes it
destroys and frees the containing kfd_process and thus itself.
This requires a dedicated workqueue
On Thu, May 26, 2016 at 11:43 AM, Josh Poimboeuf wrote:
>
> That's fine with me, it is indeed a rare case. We can always add the
> per-instruction macro later if needed. Here's a patch.
Ingo, I can take this directly, unless you have other things pending
that you want to
1 - 100 of 892 matches
Mail list logo