Hi
17.10.2017, 23:01, "Hans-Frieder Vogt" :
> attached is a driver that supports the serial OneWire masters from
> iButtonLink(TM) in the w1 kernel driver. In order to be usable it needs an
> updated userland tool (patch included in documentation file). The patch is
> against
Hi
17.10.2017, 23:01, "Hans-Frieder Vogt" :
> attached is a driver that supports the serial OneWire masters from
> iButtonLink(TM) in the w1 kernel driver. In order to be usable it needs an
> updated userland tool (patch included in documentation file). The patch is
> against linux-next.
On Mon, Oct 30, 2017 at 11:30:59AM -0500, Christopher Lameter wrote:
> Historically cpusets were not used for cpu isolation. They were used to
> restrict applications threads to sets of cpus for performance reasons. And
> we are here dealing with individual processors.
The HPC workloads very much
On Mon, Oct 30, 2017 at 11:30:59AM -0500, Christopher Lameter wrote:
> Historically cpusets were not used for cpu isolation. They were used to
> restrict applications threads to sets of cpus for performance reasons. And
> we are here dealing with individual processors.
The HPC workloads very much
+ devicetree list
Hi,
On Mon, Oct 30, 2017 at 10:49:49AM +0800, Lin Huang wrote:
> some i2c hid devices have reset gpio, need to control
> it in the driver.
>
> Change-Id: I87bca954bffc7eb7b35711406f522cb3d0fc2ded
You should be removing these Gerrit ID lines from patches before sending
them to
On Mon, 2017-10-30 at 17:11 +0100, Peter Zijlstra wrote:
> On Mon, Oct 30, 2017 at 10:48:04AM -0500, Christopher Lameter wrote:
> > On Fri, 27 Oct 2017, Peter Zijlstra wrote:
> >
> > > I _strongly_ object to this statement, isolcpus is _not_ the preferred
> > > way, cpusets are.
> > >
> > > And
+ devicetree list
Hi,
On Mon, Oct 30, 2017 at 10:49:49AM +0800, Lin Huang wrote:
> some i2c hid devices have reset gpio, need to control
> it in the driver.
>
> Change-Id: I87bca954bffc7eb7b35711406f522cb3d0fc2ded
You should be removing these Gerrit ID lines from patches before sending
them to
On Mon, 2017-10-30 at 17:11 +0100, Peter Zijlstra wrote:
> On Mon, Oct 30, 2017 at 10:48:04AM -0500, Christopher Lameter wrote:
> > On Fri, 27 Oct 2017, Peter Zijlstra wrote:
> >
> > > I _strongly_ object to this statement, isolcpus is _not_ the preferred
> > > way, cpusets are.
> > >
> > > And
Ulf Hansson writes:
> Hi Neil,
>
> [...]
>
>> +
>> + pm_genpd_init(_hdmi_pd.genpd, _qos_governor,
>> + meson_gx_pwrc_vpu_get_power(_hdmi_pd));
>> +
>
> This means that you may initialize the genpd in powered on state.
>
> For that scenario, I
Ulf Hansson writes:
> Hi Neil,
>
> [...]
>
>> +
>> + pm_genpd_init(_hdmi_pd.genpd, _qos_governor,
>> + meson_gx_pwrc_vpu_get_power(_hdmi_pd));
>> +
>
> This means that you may initialize the genpd in powered on state.
>
> For that scenario, I think you will hit a clock
On Mon, Oct 30, 2017 at 12:56:36PM +0100, Aleksandar Markovic wrote:
> From: Miodrag Dinic
>
> Provide amendments to the MIPS generic platform framework so that
> the new generic-based board Ranchu can be chosen to be built.
A bit more info about the board would be good
On Mon, Oct 30, 2017 at 12:56:36PM +0100, Aleksandar Markovic wrote:
> From: Miodrag Dinic
>
> Provide amendments to the MIPS generic platform framework so that
> the new generic-based board Ranchu can be chosen to be built.
A bit more info about the board would be good here. What boot protocol
On 30/10/2017 16:40, Ulf Hansson wrote:
> Hi Neil,
>
> [...]
>
>> +
>> + pm_genpd_init(_hdmi_pd.genpd, _qos_governor,
>> + meson_gx_pwrc_vpu_get_power(_hdmi_pd));
>> +
>
> This means that you may initialize the genpd in powered on state.
>
> For that scenario, I think
On 30/10/2017 16:40, Ulf Hansson wrote:
> Hi Neil,
>
> [...]
>
>> +
>> + pm_genpd_init(_hdmi_pd.genpd, _qos_governor,
>> + meson_gx_pwrc_vpu_get_power(_hdmi_pd));
>> +
>
> This means that you may initialize the genpd in powered on state.
>
> For that scenario, I think
On Mon, 2017-10-30 at 15:49 +, David Howells wrote:
> Mimi Zohar wrote:
>
> > Huh?! With the "secure_boot" policy enabled on the boot command line,
> > IMA-appraisal would verify the kexec kernel image, firmware, kernel
> > modules, and custom IMA policy
On Mon, 2017-10-30 at 15:49 +, David Howells wrote:
> Mimi Zohar wrote:
>
> > Huh?! With the "secure_boot" policy enabled on the boot command line,
> > IMA-appraisal would verify the kexec kernel image, firmware, kernel
> > modules, and custom IMA policy signatures.
>
> What happens if the
Hi Eduardo,
Today's linux-next merge of the thermal-soc tree got a conflict in:
drivers/thermal/hisi_thermal.c
between commit:
3fe156f1dd9909 ("thermal: hisilicon: constify thermal_zone_of_device_ops
structures")
from Linus' tree and various commits from the thermal-soc tree.
I fixed it
Hi Eduardo,
Today's linux-next merge of the thermal-soc tree got a conflict in:
drivers/thermal/hisi_thermal.c
between commit:
3fe156f1dd9909 ("thermal: hisilicon: constify thermal_zone_of_device_ops
structures")
from Linus' tree and various commits from the thermal-soc tree.
I fixed it
Hi Marc,
On Mon, Oct 30, 2017 at 08:00:08AM +, Marc Zyngier wrote:
> > static int __init gic_of_init(struct device_node *node,
> > struct device_node *parent)
> > @@ -768,6 +806,8 @@ static int __init gic_of_init(struct device_node *node,
> > }
> > }
Hi Marc,
On Mon, Oct 30, 2017 at 08:00:08AM +, Marc Zyngier wrote:
> > static int __init gic_of_init(struct device_node *node,
> > struct device_node *parent)
> > @@ -768,6 +806,8 @@ static int __init gic_of_init(struct device_node *node,
> > }
> > }
On 10/30/17 5:43 AM, Jan Kara wrote:
On Sat 28-10-17 02:22:18, Yang Shi wrote:
If some process generates events into a huge or unlimit event queue, but no
listener read them, they may consume significant amount of memory silently
until oom happens or some memory pressure issue is raised.
It'd
On 10/30/17 5:43 AM, Jan Kara wrote:
On Sat 28-10-17 02:22:18, Yang Shi wrote:
If some process generates events into a huge or unlimit event queue, but no
listener read them, they may consume significant amount of memory silently
until oom happens or some memory pressure issue is raised.
It'd
On Mon, Oct 30, 2017 at 05:24:34PM +0100, Gregory CLEMENT wrote:
> Hi Russell King,
>
> Here you will find all the objects included the vmlinux:
>
> http://free-electrons.com/~gregory/pub/compressed.tgz
Thanks. Unfortunately, nothing stands out, but I do see a difference
between the output of
On Mon, Oct 30, 2017 at 05:24:34PM +0100, Gregory CLEMENT wrote:
> Hi Russell King,
>
> Here you will find all the objects included the vmlinux:
>
> http://free-electrons.com/~gregory/pub/compressed.tgz
Thanks. Unfortunately, nothing stands out, but I do see a difference
between the output of
On Mon, 2017-10-30 at 16:48 +0100, Dmitry Vyukov wrote:
> >
> > net-next tree :
> >
> > $ git log --oneline e7989f973ae1b90ec7c0b671c81.. -- drivers/net/tun.c
> > f8ddadc4db6c7b7029b6d0e0d9af24f74ad27ca2 Merge
> > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
> >
On Mon, 2017-10-30 at 16:48 +0100, Dmitry Vyukov wrote:
> >
> > net-next tree :
> >
> > $ git log --oneline e7989f973ae1b90ec7c0b671c81.. -- drivers/net/tun.c
> > f8ddadc4db6c7b7029b6d0e0d9af24f74ad27ca2 Merge
> > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
> >
On 10/30/17 10:12 AM, Borislav Petkov wrote:
...
> Lemme see:
>
> sev_dbg_crypt() does
>
> ret = __sev_dbg_decrypt(kvm,
>__sme_page_pa(src_p[0]) + s_off,
>dst_vaddr, 0,
>
On 10/30/17 10:12 AM, Borislav Petkov wrote:
...
> Lemme see:
>
> sev_dbg_crypt() does
>
> ret = __sev_dbg_decrypt(kvm,
>__sme_page_pa(src_p[0]) + s_off,
>dst_vaddr, 0,
>
On Mon, Oct 30, 2017 at 09:52:15AM +0100, Greg Kroah-Hartman wrote:
> On Fri, Oct 27, 2017 at 11:24:22AM -0500, Bin Liu wrote:
> > Hi,
> >
> > On Tue, Oct 24, 2017 at 03:08:35AM -0700, Kees Cook wrote:
> > > In preparation for unconditionally passing the struct timer_list pointer
> > > to
> > >
On Mon, Oct 30, 2017 at 09:52:15AM +0100, Greg Kroah-Hartman wrote:
> On Fri, Oct 27, 2017 at 11:24:22AM -0500, Bin Liu wrote:
> > Hi,
> >
> > On Tue, Oct 24, 2017 at 03:08:35AM -0700, Kees Cook wrote:
> > > In preparation for unconditionally passing the struct timer_list pointer
> > > to
> > >
On Mon, 30 Oct 2017, Peter Zijlstra wrote:
> > isolcpus is the *right* approach here because you are micromanaging the OS
> > and are putting dedicated pieces of software on each core.
>
> That is what you want, and cpusets should allow for that just fine.
Well yes a cpuset of one processor I
On Mon, 30 Oct 2017, Peter Zijlstra wrote:
> > isolcpus is the *right* approach here because you are micromanaging the OS
> > and are putting dedicated pieces of software on each core.
>
> That is what you want, and cpusets should allow for that just fine.
Well yes a cpuset of one processor I
On 30 October 2017 at 17:19, Joel Fernandes wrote:
> Hi Vincent,
>
> On Mon, Oct 30, 2017 at 9:00 AM, Vincent Guittot
> wrote:
>> On 28 October 2017 at 11:59, Joel Fernandes wrote:
>>> find_idlest_group_cpu goes through CPUs of a
On 30 October 2017 at 17:19, Joel Fernandes wrote:
> Hi Vincent,
>
> On Mon, Oct 30, 2017 at 9:00 AM, Vincent Guittot
> wrote:
>> On 28 October 2017 at 11:59, Joel Fernandes wrote:
>>> find_idlest_group_cpu goes through CPUs of a group previous selected by
>>> find_idlest_group.
On 19 October 2017 at 09:45, Suzuki K Poulose wrote:
> Add ARM Cortex A-73 ETM PIDs to the known ETM ips. While at it
> also add description of the CPU to which the ETM belongs, to make
> it easier to identify the ETM devices.
>
> Cc: Mathieu Poirier
On 19 October 2017 at 09:45, Suzuki K Poulose wrote:
> Add ARM Cortex A-73 ETM PIDs to the known ETM ips. While at it
> also add description of the CPU to which the ETM belongs, to make
> it easier to identify the ETM devices.
>
> Cc: Mathieu Poirier
> Signed-off-by: Suzuki K Poulose
> ---
>
Hi Russell King,
On lun., oct. 30 2017, Russell King - ARM Linux wrote:
> On Mon, Oct 30, 2017 at 05:01:44PM +0100, Gregory CLEMENT wrote:
>> Hi Russell King,
>>
>> On lun., oct. 30 2017, Russell King - ARM Linux
>> wrote:
>>
>> > On Mon,
Hi Russell King,
On lun., oct. 30 2017, Russell King - ARM Linux wrote:
> On Mon, Oct 30, 2017 at 05:01:44PM +0100, Gregory CLEMENT wrote:
>> Hi Russell King,
>>
>> On lun., oct. 30 2017, Russell King - ARM Linux
>> wrote:
>>
>> > On Mon, Oct 30, 2017 at 02:48:02PM +0100, Gregory
Hi,
As a heads-up, while fuzzing arm64 v4.14-rc{4,7} with Syzkaller, I hit a
KASAN splat in event_sched_out():
[ 133.225742]
==
[ 133.229374] BUG: KASAN: null-ptr-deref in event_sched_out.isra.47+0x428/0x580
[ 133.230843] Read
Hi,
As a heads-up, while fuzzing arm64 v4.14-rc{4,7} with Syzkaller, I hit a
KASAN splat in event_sched_out():
[ 133.225742]
==
[ 133.229374] BUG: KASAN: null-ptr-deref in event_sched_out.isra.47+0x428/0x580
[ 133.230843] Read
Hi Joel,
On Mon, Oct 30, 2017 at 8:22 AM, Joel Stanley wrote:
> The ASPEED SoC must deassert a reset in order to use the ADC peripheral.
>
> The device tree bindings are updated to document the resets phandle, and
> the example is updated to match what is expected for both the
Hi Joel,
On Mon, Oct 30, 2017 at 8:22 AM, Joel Stanley wrote:
> The ASPEED SoC must deassert a reset in order to use the ADC peripheral.
>
> The device tree bindings are updated to document the resets phandle, and
> the example is updated to match what is expected for both the reset and
> clock
On Mon, Oct 30, 2017 at 11:07:20AM +, Hatayama, Daisuke wrote:
> > From: Marc-André Lureau
> >
> > Since qemu 2.9, DMA write operations are allowed. However, usage of this
> > interface from kernel or user-space is strongly discouraged by the
> > maintainers. This
On Mon, Oct 30, 2017 at 09:34:19PM +0530, Arvind Yadav wrote:
> Fix checkpatch.pl error:
> ERROR: space prohibited before open square bracket '['.
>
> Signed-off-by: Arvind Yadav
Applied to libata/for-4.15.
Thanks.
--
tejun
On Mon, Oct 30, 2017 at 11:07:20AM +, Hatayama, Daisuke wrote:
> > From: Marc-André Lureau
> >
> > Since qemu 2.9, DMA write operations are allowed. However, usage of this
> > interface from kernel or user-space is strongly discouraged by the
> > maintainers. This patch is meant for
On Mon, Oct 30, 2017 at 09:34:19PM +0530, Arvind Yadav wrote:
> Fix checkpatch.pl error:
> ERROR: space prohibited before open square bracket '['.
>
> Signed-off-by: Arvind Yadav
Applied to libata/for-4.15.
Thanks.
--
tejun
Hi Vincent,
On Mon, Oct 30, 2017 at 9:00 AM, Vincent Guittot
wrote:
> On 28 October 2017 at 11:59, Joel Fernandes wrote:
>> find_idlest_group_cpu goes through CPUs of a group previous selected by
>> find_idlest_group. find_idlest_group returns NULL
Hi Vincent,
On Mon, Oct 30, 2017 at 9:00 AM, Vincent Guittot
wrote:
> On 28 October 2017 at 11:59, Joel Fernandes wrote:
>> find_idlest_group_cpu goes through CPUs of a group previous selected by
>> find_idlest_group. find_idlest_group returns NULL if the local group is the
>> selected one and
That's safe to do for now. Here's the 0-day failure thread:
https://lists.01.org/pipermail/lkp/2017-October/007427.html If I can
sort out the issue, I'll submit a v3.
On Mon, Oct 30, 2017 at 8:46 AM, Masahiro Yamada
wrote:
> 2017-10-30 15:50 GMT+09:00 Masahiro
That's safe to do for now. Here's the 0-day failure thread:
https://lists.01.org/pipermail/lkp/2017-October/007427.html If I can
sort out the issue, I'll submit a v3.
On Mon, Oct 30, 2017 at 8:46 AM, Masahiro Yamada
wrote:
> 2017-10-30 15:50 GMT+09:00 Masahiro Yamada :
>> 2017-10-29 0:00
On Mon, Oct 30, 2017 at 05:01:44PM +0100, Gregory CLEMENT wrote:
> Hi Russell King,
>
> On lun., oct. 30 2017, Russell King - ARM Linux
> wrote:
>
> > On Mon, Oct 30, 2017 at 02:48:02PM +0100, Gregory CLEMENT wrote:
> >> Hi Russell,
> >>
> >> So I tested the branch
On Mon, Oct 30, 2017 at 05:01:44PM +0100, Gregory CLEMENT wrote:
> Hi Russell King,
>
> On lun., oct. 30 2017, Russell King - ARM Linux
> wrote:
>
> > On Mon, Oct 30, 2017 at 02:48:02PM +0100, Gregory CLEMENT wrote:
> >> Hi Russell,
> >>
> >> So I tested the branch fixes in your git tree.
>
On Mon, Oct 30, 2017 at 10:48:04AM -0500, Christopher Lameter wrote:
> On Fri, 27 Oct 2017, Peter Zijlstra wrote:
>
> > I _strongly_ object to this statement, isolcpus is _not_ the preferred
> > way, cpusets are.
> >
> > And yes, while cpusets suffers some problems, we _should_ really fix
> >
On Mon, Oct 30, 2017 at 10:48:04AM -0500, Christopher Lameter wrote:
> On Fri, 27 Oct 2017, Peter Zijlstra wrote:
>
> > I _strongly_ object to this statement, isolcpus is _not_ the preferred
> > way, cpusets are.
> >
> > And yes, while cpusets suffers some problems, we _should_ really fix
> >
On Mon, Oct 30, 2017 at 10:46:36AM -0400, Zi Yan wrote:
> From: Zi Yan
>
> We need to deposit pre-allocated PTE page table when a PMD migration
> entry is copied in copy_huge_pmd(). Otherwise, we will leak the
> pre-allocated page and cause a NULL pointer dereference later
On Mon, Oct 30, 2017 at 10:46:36AM -0400, Zi Yan wrote:
> From: Zi Yan
>
> We need to deposit pre-allocated PTE page table when a PMD migration
> entry is copied in copy_huge_pmd(). Otherwise, we will leak the
> pre-allocated page and cause a NULL pointer dereference later
> in zap_huge_pmd().
>
On Mon, Oct 30, 2017 at 4:44 AM, Joel Stanley wrote:
> In order to use i2c from a cold boot, the i2c peripheral must be taken
> out of reset. We request a shared reset controller each time a bus
> driver is loaded, as the reset is shared between the 14 i2c buses.
>
> On remove the
On Mon, Oct 30, 2017 at 4:44 AM, Joel Stanley wrote:
> In order to use i2c from a cold boot, the i2c peripheral must be taken
> out of reset. We request a shared reset controller each time a bus
> driver is loaded, as the reset is shared between the 14 i2c buses.
>
> On remove the reset is
Hi Russell,
On lun., oct. 30 2017, Russell King - ARM Linux wrote:
> On Mon, Oct 30, 2017 at 04:33:07PM +0100, Gregory CLEMENT wrote:
>> Humm no, actually it was with the wrong branch. If I have the patch
>> "ARM: verify size of zImage" then
Fix checkpatch.pl error:
ERROR: space prohibited before open square bracket '['.
Signed-off-by: Arvind Yadav
---
drivers/ata/pata_pdc2027x.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/ata/pata_pdc2027x.c
Hi Russell,
On lun., oct. 30 2017, Russell King - ARM Linux wrote:
> On Mon, Oct 30, 2017 at 04:33:07PM +0100, Gregory CLEMENT wrote:
>> Humm no, actually it was with the wrong branch. If I have the patch
>> "ARM: verify size of zImage" then arch/arm/boot/compressed/vmlinux is
>> not
Fix checkpatch.pl error:
ERROR: space prohibited before open square bracket '['.
Signed-off-by: Arvind Yadav
---
drivers/ata/pata_pdc2027x.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/ata/pata_pdc2027x.c b/drivers/ata/pata_pdc2027x.c
index 82bfd51..ffd8d33
Some eeproms in the at24 family do not roll over page reads,
e.g. the Microchip 24AA16/24LC16B. On those eeproms, reads
that straddle block boundaries will not work correctly.
Solution:
Implement read rollover in the driver. To enable it, add the
AT24_FLAG_NO_RDROL flag to the eeprom entry in the
Some eeproms in the at24 family do not roll over page reads,
e.g. the Microchip 24AA16/24LC16B. On those eeproms, reads
that straddle block boundaries will not work correctly.
Solution:
Implement read rollover in the driver. To enable it, add the
AT24_FLAG_NO_RDROL flag to the eeprom entry in the
On 30.10.2017 15:55, Tejun Heo wrote:
> On Sun, Oct 29, 2017 at 05:36:53PM +0100, Maciej S. Szmigiero wrote:
>> CFQ scheduler has a property that processes (or tasks in cgroups v1) that
>> aren't assigned to any particular cgroup - that is, which stay in the root
>> cgroup - effectively form an
On 30.10.2017 15:55, Tejun Heo wrote:
> On Sun, Oct 29, 2017 at 05:36:53PM +0100, Maciej S. Szmigiero wrote:
>> CFQ scheduler has a property that processes (or tasks in cgroups v1) that
>> aren't assigned to any particular cgroup - that is, which stay in the root
>> cgroup - effectively form an
Hi Russell King,
On lun., oct. 30 2017, Russell King - ARM Linux wrote:
> On Mon, Oct 30, 2017 at 02:48:02PM +0100, Gregory CLEMENT wrote:
>> Hi Russell,
>>
>> So I tested the branch fixes in your git tree.
>>
>> After doing a "make multi_v7_defconfig; make zImage", I
Hi Russell King,
On lun., oct. 30 2017, Russell King - ARM Linux wrote:
> On Mon, Oct 30, 2017 at 02:48:02PM +0100, Gregory CLEMENT wrote:
>> Hi Russell,
>>
>> So I tested the branch fixes in your git tree.
>>
>> After doing a "make multi_v7_defconfig; make zImage", I got the message
>>
On 28 October 2017 at 11:59, Joel Fernandes wrote:
> find_idlest_group_cpu goes through CPUs of a group previous selected by
> find_idlest_group. find_idlest_group returns NULL if the local group is the
> selected one and doesn't execute find_idlest_group_cpu if the group to
On 28 October 2017 at 11:59, Joel Fernandes wrote:
> find_idlest_group_cpu goes through CPUs of a group previous selected by
> find_idlest_group. find_idlest_group returns NULL if the local group is the
> selected one and doesn't execute find_idlest_group_cpu if the group to which
> 'cpu' belongs
On Fri, Oct 27, 2017 at 03:25:28PM -0700, Mark Salyzyn wrote:
> Ensure monotonic and realtime are inline, small price to pay for
> high volume common request.
Is this just based on a hunch, or is it based on proper measurement?
If proper measurement, where's the data? What CPU was it measured
On Fri, Oct 27, 2017 at 03:25:28PM -0700, Mark Salyzyn wrote:
> Ensure monotonic and realtime are inline, small price to pay for
> high volume common request.
Is this just based on a hunch, or is it based on proper measurement?
If proper measurement, where's the data? What CPU was it measured
On Mon, Oct 30, 2017 at 12:40 AM, Fengguang Wu wrote:
>
> CC nvdimm maintainers.
>
> On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote:
>>
>> Hi Linus,
>>
>> Up to now we see the below boot error/warnings when testing v4.14-rc6.
>>
>> They hit the RC release
On Mon, Oct 30, 2017 at 12:40 AM, Fengguang Wu wrote:
>
> CC nvdimm maintainers.
>
> On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote:
>>
>> Hi Linus,
>>
>> Up to now we see the below boot error/warnings when testing v4.14-rc6.
>>
>> They hit the RC release mainly due to various
On Fri, Oct 27, 2017 at 1:53 PM, Jan Kara wrote:
> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
>> On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi wrote:
>> > We discovered some problems in the latest fsnotify/fanotify codebase with
>> > the help of a
Hi Greg,
2017-10-21 1:26 GMT+09:00 Greg KH :
> On Sat, Oct 21, 2017 at 01:18:14AM +0900, Masahiro Yamada wrote:
>> 2017-10-20 23:47 GMT+09:00 Greg KH :
>> > On Fri, Oct 20, 2017 at 11:26:16PM +0900, Masahiro Yamada wrote:
>> >> 2017-10-20
On Fri, Oct 27, 2017 at 1:53 PM, Jan Kara wrote:
> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
>> On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi wrote:
>> > We discovered some problems in the latest fsnotify/fanotify codebase with
>> > the help of a stress test (Xiong Zhou is working on
Hi Greg,
2017-10-21 1:26 GMT+09:00 Greg KH :
> On Sat, Oct 21, 2017 at 01:18:14AM +0900, Masahiro Yamada wrote:
>> 2017-10-20 23:47 GMT+09:00 Greg KH :
>> > On Fri, Oct 20, 2017 at 11:26:16PM +0900, Masahiro Yamada wrote:
>> >> 2017-10-20 22:54 GMT+09:00 Greg KH :
>> >> > On Fri, Oct 20, 2017 at
Hi Randy
> -Original Message-
> From: Randy Dunlap [mailto:rdun...@infradead.org]
> Sent: 27 October 2017 17:44
> To: Gabriele Paoloni; catalin.mari...@arm.com; will.dea...@arm.com;
> robh...@kernel.org; frowand.l...@gmail.com; bhelg...@google.com;
> raf...@kernel.org; a...@arndb.de;
Hi Randy
> -Original Message-
> From: Randy Dunlap [mailto:rdun...@infradead.org]
> Sent: 27 October 2017 17:44
> To: Gabriele Paoloni; catalin.mari...@arm.com; will.dea...@arm.com;
> robh...@kernel.org; frowand.l...@gmail.com; bhelg...@google.com;
> raf...@kernel.org; a...@arndb.de;
On Mon, Oct 30, 2017 at 04:33:07PM +0100, Gregory CLEMENT wrote:
> Humm no, actually it was with the wrong branch. If I have the patch
> "ARM: verify size of zImage" then arch/arm/boot/compressed/vmlinux is
> not generated.
>
> But if I remove this patch then I can generate this file and so:
>
On Mon, Oct 30, 2017 at 04:33:07PM +0100, Gregory CLEMENT wrote:
> Humm no, actually it was with the wrong branch. If I have the patch
> "ARM: verify size of zImage" then arch/arm/boot/compressed/vmlinux is
> not generated.
>
> But if I remove this patch then I can generate this file and so:
>
Fix checkpatch.pl error:
ERROR: space prohibited before open square bracket '['.
Signed-off-by: Arvind Yadav
---
drivers/atm/iphase.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/atm/iphase.c b/drivers/atm/iphase.c
index
Fix checkpatch.pl error:
ERROR: space prohibited before open square bracket '['.
Signed-off-by: Arvind Yadav
---
drivers/atm/iphase.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/atm/iphase.c b/drivers/atm/iphase.c
index fc72b763..a785c6e 100644
---
On Mon, Oct 30, 2017 at 04:09:43PM +0100, Arnd Bergmann wrote:
> On Fri, Oct 27, 2017 at 5:27 PM, Russell King - ARM Linux
> wrote:
>
> >
> > There's three things wrong, all of which I have patches to address:
> >
> > 1. The decompressor code reading the image data
On Mon, Oct 30, 2017 at 04:09:43PM +0100, Arnd Bergmann wrote:
> On Fri, Oct 27, 2017 at 5:27 PM, Russell King - ARM Linux
> wrote:
>
> >
> > There's three things wrong, all of which I have patches to address:
> >
> > 1. The decompressor code reading the image data sometimes issues unaligned
> >
Mimi Zohar wrote:
> Huh?! With the "secure_boot" policy enabled on the boot command line,
> IMA-appraisal would verify the kexec kernel image, firmware, kernel
> modules, and custom IMA policy signatures.
What happens if the "secure_boot" policy isn't enabled on the
Mimi Zohar wrote:
> Huh?! With the "secure_boot" policy enabled on the boot command line,
> IMA-appraisal would verify the kexec kernel image, firmware, kernel
> modules, and custom IMA policy signatures.
What happens if the "secure_boot" policy isn't enabled on the boot command
line? Can you
From: Markus Elfring
Date: Mon, 30 Oct 2017 16:34:44 +0100
* Print a line break together with other data in a single function call.
* Adjust indentation.
Signed-off-by: Markus Elfring
---
drivers/pinctrl/pinctrl-mcp23s08.c | 11
From: Markus Elfring
Date: Mon, 30 Oct 2017 16:34:44 +0100
* Print a line break together with other data in a single function call.
* Adjust indentation.
Signed-off-by: Markus Elfring
---
drivers/pinctrl/pinctrl-mcp23s08.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
On Mon, Oct 30, 2017 at 02:48:02PM +0100, Gregory CLEMENT wrote:
> Hi Russell,
>
> So I tested the branch fixes in your git tree.
>
> After doing a "make multi_v7_defconfig; make zImage", I got the message
> "arm-linux-gnueabi-ld: error: zImage file size is incorrect" you added
> in the commit
On Mon, Oct 30, 2017 at 02:48:02PM +0100, Gregory CLEMENT wrote:
> Hi Russell,
>
> So I tested the branch fixes in your git tree.
>
> After doing a "make multi_v7_defconfig; make zImage", I got the message
> "arm-linux-gnueabi-ld: error: zImage file size is incorrect" you added
> in the commit
On Mon, 2017-10-30 at 10:49 -0400, J. Bruce Fields wrote:
> On Mon, Oct 30, 2017 at 04:47:58PM +0300, Vasily Averin wrote:
> > nlm_complain_hosts() walk through nlm_server_hosts hlist that should be
> > protected by nlm_host_mutex.
>
> I haven't looked at the NLM locking in ages. Do we know who
On Mon, 2017-10-30 at 10:49 -0400, J. Bruce Fields wrote:
> On Mon, Oct 30, 2017 at 04:47:58PM +0300, Vasily Averin wrote:
> > nlm_complain_hosts() walk through nlm_server_hosts hlist that should be
> > protected by nlm_host_mutex.
>
> I haven't looked at the NLM locking in ages. Do we know who
On Sun, Oct 29, 2017 at 2:01 PM, Eric Dumazet wrote:
> On Sun, 2017-10-29 at 13:45 +0100, Thomas Gleixner wrote:
>> On Fri, 27 Oct 2017, syzbot wrote:
>>
>> Cc'ed network folks.
>>
>> > syzkaller hit the following crash on
>> > e7989f973ae1b90ec7c0b671c81f7f553affccbe
>>
On Sun, Oct 29, 2017 at 2:01 PM, Eric Dumazet wrote:
> On Sun, 2017-10-29 at 13:45 +0100, Thomas Gleixner wrote:
>> On Fri, 27 Oct 2017, syzbot wrote:
>>
>> Cc'ed network folks.
>>
>> > syzkaller hit the following crash on
>> > e7989f973ae1b90ec7c0b671c81f7f553affccbe
>> >
From: Markus Elfring
Date: Mon, 30 Oct 2017 16:26:09 +0100
* The script "checkpatch.pl" pointed information out like the following.
WARNING: Prefer seq_puts to seq_printf
Thus fix the affected source code places.
* Adjust jump targets so that a bit of
From: Markus Elfring
Date: Mon, 30 Oct 2017 16:26:09 +0100
* The script "checkpatch.pl" pointed information out like the following.
WARNING: Prefer seq_puts to seq_printf
Thus fix the affected source code places.
* Adjust jump targets so that a bit of exception handling can be better
On Fri, 27 Oct 2017, Peter Zijlstra wrote:
> I _strongly_ object to this statement, isolcpus is _not_ the preferred
> way, cpusets are.
>
> And yes, while cpusets suffers some problems, we _should_ really fix
> those and not promote this piece of shit isolcpus crap.
Well low level control at the
On Fri, 27 Oct 2017, Peter Zijlstra wrote:
> I _strongly_ object to this statement, isolcpus is _not_ the preferred
> way, cpusets are.
>
> And yes, while cpusets suffers some problems, we _should_ really fix
> those and not promote this piece of shit isolcpus crap.
Well low level control at the
701 - 800 of 1616 matches
Mail list logo