David Miller wrote:
> I'll pull, but this is not how I want you to operate.
Anyway, thanks for pulling it.
David
On Tue, 2016-05-17 at 14:01 +0200, Christophe Leroy wrote:
> On processors like the 8xx, the machine check exception can also
> happen directly on the load/store instruction itself, so that case
> needs to be handled as well
>
> Signed-off-by: Christophe Leroy
> ---
What machine checks are happe
On Thu, Jul 7, 2016 at 8:26 PM, Pranay Srivastava wrote:
> On Thu, Jun 30, 2016 at 4:32 PM, Pranay Kr. Srivastava
> wrote:
>> From: "Pranay Kr. Srivastava"
>>
>> This patch
>> 1) uses spin_lock instead of irq version.
>>
>> 2) removes the goto statement in case a socket
>>is already assigned
On Fri, Jul 08, 2016 at 10:05:18PM -0500, Eric W. Biederman wrote:
> James Bottomley writes:
>
> > On Fri, 2016-07-08 at 18:52 -0500, Eric W. Biederman wrote:
> >> James Bottomley writes:
> >>
> >> > On July 8, 2016 1:38:19 PM PDT, Andrew Vagin
> >> > wrote:
> >>
> >> > > What do you think ab
Alexandre Belloni writes:
> rtc-v3020.h belongs to include/linux/platform_data/
>
> Signed-off-by: Alexandre Belloni
> ---
> Cc: Daniel Mack
> Cc: Haojian Zhuang
> Cc: Robert Jarzmik
> Cc: linux-arm-ker...@lists.infradead.org
> arch/arm/mach-pxa/cm-x270.c | 2 +-
> arch/arm
On Fri, Jul 08, 2016 at 07:40:48PM -0700, Joe Perches wrote:
> This change isn't described in the commit message and there
> doesn't seem to be a need to change this.
How do *you* know? Did *you* actually sit down and build a kernel with
your proposed change before sending a reply?
I'm pretty sur
The workqueue "work_thread" is involved in updating parameters for
transfers. It has a single work item(&sd->work) and hence
doesn't require ordering. Also, it is not being used on a memory
reclaim path. Hence, the singlethreaded workqueue has been replaced with
the use of system_wq.
System workqu
Should update "cfs_rq->throttled_clock_task" other than pcfs_rq's.
Signed-off-by: Xunlei Pang
---
kernel/sched/fair.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 4088eed..039de34 100644
--- a/kernel/sched/fair.c
+++ b/kernel
* Rik van Riel wrote:
> On Fri, 2016-07-08 at 19:22 -0700, Laura Abbott wrote:
> >
> > Even with the SLUB fixup I'm still seeing this blow up on my arm64
> > system. This is a
> > Fedora rawhide kernel + the patches
> >
> > [0.666700] usercopy: kernel memory exposure attempt detected from
Hi Vinod,
> On Fri, Jul 01, 2016 at 05:07:05PM +0530, Kedareswara rao Appana wrote:
> > Device-tree binding documentation for Xilinx zynqmp dma engine used in
> > Zynq UltraScale+ MPSoC.
>
> And I missed the cleanup part, so both applied now
Thanks for applying the patches will send patch for t
On Sat, Jul 9, 2016 at 10:54 AM, Xunlei Pang wrote:
> Should update "cfs_rq->throttled_clock_task" other than pcfs_rq's.
>
> Signed-off-by: Xunlei Pang
Ack
> ---
> kernel/sched/fair.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fa
On Fri, Jul 08, 2016 at 09:34:57PM +0200, Ingo Molnar wrote:
> The cache-id identifies a hardware cache of the system within a given
> cache-index category of caches. The (cache-index,cache-id) pair is
I'd say something like:
"... within a given cache index in a set of cache indices. The
On 09/07/2016 at 09:45:52 +0200, Robert Jarzmik wrote :
> Alexandre Belloni writes:
>
> > rtc-v3020.h belongs to include/linux/platform_data/
> >
> > Signed-off-by: Alexandre Belloni
> > ---
> > Cc: Daniel Mack
> > Cc: Haojian Zhuang
> > Cc: Robert Jarzmik
> > Cc: linux-arm-ker...@lists.infra
On 9 July 2016 at 04:22, Laura Abbott wrote:
> On 07/06/2016 03:25 PM, Kees Cook wrote:
>>
>> Hi,
>>
>> This is a start of the mainline port of PAX_USERCOPY[1]. After I started
>> writing tests (now in lkdtm in -next) for Casey's earlier port[2], I
>> kept tweaking things further and further until
Hello,
I'm an Outreachy intern working under Rik van Riel. My project is about
latency tracing during memory allocation. The idea is to use
tracepoints, both existing and new, to derive higher level information
on memory allocation and identify where time was spent.
This patchset which
1, adds a
Hi Vinod,
Thanks for the review...
> > +
> > + chan->is_dmacoherent = of_property_read_bool(node, "dma-
> coherent");
> > + zdev->chan = chan;
> > + tasklet_init(&chan->tasklet, zynqmp_dma_do_tasklet, (ulong)chan);
>
> where is this killed?
This is killed in the zynqmp_dma_chan_r
* Dave Hansen wrote:
> On 07/08/2016 12:18 AM, Ingo Molnar wrote:
>
> > So the question is, what is user-space going to do? Do any glibc patches
> > exist? How are the user-space library side APIs going to look like?
>
> My goal at the moment is to get folks enabled to the point that they can
Hello,
I was playing with quite simple bridged setup on different boards with
very recent kernels (4.6.3 as of this writing) and found one interesting
behavior that I cannot yet understand and googling din't help here as well.
My setup is pretty simple:
- --
From: David Tolnay
Date: Sat, 9 Jul 2016 00:20:00 -0700
Subject: [PATCH] perf tool: add Rust demangling
Rust demangling is another step after bfd demangling. Add a diagnosis to
identify mangled Rust symbols based on the hash that the Rust mangler
appends as the last path component, as well as oth
In cyclic DMA mode need to link the tail bd segment
with the head bd segment to process bd's in cyclic.
Current driver is doing this only for tx channel
needs to update the same for rx channel case also.
This patch fixes the same.
Signed-off-by: Kedareswara rao Appana
---
drivers/dma/xilinx/xi
Struct shrinker does not have a field to uniquely identify the shrinkers
it represents. It would be helpful to have a new field to hold names of
shrinkers. This information would be useful while analyzing their
behavior using tracepoints.
---
include/linux/shrinker.h | 1 +
1 file changed, 1 inse
greetings linux
http://profedu.online/escape.php?race=1q5xsgykw917
My Best
Chris Rankin
This patch makes changes to have all instances of struct shrinker update
the newly added name field. This name could then be passed to
tracepoints, which can help identify which shrinker was invoked.
---
arch/x86/kvm/mmu.c | 1 +
drivers/gpu/drm/i915/i915_gem_shrin
Currently, the mm_shrink_slab_start and mm_shrink_slab_end
tracepoints tell us how much time was spent in a shrinker, the number of
objects scanned, etc. But there is no information about the identity of
the shrinker. This patch enables the trace output to display names of
shrinkers.
---
include/
On Fri, Jul 08, 2016 at 05:08:08PM -0400, Steven Rostedt wrote:
> On Fri, 8 Jul 2016 22:24:55 +0200
> Torsten Duwe wrote:
>
> > On Fri, Jul 08, 2016 at 11:57:10AM -0400, Steven Rostedt wrote:
> > > On Fri, 8 Jul 2016 10:48:24 -0500
> > > Josh Poimboeuf wrote:
> > > >
> > > > Here, with -fprol
This reverts commit 8792f7772f4f40ffc68bad5f28311205584b734d.
The s3c6410 rtc don't use rtc_src property, that property is designed
for Exynos5250 and Exynos5440. The problem reported in the commit
I mentioned should be fixed in the other way.
Signed-off-by: Randy Li
---
drivers/rtc/rtc-s3c.c |
The device data for samsung,exynos3250-rtc and samsung,s3c6410-rtc
are just have a difference, but keeping using the same device data
would cause the platform using the other IP core not work.
Signed-off-by: Randy Li
---
drivers/rtc/rtc-s3c.c | 14 +-
1 file changed, 13 insertions(+)
The 8792f7772f4f40ffc68bad5f28311205584b734d would just make those
platform using rtc core from exynos3250 work but have a huge
effect on those platforms using the rtc core from s3c6410.
These patches would fix this problem.
Randy Li (3):
Revert "drivers/rtc/rtc-s3c.c: add .needs_src_clk to s3c
Those platforms are reported to use the same rtc IP core
as exynos3250's.
Signed-off-by: Randy Li
---
arch/arm/boot/dts/exynos3250.dtsi | 2 +-
arch/arm/boot/dts/exynos5.dtsi| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/exynos3250.dtsi
b/arch/arm/b
The I2C core removes the manufacturer prefix from the compatible field
so it reports to user-space the uevent i2c:rave-wdt, but this doesn't
match with the i2c_device_id (i2c:ziirave-wdt) array so the module is not
autoloaded. Correct the I2C device id to match with the reported uevent
and fix the
Hi,
Here a small patch series to add support for firmware update to the ziirave
watchdog driver. The first patch is a fix found during the development of this
new feature, the second patch is the one that adds support for firmware update.
Best regards,
Enric Balletbo i Serra (2):
watchdog: zii
This patch adds and entry to the sysfs to start firmware upload process
on the specified device with the requested firmware.
The uploading of the firmware needs only to happen once per firmware
upgrade, as the firmware is stored in persistent storage. If the
firmware upload or the firmware verific
-shrinkers-and-have-tracepoints-display-them/20160709-170759
config: i386-defconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
I
On Fri, Jul 08, 2016 at 05:43:02PM +0200, Thierry Reding wrote:
> Mark, do you want me to provide a stable branch with the PWM regulator
> patches and resolve that conflict in your tree? Or would you rather take
> the whole set based on a stable branch from the PWM tree? Or maybe yet
> another pos
On 07/09/2016 02:20 AM, Alexei Starovoitov wrote:
On Sat, Jul 09, 2016 at 01:31:40AM +0200, Eric Dumazet wrote:
On Fri, 2016-07-08 at 17:52 +0200, Michal Kubecek wrote:
If socket filter truncates an udp packet below the length of UDP header
in udpv6_queue_rcv_skb() or udp_queue_rcv_skb(), it wi
On Friday 08 July 2016 23:37:54 Dmitry Torokhov wrote:
> On Thu, Jul 07, 2016 at 01:41:01PM +0200, Pali Rohár wrote:
> > On Tuesday 21 June 2016 13:27:30 Pali Rohár wrote:
> > > On Monday 20 June 2016 17:31:13 Dmitry Torokhov wrote:
> > > > Hi Pali,
> > > >
> > > > On Mon, Jun 06, 2016 at 01:23:56
On 08/07/16 23:29, Shuah Khan wrote:
> If s5p_mfc_release() runs after s5p_mfc_remove(), the former will access
> invalid s5p_mfc_dev pointer saved in the s5p_mfc_ctx and runs into kernel
> paging request errors.
>
> Clear ctx dev pointer in s5p_mfc_remove() and change s5p_mfc_release() to
> avoid
On July 9, 2016 4:26:28 PM GMT+09:00, Andrew Vagin wrote:
>On Fri, Jul 08, 2016 at 10:05:18PM -0500, Eric W. Biederman wrote:
>> James Bottomley writes:
>>
>> > On Fri, 2016-07-08 at 18:52 -0500, Eric W. Biederman wrote:
>> >> James Bottomley writes:
>> >>
>> >> > On July 8, 2016 1:38:19 PM PD
On July 9, 2016 4:26:28 PM GMT+09:00, Andrew Vagin wrote:
>On Fri, Jul 08, 2016 at 10:05:18PM -0500, Eric W. Biederman wrote:
>> James Bottomley writes:
>>
>> > On Fri, 2016-07-08 at 18:52 -0500, Eric W. Biederman wrote:
>> >> James Bottomley writes:
>> >>
>> >> > On July 8, 2016 1:38:19 PM PD
On Sat, Jul 09, 2016 at 11:48:49AM +0200, Daniel Borkmann wrote:
> On 07/09/2016 02:20 AM, Alexei Starovoitov wrote:
> >On Sat, Jul 09, 2016 at 01:31:40AM +0200, Eric Dumazet wrote:
> >>On Fri, 2016-07-08 at 17:52 +0200, Michal Kubecek wrote:
> >>>If socket filter truncates an udp packet below the
On Sat, Jul 9, 2016 at 4:37 AM, Alexey Brodkin
wrote:
> Hello,
>
> I was playing with quite simple bridged setup on different boards with
> very recent kernels (4.6.3 as of this writing) and found one interesting
> behavior that I cannot yet understand and googling din't help here as well.
>
> My
Commit-ID: 0b95364f977c180e1f336e00273fda5d3eca54b4
Gitweb: http://git.kernel.org/tip/0b95364f977c180e1f336e00273fda5d3eca54b4
Author: Paolo Bonzini
AuthorDate: Mon, 20 Jun 2016 16:58:29 +0200
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 10:44:01 +0200
x86/entry: Avoid interrupt
Commit-ID: eec4b1227db153ca16f8f5f285d01fefdce05438
Gitweb: http://git.kernel.org/tip/eec4b1227db153ca16f8f5f285d01fefdce05438
Author: Paolo Bonzini
AuthorDate: Mon, 20 Jun 2016 16:58:30 +0200
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 10:44:02 +0200
x86/entry: Inline enter_fro
* Brian Gerst wrote:
> On Mon, Jun 20, 2016 at 11:14 AM, Borislav Petkov wrote:
> > On Mon, Jun 20, 2016 at 11:01:02AM -0400, Brian Gerst wrote:
> >> The idea was to put the uncommon case (kernel thread) out of line for
> >> performance reasons.
> >
> > A comment saying so wouldn't hurt...
>
>
* Kees Cook wrote:
> Before, the stack protector flag was sanity checked before .config had
> been reprocessed. This meant the build couldn't be aborted early, and
> only a warning could be emitted followed later by the compiler blowing
> up with an unknown flag. This has caused a lot of confusi
On 08/07/16 23:43, Markus Mayer wrote:
> Add a collection of generic functions to convert strings to lowercase
> or uppercase.
>
> Changing the case of a string (with or without copying it first) seems
> to be a recurring requirement in the kernel that is currently being
> solved by several duplic
Hi Aaron,
On Sat, 2016-07-09 at 07:47 -0400, Aaron Z wrote:
> On Sat, Jul 9, 2016 at 4:37 AM, Alexey Brodkin
> wrote:
> >
> > Hello,
> >
> > I was playing with quite simple bridged setup on different boards with
> > very recent kernels (4.6.3 as of this writing) and found one interesting
> > be
Am 2016-07-08 um 23:08 schrieb Dmitry Torokhov:
> On Tue, Jun 28, 2016 at 06:17:13PM +0200, Martin Kepplinger wrote:
>> Am 2016-06-23 um 19:18 schrieb Dmitry Torokhov:
>>> Hi Martin,
>>>
>>> On Tue, Jun 14, 2016 at 01:20:15PM +0200, Martin Kepplinger wrote:
static int pegasus_reset_resume(str
On Sat, Jul 9, 2016 at 6:43 AM, Michal Kubecek wrote:
> On Sat, Jul 09, 2016 at 11:48:49AM +0200, Daniel Borkmann wrote:
>> On 07/09/2016 02:20 AM, Alexei Starovoitov wrote:
>> >On Sat, Jul 09, 2016 at 01:31:40AM +0200, Eric Dumazet wrote:
>> >>On Fri, 2016-07-08 at 17:52 +0200, Michal Kubecek wro
tip-bot for Paolo Bonzini wrote:
>Commit-ID: eec4b1227db153ca16f8f5f285d01fefdce05438
>Gitweb:
>http://git.kernel.org/tip/eec4b1227db153ca16f8f5f285d01fefdce05438
>Author: Paolo Bonzini
>AuthorDate: Mon, 20 Jun 2016 16:58:30 +0200
>Committer: Ingo Molnar
>CommitDate: Sat, 9 Jul 2016 1
Hi,
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.7-rc6 next-20160708]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Insu-Yun/qxl-correctly-handling-failed-allocation/201
Intel MID platforms are using explicitly defined regulators.
Let regulator core know that we do not have any additional
regulators left. This lets it substitute unprovided regulators with
dummy ones.
Without this change when CONFIG_REGULATOR=y the USB driver fails on getting
"vbus" regulator and
Hi dmitry:
>> >> modify raydium touch firmware update rule.
>>
>> >Why? You need to explain why you are proposing a change (but as I
>> >mentioned I see no reason for using custom file names for firmware. Have
>> >userspace adjust name as needed by the driver.
>>
>> >Thanks.
>>
>> Just want to
Hi dmitry:
> >>input_mt_report_slot_state(ts->input, MT_TOOL_FINGER, state);
> >>
> >> - if (!state)
> >> - continue;
> >> -
> >> - input_report_abs(ts->input, ABS_MT_POSITION_X,
> >> + if (state == 0x01) {
>
> >Why we need this change? How
Hi Hans,
Thanks for great help.
I believe the issues highlighted by your are rectified by now.
One chunk of your proposed changes seems to be wrong.
Also I have one non-technical change I want to introduce to this driver, see it
in the bottom of this letter ("Also, I decided to document known vi
Hello, Ming.
On Fri, Jul 08, 2016 at 06:35:06PM +0800, Ming Lei wrote:
> I am wondering why REQ_THROTTLED is cleared for the original bio
> even it has been charged and will be issued to driver, and is it allowed
> to throttle and charge the same bio for many times?
So, IIUC, the flag is just to
On 9 July 2016 at 05:04, Luis de Bethencourt wrote:
> On 08/07/16 23:43, Markus Mayer wrote:
>> Add a collection of generic functions to convert strings to lowercase
>> or uppercase.
>>
>> Changing the case of a string (with or without copying it first) seems
>> to be a recurring requirement in th
Thank you for you review, HeiKo
On 07/08/2016 05:35 AM, Heiko Stuebner wrote:
Hi Randy,
Am Donnerstag, 7. Juli 2016, 02:22:57 schrieb Randy Li:
The rk3288 firefly reload is a Rockchip RK3288 based board be found by
core board and main board. The regulators are connected in a different
way to
IS_ERR_VALUE() assumes that its parameter is an unsigned long.
It can not be used to check if an 'unsigned int' reflects an error.
As they pass an 'unsigned int' into a function that takes an
'unsigned long' argument. This happens to work because the type
is sign-extended on 64-bit architectures be
From: Chen Gang
For pure bool function's return value, bool is a little better more or
less than int.
And return boolean result directly, since 'if' statement is also for
boolean checking, and return boolean result, too.
Signed-off-by: Chen Gang
---
include/linux/migrate.h | 4 ++--
mm/compac
On Fri, Jul 08, 2016 at 11:50:02PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2016/7/8 11:19, Jaegeuk Kim wrote:
> > Hi Chao,
> >
> > Could you take a look at this in xfstests/generic/013?
> >
> > [ 502.480850] ==
> > [ 502.480864] [ INFO: po
On Sat, Jul 09, 2016 at 10:28:49AM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2016/6/9 1:24, Jaegeuk Kim wrote:
> > In f2fs, we don't need to keep block plugging for NODE and DATA writes,
> > since
> > we already merged bios as much as possible.
>
> IMO, we can not remove block plug, this is bec
From: Chen Gang
For pure bool function's return value, bool is a little better more or
less than int.
And return boolean result directly. Since 'if' statement is also for
boolean checking, and return boolean result, too.
Signed-off-by: Chen Gang
---
arch/powerpc/include/asm/mman.h | 8 +++
On 07/08/16 09:13, Petr Mladek wrote:
> On Thu 2016-07-07 20:27:13, Topi Miettinen wrote:
>> On 07/07/16 09:16, Petr Mladek wrote:
>>> On Sun 2016-07-03 15:08:07, Topi Miettinen wrote:
The attached patch would make any uses of capabilities generate audit
messages. It works for simple test
-to-avoid-IS_ERR_VALUE-abuses/20160709-235356
config: x86_64-rhel (attached as .config)
compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
In file included from i
On Sat, Jul 9, 2016 at 5:03 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> Before, the stack protector flag was sanity checked before .config had
>> been reprocessed. This meant the build couldn't be aborted early, and
>> only a warning could be emitted followed later by the compiler blowing
On Fri, Jul 8, 2016 at 7:22 PM, Laura Abbott wrote:
> On 07/06/2016 03:25 PM, Kees Cook wrote:
>>
>> Hi,
>>
>> This is a start of the mainline port of PAX_USERCOPY[1]. After I started
>> writing tests (now in lkdtm in -next) for Casey's earlier port[2], I
>> kept tweaking things further and furthe
IS_ERR_VALUE() assumes that its parameter is an unsigned long.
It can not be used to check if an 'unsigned int' reflects an error.
As they pass an 'unsigned int' into a function that takes an
'unsigned long' argument. This happens to work because the type
is sign-extended on 64-bit architectures be
On Sat, Jul 9, 2016 at 1:25 AM, Ard Biesheuvel
wrote:
> On 9 July 2016 at 04:22, Laura Abbott wrote:
>> On 07/06/2016 03:25 PM, Kees Cook wrote:
>>>
>>> Hi,
>>>
>>> This is a start of the mainline port of PAX_USERCOPY[1]. After I started
>>> writing tests (now in lkdtm in -next) for Casey's earli
applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Arvind-Yadav/ErrHandling-Make-IS_ERR_VALUE_U32-as-generic-API-to-avoid-IS_ERR_VALUE-abuses/20160709-235356
config: x86_64-rhel (attached as .config)
compiler: gcc-4.9
On Fri, Jul 8, 2016 at 11:17 PM, wrote:
> Yeah, 'ping' dies with a similar traceback going to rawv6_setsockopt(),
> and 'trinity' dies a horrid death during initialization because it creates
> some sctp sockets to fool around with. The problem in all these cases is that
> setsockopt uses copy_fr
Hi Eric,
thanks for all the infos and help! Both your patches look good and i
have successfully tested them on top of with my vblank timestamping patch.
So for both:
Reviewed-and-tested-by: Mario Kleiner
Will you squash 2/2 into my patch or should i resend my patch with yours
squashed in?
From: Chen Gang
For a pure output parameter:
- When callee fails, the caller should not assume the output parameter
is still valid.
- And callee should not assume the pure output parameter must be
provided by caller -- caller has right to pass NULL when caller does
not care about it.
Hello!
I've been attempting to qualify the Linux 4.5.2 user-space headers for
a toolchain release, and ran into what looks like a missing include
file in include/uapi/linux/errqueue.h. In particular,
https://github.com/torvalds/linux/commit/f24b9be5957b38bb420b838115040dc2031b7d0c
adds the follow
Commit-ID: 9acacc2ac525ef1397af63b15cef7bb77a823c06
Gitweb: http://git.kernel.org/tip/9acacc2ac525ef1397af63b15cef7bb77a823c06
Author: Zhao Lei
AuthorDate: Mon, 20 Jun 2016 17:37:18 +0800
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 13:56:15 +0200
sched/cpuacct: Merge cpuacct_usa
Commit-ID: 8e546bfafb3121ed25c73a0c02311ec58459344a
Gitweb: http://git.kernel.org/tip/8e546bfafb3121ed25c73a0c02311ec58459344a
Author: Zhao Lei
AuthorDate: Mon, 20 Jun 2016 17:37:19 +0800
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 13:56:15 +0200
sched/cpuacct: Use loop to conso
Commit-ID: 277a13e4f0d661678a7084bf97ed96a99c7dac21
Gitweb: http://git.kernel.org/tip/277a13e4f0d661678a7084bf97ed96a99c7dac21
Author: Zhao Lei
AuthorDate: Mon, 20 Jun 2016 17:37:20 +0800
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 13:56:15 +0200
sched/cpuacct: Introduce cpuacct
Commit-ID: 62d855d3e725f4e4b0d2786f7cad3f0660a03a59
Gitweb: http://git.kernel.org/tip/62d855d3e725f4e4b0d2786f7cad3f0660a03a59
Author: Andy Shevchenko
AuthorDate: Sat, 18 Jun 2016 18:51:34 +0300
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 14:02:09 +0200
x86/platform/intel-mid: R
Commit-ID: 8709ed4d4b0eab04561c1ec9e6ea50fd1e3897ff
Gitweb: http://git.kernel.org/tip/8709ed4d4b0eab04561c1ec9e6ea50fd1e3897ff
Author: Dave Hansen
AuthorDate: Fri, 17 Jun 2016 17:15:03 -0700
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 14:06:06 +0200
x86/cpu: Fix duplicated X86_B
On Sat, 2016-07-09 at 09:50 +0200, Borislav Petkov wrote:
> On Fri, Jul 08, 2016 at 07:40:48PM -0700, Joe Perches wrote:
> > This change isn't described in the commit message and there
> > doesn't seem to be a need to change this.
> How do *you* know? Did *you* actually sit down and build a kernel
-to-avoid-IS_ERR_VALUE-abuses/20160709-235356
config: x86_64-randconfig-x007-201628 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
I
Andrew Vagin writes:
> All these thoughts about security make me thinking that kcmp is what we
> should use here. It's maybe something like this:
>
> kcmp(pid1, pid2, KCMP_NS_USERNS, fd1, fd2)
>
> - to check if userns of the fd1 namepsace is equal to the fd2 userns
>
> kcmp(pid1, pid2, KCMP_NS_PA
ebied...@xmission.com (Eric W. Biederman) writes:
> Andrew Vagin writes:
>
>> All these thoughts about security make me thinking that kcmp is what we
>> should use here. It's maybe something like this:
>>
>> kcmp(pid1, pid2, KCMP_NS_USERNS, fd1, fd2)
>>
>> - to check if userns of the fd1 namepsac
When a word length of 1 byte is selected and writing data of length
more than QSPI_WLEN_MAX_BYTES, first MAX_BYTES will be transfered
and remaining will be transfered byte by byte. In that case wlen
field should be cleared before setting.
Signed-off-by: Prahlad V
---
drivers/spi/spi-ti-qspi.c |
On Fri, Jul 08, 2016 at 03:06:07PM -0700, Dmitry Torokhov wrote:
> > Last year we had the invite-only session on the 3rd day and what I heard
> > from some people that was considered better. People had a chance to
> > already solve several things upfront and the invite-only day had less
> > issues
Fixes: a1db74209483 ("module: replace copy_module_from_fd with kernel version")
Signed-off-by: Mickaël Salaün
Cc: Mimi Zohar
Cc: Kees Cook
Cc: Luis R. Rodriguez
Cc: Rusty Russell
Cc: Linus Torvalds
Cc: Greg Kroah-Hartman
---
include/linux/lsm_hooks.h | 1 -
include/linux/security.h | 1 -
On Fri, Jul 08, 2016 at 06:03:38PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160707:
>
> New trees: netfilter and netfilter-next
>
> The drm-msm tree gained a conflict against the arm tree.
>
> The block tree gained conflicts against Linus' and the btrfs-kdave trees.
>
> The
is_prefetch in arch/x86/mm/fault.c can be called on a user address
that's not readable due to PKRU. This could break it. You might need
to add a get_user_exec or similar.
--Andy
On Jul 6, 2016 6:25 PM, "Kees Cook" wrote:
>
> Hi,
>
> This is a start of the mainline port of PAX_USERCOPY[1]. After I started
> writing tests (now in lkdtm in -next) for Casey's earlier port[2], I
> kept tweaking things further and further until I ended up with a whole
> new patch series. To tha
From: Hayes Wang
Date: Thu, 7 Jul 2016 15:09:17 +0800
> Remove the unnacessary code.
Series applied.
From: Arvind Yadav
Date: Fri, 8 Jul 2016 00:07:54 +0530
> -Return type of 'qe_muram_alloc' is 'unsigned long', That Was trying to
> assigned in ucc_fast_tx_virtual_fifo_base_offset and
> ucc_fast_rx_virtual_fifo_base_offset. These variable are 'unsigned int'.
> So before assginment need a proper
From: Jon Mason
Date: Thu, 7 Jul 2016 19:08:52 -0400
> David Miller, Please consider including patches 1-5 in net-next
Done.
From: Colin Ian King
At the current point where ret is being checked for non-zero it has
not changed since it was initialized to zero, hence the check and the
label unref are redundant and can be removed.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/vc4/vc4_drv.c | 3 ---
1 file changed,
Hi Randy,
Am Samstag, 9. Juli 2016, 23:42:28 schrieb ayaka:
> On 07/08/2016 05:35 AM, Heiko Stuebner wrote:
> > Am Donnerstag, 7. Juli 2016, 02:22:57 schrieb Randy Li:
> >> The rk3288 firefly reload is a Rockchip RK3288 based board be found by
> >> core board and main board. The regulators are co
[Re: [PATCH 14/14] PCI: xgene: make it explicitly non-modular] On 07/07/2016
(Thu 15:42) Duc Dang wrote:
> On Thu, Jul 7, 2016 at 3:35 PM, Tanmay Inamdar wrote:
> >
> >
> > On Sat, Jul 2, 2016 at 4:13 PM, Paul Gortmaker
> > wrote:
> >>
> >> The Kconfig currently controlling compilation of this
On 9 Jul 2016 at 14:27, Andy Lutomirski wrote:
> On Jul 6, 2016 6:25 PM, "Kees Cook" wrote:
> >
> > Hi,
> >
> > This is a start of the mainline port of PAX_USERCOPY[1]. After I started
> > writing tests (now in lkdtm in -next) for Casey's earlier port[2], I
> > kept tweaking things further and fu
On Thu, Jul 7, 2016 at 6:37 PM, Gregory CLEMENT
wrote:
> This clock is the parent of all the Armada 3700 clocks. It is a fixed
> rate clock which depends on the gpio configuration read when resetting
> the SoC.
>
> Signed-off-by: Gregory CLEMENT
> ---
> drivers/clk/mvebu/Kconfig| 3
On Tue, Jul 5, 2016 at 5:04 AM, Joseph Lo wrote:
> The Inter-VM communication (IVC) is a communication protocol, which is
> designed for interprocessor communication (IPC) or the communication
> between the hypervisor and the virtual machine with a guest OS on it. So
> it can be translated as inte
Am Samstag, 9. Juli 2016, 11:38:00 schrieb William.wu:
> Dear Heiko & Balbi，
>
> On 2016/7/8 21:29, Felipe Balbi wrote:
> > Hi,
> >
> > Heiko Stuebner writes:
> >> Am Donnerstag, 7. Juli 2016, 10:54:24 schrieb William Wu:
> >>> Add a quirk to configure the core to support the
> >>> UTMI+ PHY wit
I came across the following issue in kernel 3.16 (Ubuntu 14.04) which
was then reproduced in kernels 4.4 LTS:
After a couple of of memcg oom-kills in a cgroup, a syscall in
*another* process in the same cgroup hangs indefinitely.
Reproducing:
# mkdir -p strace_run
# mkdir /sys/fs/cgroup/memory/1
1 - 100 of 145 matches
Mail list logo
