Neil Armstrong | 26 May 11:38 2016

[RFC PATCH 0/2] scpi: Add SCPI framework to handle vendors variants

Since the current SCPI implementation, based on [0]:
- is (at leat) JUNO specific
- does not specify a strong "standard"
- does not specify a strong MHU interface specification

SoC vendors could implement a variant with slight changes in message
indexes, new messages types, different messages data format or different MHU
communication scheme.

To keep the spirit of the SCPI interface, add a thin "register" layer to get
the ops from the parent node and switch the drivers using the ops to use
the new of_scpi_ops_get() call.


Neil Armstrong (2):
  firmware: Add a SCPI framework to handle multiple vendors
  firmware: scpi: Switch scpi drivers to use new Framework calls

 drivers/clk/clk-scpi.c         |  18 ++++---
 drivers/cpufreq/scpi-cpufreq.c |   7 +--
 drivers/firmware/Makefile      |   1 +
 drivers/firmware/arm_scpi.c    |  18 +++----
 drivers/firmware/scpi.c        | 110 +++++++++++++++++++++++++++++++++++++++++
 drivers/hwmon/scpi-hwmon.c     |   6 +--
 include/linux/scpi_protocol.h  |  33 ++++++++++++-
 7 files changed, 169 insertions(+), 24 deletions(-)
 create mode 100644 drivers/firmware/scpi.c

(Continue reading)

Vitaly Kuznetsov | 26 May 11:26 2016

[PATCH v2] efi: fix for_each_efi_memory_desc_in_map() for empty memmaps

Commit 78ce248faa3c ("efi: Iterate over efi.memmap in
for_each_efi_memory_desc()") introduced a regression for systems booted
with 'noefi' kernel option. In particular, I observe early kernel hang in
efi_find_mirror() on for_each_efi_memory_desc() call. As we don't have
efi memmap we enter this iterator with the following parameters: = 0, efi.memmap.map_end = 0, efi.memmap.desc_size = 28

for_each_efi_memory_desc_in_map() does the following comparison:

(md) <= (efi_memory_desc_t *)((m)->map_end - (m)->desc_size);

where md = 0, (m)->map_end = 0 and (m)->desc_size = 28 but when we subtract
something from a NULL pointer wrap around happens and we end up returning
invalid pointer.

Fixes: 78ce248faa3c ("efi: Iterate over efi.memmap in for_each_efi_memory_desc()")
Signed-off-by: Vitaly Kuznetsov <vkuznets <at>>
Changes since v1: cast to (void *) instead of (efi_memory_desc_t *)
 [Matt Fleming]. It seems we're still exercising some sort of an
 undefined behavioir as C standard only allows us to compare pointers
 which point to the same object in memory (or one position past the end of
 the object) and I doubt NULL pointers are covered by this rule but gcc
 gives no warning, I think we're relatively safe. It may also make sense
 to write this comparison casting everything to something like unsigned
 long I guess...
 include/linux/efi.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
(Continue reading)

Yuyang Du | 26 May 03:14 2016

[PATCH 0/2] sched/fair: Skip sched avgs update for new group task before wake_up_new_task()

Hi Peter,

Vincent reported this problem, which is there for a while. The first patch
is cleanup as well as paving the way to the fix.


Yuyang Du (2):
  sched/fair: Clean up attach_entity_load_avg()
  sched/fair: Skip detach and attach load avgs for new group task

 kernel/sched/auto_group.c |    2 +-
 kernel/sched/core.c       |    8 +++---
 kernel/sched/fair.c       |   62 ++++++++++++++++++++++++---------------------
 kernel/sched/sched.h      |    4 +--
 4 files changed, 40 insertions(+), 36 deletions(-)



Neil Armstrong | 26 May 10:31 2016

[PATCH] watchdog: Add a device managed API for watchdog_register_device()

This helps in reducing code in .remove callbacks and sometimes
dropping .remove callbacks entirely.

Signed-off-by: Neil Armstrong <narmstrong <at>>
 Documentation/driver-model/devres.txt |  3 +++
 drivers/watchdog/watchdog_core.c      | 36 +++++++++++++++++++++++++++++++++++
 include/linux/watchdog.h              |  3 +++
 3 files changed, 42 insertions(+)

diff --git a/Documentation/driver-model/devres.txt b/Documentation/driver-model/devres.txt
index c63eea0..589296b 100644
--- a/Documentation/driver-model/devres.txt
+++ b/Documentation/driver-model/devres.txt
 <at>  <at>  -357,3 +357,6  <at>  <at>  SLAVE DMA ENGINE

+  devm_watchdog_register_device()
diff --git a/drivers/watchdog/watchdog_core.c b/drivers/watchdog/watchdog_core.c
index 981a668..a664d80 100644
--- a/drivers/watchdog/watchdog_core.c
+++ b/drivers/watchdog/watchdog_core.c
 <at>  <at>  -329,6 +329,42  <at>  <at>  void watchdog_unregister_device(struct watchdog_device *wdd)


+static void devm_watchdog_unregister_device(struct device *dev, void *res)
(Continue reading)

Ulf Hansson | 26 May 10:11 2016

[GIT PULL] MMC fixes for v.4.7 rc1

Hi Linus,

Here are some mmc fixes intended for v4.7 rc1. They are based on a
commit earlier in the merge window and have been tested in linux-next
for a while.

Details are as usual found in the signed tag. Please pull this in!

Kind regards
Ulf Hansson

The following changes since commit 16490980e396fac079248b23b1dd81e7d48bebf3:

  Merge tag 'device-properties-4.7-rc1' of
(2016-05-16 19:51:04 -0700)

are available in the git repository at:

  git:// tags/mmc-v4.7-rc1

for you to fetch changes up to 265984b36ce82fec67957d452dd2b22e010611e4:

  mmc: sdhci-acpi: Remove MMC_CAP_BUS_WIDTH_TEST for Intel controllers
(2016-05-23 11:52:41 +0200)

MMC core:
 - Prevent re-tuning while serving requests for RPMB partitions
 - Extend timeout for long read time quirk to support more eMMCs
(Continue reading)

Weifeng Voon | 26 May 10:01 2016

[PATCH 0/5] i2c: designware: Enable fast mode plus and high speed

Enabled fast mode plus and high speed which supported by APL SoC.

Weifeng Voon (5):
  i2c: designware: Move clk_freq into struct dw_i2c_dev
  i2c: designware: get fast plus and high speed *CNT configuration
  i2c: designware: Enable fast mode plus
  i2c: designware: set the common config before the if else
  i2c: designware: Enable high speed mode

 drivers/i2c/busses/i2c-designware-core.c    | 33 +++++++++++++++++++++---
 drivers/i2c/busses/i2c-designware-core.h    | 12 +++++++++
 drivers/i2c/busses/i2c-designware-platdrv.c | 39 +++++++++++++++++++----------
 3 files changed, 68 insertions(+), 16 deletions(-)



Shubham Bansal | 26 May 10:01 2016

[PATCH] Staging: android: ion: fixed a kzalloc coding style issue.

Fixed a coding style issue. Issue reported by

Signed-off-by: Shubham Bansal <illusionist.neo <at>>
 drivers/staging/android/ion/ion.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/android/ion/ion.c b/drivers/staging/android/ion/ion.c
index 8536567..2217ccb 100644
--- a/drivers/staging/android/ion/ion.c
+++ b/drivers/staging/android/ion/ion.c
 <at>  <at>  -184,7 +184,7  <at>  <at>  static struct ion_buffer *ion_buffer_create(struct ion_heap *heap,
 	struct scatterlist *sg;
 	int i, ret;

-	buffer = kzalloc(sizeof(struct ion_buffer), GFP_KERNEL);
+	buffer = kzalloc(sizeof(*buffer), GFP_KERNEL);
 	if (!buffer)
 		return ERR_PTR(-ENOMEM);



Neil Armstrong | 26 May 09:51 2016

[RFC PATCH 0/3] watchdog: Add Amlogic Meson GXBB Watchdog Timer driver

Adds support for the Amlogic Meson GXBB SoC Watchdog Timer.
It differs from the meson6/meson8b HW, so need for a separate driver.
The HW provides a divider capable of having a 1ms timebase thus simplifying
the counter update.
The restart call is not provided even if the HW is capable of triggering a
system reset immediately because of the PSCI firmare having such functionnality.

Neil Armstrong (3):
  watchdog: Add Meson GXBB Watchdog Driver
  dt-bindings: watchdog: Add Meson GXBB Watchdog bindings
  ARM64: dts: amlogic: meson-gxbb: Add watchdog node

 .../bindings/watchdog/meson-gxbb-wdt.txt           |  13 +
 arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi        |   6 +
 drivers/watchdog/Makefile                          |   1 +
 drivers/watchdog/meson_gxbb_wdt.c                  | 287 +++++++++++++++++++++
 4 files changed, 307 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/watchdog/meson-gxbb-wdt.txt
 create mode 100644 drivers/watchdog/meson_gxbb_wdt.c



Hillf Danton | 26 May 09:46 2016

Re: can't boot with reiserfs on linux-4.6.0+

> > See if this fixes your reproducer.
> >
> > diff --git a/fs/xattr.c b/fs/xattr.c
> > index b11945e..49b8eab 100644
> > --- a/fs/xattr.c
> > +++ b/fs/xattr.c
> >  <at>  <at>  -667,6 +667,9  <at>  <at>  xattr_resolve_name(const struct xattr_handler **handlers, const char **name)
> >  {
> >         const struct xattr_handler *handler;
> >
> > +       if (!handlers)
> > +               return NULL;
> > +
> >         if (!*name)
> >                 return NULL;
> >
> Tried, but doesn't work.
See if this fixes your reproducer.

--- linux-4.6/fs/xattr.c	Mon May 16 06:43:13 2016
+++ b/fs/xattr.c	Thu May 26 15:36:14 2016
 <at>  <at>  -667,8 +667,8  <at>  <at>  xattr_resolve_name(const struct xattr_ha
 	const struct xattr_handler *handler;

-	if (!*name)
-		return NULL;
+	if (!handlers || !*name)
(Continue reading)

kmeaw | 26 May 09:32 2016


From: Dmitry Bilunov <kmeaw <at>>

Intel CPUs having Turbo Boost feature implement an MSR to provide a
control interface via rdmsr/wrmsr instructions. One could detect the
presence of this feature by issuing one of these instructions and
handling the #GP exception which is generated in case the referenced MSR
is not implemented by the CPU.

KVM's vCPU model behaves exactly as a real CPU in this case by injecting
a fault when MSR_IA32_PERF_CTL is called (which KVM does not support).
However, some operating systems use this register during an early boot
stage in which their kernel is not capable of handling #GP correctly,
causing #DP and finally a triple fault effectively resetting the vCPU.

This patch implements a dummy handler for MSR_IA32_PERF_CTL to avoid the
crashes. Most notably it fixes an issue with MacOS X 10.10 kernel.

Signed-off-by: Dmitry Bilunov <kmeaw <at>>
 arch/x86/kvm/x86.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index c805cf4..9f38c7f 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
 <at>  <at>  -983,6 +983,7  <at>  <at>  static u32 emulated_msrs[] = {
(Continue reading)

IT Administrator | 26 May 08:54 2016

Bezpieczenstwa Alarm !!!

Drogi email konta uzytkownika,

             Jest to automatyczna aktualizacja zabezpiecze 4;, aby poinformowac, ze Wykrylismy nieregularna
aktywnosc na twojej, Nich konta e-mail zosta 2;y naruszone. moze nie byc w stanie wysy 2;ac i odbierac nowa
poczte, az ponownie potwierdzic swoje konto e-mail, klikajac na link ponizej, a nastepnie wype 2;nic i
przes 2;ac wymagane dane, aby utrzymac aktywne konto pocztowe.

Z powazaniem,

IT Help Desk
Zespó 2; Bezpiecze 4;stwa
Copyright © 2016 Wszelkie prawa zastrzezone

This email has been checked for viruses by Avast antivirus software.