ext4_xattr_value_same() is used as a quick optimization in case the new
xattr value is identical to the previous value. When xattr value is
stored in a xattr inode the check becomes expensive so it is better to
just assume that they are not equal.
Signed-off-by: Tahsin Erdogan
---
fs/ext4/xattr.
On Tue, May 30, 2017 at 03:59:10PM -0700, Tyrel Datwyler wrote:
> On 05/30/2017 09:25 AM, Johan Hovold wrote:
> > The thermal child device reuses the parent MFD-device device-tree node
> > when registering a thermal zone, but did not take a reference to the
> > node.
> >
> > This leads to a refere
Two places in code missed converting xattr inode number using
le32_to_cpu().
Signed-off-by: Tahsin Erdogan
---
fs/ext4/xattr.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/fs/ext4/xattr.c b/fs/ext4/xattr.c
index 8e855fc2eb03..4dd8be16d175 100644
--- a/fs/ext4/xatt
Hi Stefan,
On 30/05/2017 19:41, Stefan Wahren wrote:
> Hi Phil,
>
>> Phil Elwell hat am 30. Mai 2017 um 18:28 geschrieben:
>>
>>
>> Restrict clock sources for the PCM peripheral to the oscillator and
>> PLLD_PER because other source may have varying rates or be switched off.
>
>> Prevent other
The ref count on ea_inode is incremented by
ext4_xattr_inode_orphan_add() which is supposed to be decremented by
ext4_xattr_inode_array_free(). The decrement is conditioned on whether
the ea_inode is currently on the orphan list. However, the orphan list
addition only happens when journaling is ena
ea_inode contents are treated as metadata, that's why it is journaled
during initial writes. Failing to call revoke during freeing could cause
user data to be overwritten with original ea_inode contents during journal
replay.
Signed-off-by: Tahsin Erdogan
---
fs/ext4/extents.c | 3 ++-
fs/ext4/
On 05/31/2017 03:23 PM, Jia-Ju Bai wrote:
The driver may sleep under a spin lock, and the function call path is:
journal_wait_for_write (acquire the lock by spin_lock)
closure_sync
schedule --> may sleep
To fix it, the lock is released before "closure_sync", and the lock is
acquired aga
In general, kernel functions indicate success/failure through their return
values. This function returns the status as an output parameter and reserves
the return value for the inode. Make it follow the general convention.
Signed-off-by: Tahsin Erdogan
---
fs/ext4/xattr.c | 73 ++
EXT4_XATTR_MAX_LARGE_EA_SIZE definition in ext4 is currently unused.
Besides, vfs enforces its own 64k limit which makes the 1MB limit in
ext4 redundant. Remove it.
Signed-off-by: Tahsin Erdogan
---
fs/ext4/ext4.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/fs/ext4/ext4.h b/fs/ext4/
In data=ordered mode jinode needs to be attached to the xattr inode when
writing data to it. Attachment normally occurs during file open for regular
files. Since we are not using file interface to write to the xattr inode,
the jinode attach needs to be done manually.
Otherwise the following crash
On Mon, May 29, 2017 at 11:39:47AM +0200, Vlastimil Babka wrote:
> Since commit 3bc48f96cf11 ("mm, page_alloc: split smallest stolen page in
> fallback") we pick the smallest (but sufficient) page of all that have been
> stolen from a pageblock of different migratetype. However, there are cases
>
Quota charging is based on the ownership of the inode. Currently, the
xattr inode owner is set to the caller which may be different from the
parent inode owner. This is inconsistent with how quota is charged for
xattr block and regular data block writes.
Signed-off-by: Tahsin Erdogan
---
fs/ext4
On Tue, May 30, 2017 at 04:35:37PM -0700, Joe Perches wrote:
> Using the extension saves a bit of code.
>
> Miscellanea:
>
> o Neaten and simplify dump_dp_payload_table
> o Removed trailing blank space from output
Not a huge fan of smashing random trivia into the same patch, but merged
anyway. %
We don't need acls on xattr inodes because they are not directly
accessible from user mode.
Besides lockdep complains about recursive locking of xattr_sem as seen
below.
=
[ INFO: possible recursive locking detected ]
4.11.0-rc8+ #402 Not tainted
From: Andreas Dilger
Large xattr support is implemented for EXT4_FEATURE_INCOMPAT_EA_INODE.
If the size of an xattr value is larger than will fit in a single
external block, then the xattr value will be saved into the body
of an external xattr inode.
The also helps support a larger number of xa
Hi Stefan,
On 30/05/2017 20:04, Stefan Wahren wrote:
> Hi Phil,
>
>> Phil Elwell hat am 30. Mai 2017 um 18:28 geschrieben:
>>
>>
>> Fractional clock dividers generate accurate average frequencies but
>> with jitter, particularly when the integer divisor is small.
>>
>> Introduce a new metric of
On Mon, May 29, 2017 at 3:33 AM, Johannes Berg
wrote:
> Hi Tejun,
>
> I suspect this is a long-standing bug introduced by all the pool rework
> you did at some point, but I don't really know nor can I figure out how
> to fix it right now. I guess it could possibly also be a lockdep issue,
> or an
On Wed, May 31, 2017 at 02:39:28AM +0200, Linus Walleij wrote:
> On Tue, May 30, 2017 at 6:25 PM, Johan Hovold wrote:
>
> > Commit ab78029ecc34 ("drivers/pinctrl: grab default handles from device
> > core") added automatic pin-control management to driver core by looking
> > up and setting any de
On 05/31/2017 01:37 PM, Boris Brezillon wrote:
Hi Archit,
Le Wed, 31 May 2017 13:31:16 +0530,
Archit Taneja a écrit :
Hi Boris,
On 05/31/2017 11:56 AM, Boris Brezillon wrote:
Hi Philippe,
Le Tue, 30 May 2017 16:55:42 +,
Philippe CORNU a écrit :
Hi Eric,
I took your patch for the
Hi,
> > #include
> > #include
> > #include
> > #include
> > #include
> >
> > DEFINE_MUTEX(mtx);
> > static struct workqueue_struct *wq;
> > static struct work_struct w1, w2;
> >
> > static void w1_wk(struct work_struct *w)
> > {
> > mutex_lock(&mtx);
> > msleep(100);
> >
e system]
>
> url:
> https://github.com/0day-ci/linux/commits/Johan-Hovold/driver-core-USB-thermal-fix-device-tree-node-reuse/20170531-043026
> base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
> usb-testing
> reproduce: make htmldocs
>
> All warning
On Tue, May 30, 2017 at 9:59 PM, Alexey Klimov wrote:
>
> I was able to come up with new version with only HR-timer spinlock in timer
> callback. That one seems a little bit better.
>
Yes, this is what I meant by simply using a lock. However the lock
around the last_tx_done() for all channels see
On Tue, 30 May 2017, Brian Norris wrote:
> Sorry to respond to myself. Thomas, your reply to another mail in this
> series helped me to notice:
>
> On Tue, May 30, 2017 at 04:19:58PM -0700, Brian Norris wrote:
> > Side note: for issues like the first problem above, I wonder why there
> > isn't a f
On Wed, May 31, 2017 at 2:09 PM, Balbir Singh wrote:
> On Wed, 24 May 2017 13:20:23 -0400
> Jérôme Glisse wrote:
>
>> Allow to unmap and restore special swap entry of un-addressable
>> ZONE_DEVICE memory.
>>
>> Changed since v1:
>> - s/device unaddressable/device private/
>>
>> Signed-off-by: J
On Tue, May 30, 2017 at 09:10:06PM +1000, Nicholas Piggin wrote:
> On Tue, 30 May 2017 16:20:55 +0530
> Gautham R Shenoy wrote:
>
> > On Tue, May 30, 2017 at 05:13:57PM +1000, Nicholas Piggin wrote:
> > > On Tue, 16 May 2017 14:19:48 +0530
> > > "Gautham R. Shenoy" wrote:
> > >
> > > > From:
On Tue, May 30, 2017 at 2:09 PM, Alan Cox wrote:
>> >> I'll think about possible solutions, but I have no prior experience
>> >> with the tty code. In the meantime syzkaller also hit a couple of
>> >> other fun tty/pty bugs including a write/ioctl race that results in
>> >> buffer overflow :-/
>
>
The driver may sleep under a spin lock, and the function call path is:
psbfb_2d_submit (acquire the lock by spin_lock_irqsave)
psb_2d_wait_available
psb_spank
msleep --> may sleep
To fix it, the "msleep" is replaced with "mdelay" in psb_spank.
Signed-off-by: Jia-Ju Bai
---
drivers/g
On Wed, 2017-05-31 at 10:36 +0200, Johannes Berg wrote:
>
> This was "ifndef", so it does in fact run here, just like you
> suggested. It doesn't warn though.
Also, even if DEADLOCK *is* defined, lockdep doesn't report anything.
johannes
On Tue, May 30, 2017 at 10:37:03AM -0500, Tom Lendacky wrote:
> I can define the command line option and the "on" and "off" values as
> character buffers in the function and initialize them on a per character
> basis (using a static string causes the same issues as referencing a
> string constant),
Hi,
On 23/02/2017 at 10:49:17 +0200, Claudiu Beznea wrote:
> Add pwm controller bindings for sam5d2_xplained
> and enable it.
>
> Changes since v1:
> - Correct the typo in patch subject.
>
> Signed-off-by: Claudiu Beznea
> ---
> arch/arm/boot/dts/at91-sama5d2_xplained_common.dtsi | 4
> a
Hi David,
I've noticed that the upstream patch:
https://github.com/torvalds/linux/commit/0ff50e83b5122e836ca492fefb11656b225ac29c
contains the KMSAN report and the repro, despite I've put them under
the triple dash (IIRC Eric told me I shouldn't bloat the patch
descriptions with that information).
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus
Fix regressions:
- missing CONFIG_EXPORTFS dependency
- failure if upper fs doesn't support xattr
- bad error cleanup
This also adds the concept of "impure" directories complementing
On Wed, 31 May 2017 10:16:50 +0200, Arnd Bergmann wrote:
> When devlink is configured as a loadable module, a built-in nfp driver
> causes a link error:
>
> drivers/net/built-in.o: In function `nfp_devlink_port_register':
> (.text+0xb8b05): undefined reference to `devlink_port_type_eth_set'
> driv
Hi,
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Benjamin
> Tissoires
> Subject: Re: [RFC PATCH v3 1/5] ACPI: button: Add indication of BIOS
> notification and faked events
>
> Hi Lv,
>
> On May 27 2017 or thereabouts, Lv Zheng wrote:
> > Th
On Wed, 2017-05-31 at 02:29 +, Chen, Xiaoguang wrote:
> Hi Gerd,
>
> It is based on 4.12.0-rc1
Applies, good.
But then fails to build:
error: ‘struct vfio_vgpu_dmabuf_info’ has no member named ‘resv’
gvt/kvmgt.c:611:11: note: in expansion of macro ‘offsetofend’
minsz = offsetofend(struct
On Tue, May 30, 2017 at 11:15:38PM +0200, Thomas Gleixner wrote:
> The only user of this facility is ptp_clock, which does not implement any of
> those functions.
>
> Remove them to prevent accidental users. Especially the interval timer
> interfaces are now more or less impossible to implement be
Hi,
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
> Subject: Re: [RFC PATCH v3 5/5] ACPI: button: Always notify kernel space
> using _LID returning value
>
> Hi Lv,
>
> On May 27 2017 or thereabouts, Lv Zheng wrote:
> > Both nouveau and i915, the only 2 kernel space lid noti
Am 31.05.2017 um 10:28 schrieb Phil Elwell:
> Hi Stefan,
>
> On 30/05/2017 19:41, Stefan Wahren wrote:
>> Hi Phil,
>>
>>> Phil Elwell hat am 30. Mai 2017 um 18:28 geschrieben:
>>>
>>>
>>> Restrict clock sources for the PCM peripheral to the oscillator and
>>> PLLD_PER because other source may have
On 31.05.2017 11:50, Alexandre Belloni wrote:
> Hi,
>
> On 23/02/2017 at 10:49:17 +0200, Claudiu Beznea wrote:
>> Add pwm controller bindings for sam5d2_xplained
>> and enable it.
>>
>> Changes since v1:
>> - Correct the typo in patch subject.
>>
>> Signed-off-by: Claudiu Beznea
>> ---
>> arch
Hi, Dmitry!
On 05/30/2017 07:37 PM, Dmitry Torokhov wrote:
On Tue, May 30, 2017 at 03:50:20PM +0300, Oleksandr Andrushchenko wrote:
Hi, Dmitry!
On 05/30/2017 08:51 AM, Dmitry Torokhov wrote:
On Fri, Apr 21, 2017 at 09:40:36AM +0300, Oleksandr Andrushchenko wrote:
Hi, Dmitry!
On 04/21/2017 0
Hi Gerd,
I found this problem once I sent the patches :(
I checked the uapi definitions and found it is usually called pad to do the
aligning. So I changed the 'resv' to 'pad' in the patch but forgot to update it
in the last patch and did not test after the "small" change. Next time I will
tes
On Tue, May 30, 2017 at 12:39:30PM +0200, Michal Hocko wrote:
> On Tue 30-05-17 13:19:22, Mike Rapoport wrote:
> > > > But then we'll have to populate these regions with
> > > > UFFDIO_COPY which adds quite an overhead.
> > >
> > > How big is the performance impact?
> >
> > I don't have the numbe
There is no link between the number of elements of tab which contains all
pin desc (located in each pinctrl-stm32.c files) and the pin number
(defined in the tab).
Signed-off-by: Alexandre TORGUE
diff --git a/drivers/pinctrl/stm32/pinctrl-stm32.c
b/drivers/pinctrl/stm32/pinctrl-stm32.c
inde
On Wed, May 31, 2017 at 08:51:28AM +0200, Michal Hocko wrote:
> On Wed 31-05-17 14:30:33, kernel test robot wrote:
> >
> > FYI, we noticed the following commit:
> >
> > commit: beeeccca9bebcec386cc31c250cff8a06cf27034 ("btrfs: Use kvzalloc
> > instead of kzalloc/vmalloc in alloc_bitmap")
> > htt
The driver may sleep under a write spin lock, and function call path is:
netxen_nic_hw_read_wx_2M (acquire the lock by write_lock_irqsave)
crb_win_lock
netxen_pcie_sem_lock
msleep --> may sleep
netxen_nic_hw_write_wx_2M (acquire the lock by write_lock_irqsave)
crb_win_lock
netxen_
On Tue, May 30, 2017 at 02:17:20PM -0400, Johannes Weiner wrote:
> To re-implement slab cache vs. page cache balancing, we'll need the
> slab counters at the lruvec level, which, ever since lru reclaim was
> moved from the zone to the node, is the intersection of the node, not
> the zone, and the m
On Tue, 30 May 2017 13:20:12 +0200
Arnd Bergmann wrote:
> An unknown change in the kernel headers caused a build regression
> in an MTD partition driver:
>
> In file included from drivers/mtd/bcm47xxpart.c:12:0:
> include/linux/bcm47xx_nvram.h: In function 'bcm47xx_nvram_init_from_mem':
> includ
Hello,
On Fri, 19 May 2017 18:04:42 +0200, Gregory CLEMENT wrote:
> Gregory CLEMENT (6):
> MAINTAINERS: extend mvebu SoC entry with pinctrl drivers
> pinctrl: dt-bindings: add documentation for AP806 pin controllers
> pinctrl: dt-bindings: add documentation for CP110 pin controllers
> pin
On Tue, May 30, 2017 at 10:48:27AM -0500, Tom Lendacky wrote:
> I'll look at doing that instead of removing the support for the whole
> file.
Right, so I don't think the stack protector is even ready that early -
we do set it up later:
/* Set up %gs.
*
* The base of %gs
Hello,
On Fri, 19 May 2017 18:09:19 +0200, Gregory CLEMENT wrote:
> Not that currently I didn't manage to fully test the gpio, indeed I
> only have a 7040 DB board which lack of test point for this kind of
> test. So any tested-by would be welcome.
I have tested GPIOs on the master CP110 of the
Fractional clock dividers generate accurate average frequencies but
with jitter, particularly when the integer divisor is small.
Introduce a new metric of clock accuracy to penalise clocks with a good
average but worse jitter compared to clocks with an average which is no
better but with lower jit
Restrict clock sources for the PCM peripheral to the oscillator and
PLLD_PER because other source may have varying rates or be switched off.
Prevent other sources from being selected by replacing their names in
the list of potential parents with dummy entries (entry index is
significant).
Signed-o
The switch to using the upstream bcm2835_cprman clock driver caused a
few problems for users of PCM (I2S) peripherals. Audio applications
require accurate, stable clocks, and the cprman driver wasn't
conservative enough in its choice of clock sources.
These patches restrict the clock sources for t
On Wed 31-05-17 02:12:02, Omar Sandoval wrote:
> On Wed, May 31, 2017 at 08:51:28AM +0200, Michal Hocko wrote:
> > On Wed 31-05-17 14:30:33, kernel test robot wrote:
> > >
> > > FYI, we noticed the following commit:
> > >
> > > commit: beeeccca9bebcec386cc31c250cff8a06cf27034 ("btrfs: Use kvzallo
The driver may sleep under a spin lock, and the function call path is:
netxen_nic_pci_mem_access_direct (acquire the lock by spin_lock)
ioremap --> may sleep
To fix it, the lock is released before "ioremap", and the lock is
acquired again after this function.
Signed-off-by: Jia-Ju Bai
---
dr
Am 31.05.2017 um 10:33 schrieb Phil Elwell:
> Hi Stefan,
>
> On 30/05/2017 20:04, Stefan Wahren wrote:
>> Hi Phil,
>>
>>> Phil Elwell hat am 30. Mai 2017 um 18:28 geschrieben:
>>>
>>>
>>> Fractional clock dividers generate accurate average frequencies but
>>> with jitter, particularly when the int
From: Jiada Wang
for SPI controllers on imx53 and later SoCs, there is HW issue when
work in slave mode, as new device type 'IMX53_ECSPI' has been added
for these SPI controllers which is compatible with 'fsl,imx53-ecspi'.
This patch updates DTS to make imx53 later SPI controller only be
compati
From: Jiada Wang
Changes in v2:
re-workd i.MX ECSPI controller slave mode support based on Geert's work
Jiada Wang (3):
spi: imx: add selection for iMX53 and iMX6 controller
ARM: dts: imx: change compatiblity for SPI controllers on imx53 later
soc
spi: imx: Add support for SPI Slave m
From: Jiada Wang
ECSPI contorller for iMX53 and iMX6 has few hardware issues
comparing to iMX51.
The change add possibility to detect which controller is used
to apply possible workaround and limitations.
Signed-off-by: Jiada Wang
---
.../devicetree/bindings/spi/fsl-imx-cspi.txt | 1 +
From: Jiada Wang
Previously i.MX SPI controller only works in Master mode.
This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI
controller to work also in Slave mode.
Currently SPI Slave mode support patch has the following limitations:
1. The stale data in RXFIFO will be dropped when the S
Hi Rafael,
On 14/05/2017 at 01:55:32 +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Commit eed4d47efe95 (ACPI / sleep: Ignore spurious SCI wakeups from
> suspend-to-idle) modified the core suspend-to-idle code to filter
> out spurious SCI interrupts received while suspended, which
Hi Stephen and Michael,
How many times do I need to push those patch get merged?
Regards,
Andy
-Original Message-
From: Andy Tang
Sent: Monday, April 17, 2017 9:37 AM
To: 'mturque...@baylibre.com' ; 'sb...@codeaurora.org'
Cc: 'robh...@kernel.org' ; 'mark.rutl...@arm.com'
; 'linux-...
On Tue, 30 May 2017, Brian Norris wrote:
> On Sat, May 27, 2017 at 10:16:37AM +0200, Thomas Gleixner wrote:
> > On Sat, 27 May 2017, jeffy wrote:
> > > for example when a driver(drivers/net/wireless/marvell/mwifiex/main.c)
> > > try to
> > > do these:
> > >
> > > devm_request_irq->irq_startup->ir
Add pwm controller bindings for sama5d2_xplained
and enable it.
Signed-off-by: Claudiu Beznea
---
Changes in v3:
- enable pwm in at91-sama5d2_xplained.dts file
Changes in v2:
- Correct the typo in patch subject.
arch/arm/boot/dts/at91-sama5d2_xplained.dts | 4
arch/arm/boot/dts/sama5d2.dt
Ard Biesheuvel wrote:
> - The series conflates 'UEFI secure boot support' with 'kernel lock
> down support'. I think this has been brought up before, but I really
> think we should have a cleaner separation between the feature (locking
> down various bits of the kernel if lockdown is in effect) f
On 31/05/2017 at 11:21:55 +0200, Alexandre Belloni wrote:
> Hi Rafael,
>
> On 14/05/2017 at 01:55:32 +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Commit eed4d47efe95 (ACPI / sleep: Ignore spurious SCI wakeups from
> > suspend-to-idle) modified the core suspend-to-idle code
Fixes the static checker warning in optee_release().
error: uninitialized symbol 'parg'.
Reported-by: Dan Carpenter
Signed-off-by: Jens Wiklander
---
drivers/tee/optee/core.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/tee/optee/core.c b/drivers/tee/o
On Wed, May 31, 2017 at 10:24:14AM +0200, Michal Hocko wrote:
> On Wed 31-05-17 08:30:08, Vlastimil Babka wrote:
> > On 05/30/2017 06:06 PM, Andrea Arcangeli wrote:
> > >
> > > I'm not sure if it should be considered a bug, the prctl is intended
> > > to use normally by wrappers so it looks optima
On Wed, May 31, 2017 at 11:19:05AM +0200, Michal Hocko wrote:
> On Wed 31-05-17 02:12:02, Omar Sandoval wrote:
> > On Wed, May 31, 2017 at 08:51:28AM +0200, Michal Hocko wrote:
> > > On Wed 31-05-17 14:30:33, kernel test robot wrote:
> > > >
> > > > FYI, we noticed the following commit:
> > > >
>
clk_prepare_enable() can fail here and we must check its return value.
Signed-off-by: Arvind Yadav
---
drivers/media/i2c/tc358743.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/media/i2c/tc358743.c b/drivers/media/i2c/tc358743.c
index acef4ec..0b30f7b 100644
-
On 05/31/2017 05:27 AM, Lu Baolu wrote:
> Hi,
>
> On 05/30/2017 09:46 PM, Vlastimil Babka wrote:
>> On 03/21/2017 09:01 AM, Lu Baolu wrote:
>>> XHCI debug capability (DbC) is an optional but standalone
>>> functionality provided by an xHCI host controller. Software
>>> learns this capability by wa
From: Rabin Vincent
There currently appears to be no way for userspace to find out the
underlying volume number for a mounted ubifs file system, since ubifs
uses anonymous block devices. The volume name is present in
/proc/mounts but UBI volumes can be renamed after the volume has been
mounted.
On Wed, May 24, 2017 at 11:00:51AM +0200, Vincent Guittot wrote:
> schedutil governor relies on cfs_rq's util_avg to choose the OPP when cfs
> tasks are running. When the CPU is overloaded by cfs and rt tasks, cfs tasks
> are preempted by rt tasks and in this case util_avg reflects the remaining
>
Instead of printing errors after mxs_i2c_pio_wait_xfer_end returns with
an error code just print a debug message.
NAKs and timeouts can occur in this situation normally, so do not treat
them as errors.
Signed-off-by: Michael Thalmeier
---
drivers/i2c/busses/i2c-mxs.c | 6 +++---
1 file changed,
This patch adds very useful debugging information to lid events.
These messages and with ec_log_drv() can be used to demonstrate the order
between acpi_ec_resume() and acpi_button_resume().
Cc: Benjamin Tissoires
Cc: Peter Hutterer
Signed-off-by: Lv Zheng
---
drivers/acpi/button.c | 5 +
1
This patch adds a parameter to acpi_lid_notify_state() so that it can act
differently against BIOS notification and kernel faked events.
Cc:
Cc: Benjamin Tissoires
Cc: Peter Hutterer
Signed-off-by: Lv Zheng
---
drivers/acpi/button.c | 14 --
1 file changed, 8 insertions(+), 6 dele
On Tue, May 30, 2017 at 11:00:04AM +0100, David Howells wrote:
> This isn't going to work. You've effectively changed the types of the fields
> in the UUID struct from BE to CPU-endian, but you're still calling
> generate_random_uuid(), which produces a BE UUID. You need to leave the
> struct mem
Surface Pro 3 is a typical platform where suspend/resume loop problem
can be seen.
The problem is due to a systemd 229 bug:
1. "ignore": always can trigger endless suspend/resume loop
2. "open": sometimes suspend/resume loop can be stopped
3. "method": always can trigger endless susped/resume loop
In acpi_lid_notify_state(), it now contains logic to avoid frequently
replayed events which originally was ensured by using blocking notifier.
On the contrary, using blocking notifier is wrong as it could keep on
returning NOTIFY_DONE, causing events lost.
This patch thus changes lid notification
Hi,
I've got the following error report while fuzzing the kernel with syzkaller.
On commit 5ed02dbb497422bf225783f46e6eadd237d23d6b (4.12-rc3).
Unfortunately it's not reproducible.
==
BUG: KASAN: use-after-free in ip6_dst_ifdown+0x
Both nouveau and i915, the only 2 kernel space lid notification listeners,
invoke acpi_lid_open() API to obtain _LID returning value instead of using
the notified value. So kernel graphics drivers are only interested in _LID
return value, hence this patch makes this logic explicit in button driver.
On Tue, May 30, 2017 at 10:08:15AM +0200, Johannes Thumshirn wrote:
> A patch for nvmetcli will follow shortly.
Thanks. No really required but nice would be a nvme-cli subcommand
to read the values as well.
On 5/30/2017 1:20 PM, Arnd Bergmann wrote:
An unknown change in the kernel headers caused a build regression
in an MTD partition driver:
In file included from drivers/mtd/bcm47xxpart.c:12:0:
include/linux/bcm47xx_nvram.h: In function 'bcm47xx_nvram_init_from_mem':
include/linux/bcm47xx_nvram.h:2
On Tue, May 30, 2017 at 11:48:09AM +0200, Johannes Thumshirn wrote:
> On 05/30/2017 11:24 AM, Christoph Hellwig wrote:
> > This should be stored as a uuid_t (or rather uuid_be in the current
> > kernel, but I'm about to rename it), and use uuid_be_to_bin / uuid_to_bin
> > for parsing.
>
> OK, thou
Hi,
I've got the following error report while fuzzing the kernel with syzkaller.
On commit 5ed02dbb497422bf225783f46e6eadd237d23d6b (4.12-rc3).
Unfortunately it's not reproducible.
==
BUG: KASAN: use-after-free in add_grec+0x101e/0
Commit-ID: 5b8b9cf76add98e19ff8ceb4247c2920687591a0
Gitweb: http://git.kernel.org/tip/5b8b9cf76add98e19ff8ceb4247c2920687591a0
Author: Arnd Bergmann
AuthorDate: Tue, 30 May 2017 11:14:17 +0200
Committer: Ingo Molnar
CommitDate: Wed, 31 May 2017 07:59:45 +0200
x86/KASLR: Use the right m
On Tue, May 30, 2017 at 11:45:25AM +0200, Johannes Thumshirn wrote:
> Mostly consistency. The current nvme host code has the EUI sprinkled all
> around. Sure I can drop it, but then what's the point in evaluating it
> on the host side? Other targets may send it, so we need in on the host
> and do w
On 05/31/17 02:59, Mikulas Patocka wrote:
>>> 2. use the PAT patch and revert the change to the function pat_ap_init
>>> - i.e. change it to the original:
>>> static void pat_ap_init(u64 pat)
>>> {
>>> if (!boot_cpu_has(X86_FEATURE_PAT)) {
>>
>> Joy.
>
> It is interesting - does it mean that t
Assembly in at91_lpddr_poweroff has r0 in the clobber list but uses r6.
Reported-by: Ben Hutchings
Signed-off-by: Alexandre Belloni
---
drivers/power/reset/at91-sama5d2_shdwc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/power/reset/at91-sama5d2_shdwc.c
b/driver
Assembly in at91_lpddr_poweroff has r0 in the clobber list but uses r6.
Reported-by: Ben Hutchings
Signed-off-by: Alexandre Belloni
---
drivers/power/reset/at91-poweroff.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/power/reset/at91-poweroff.c
b/drivers/power/re
On Tue, 30 May 2017 23:29:10 +0900
Tetsuo Handa wrote:
> James Morris wrote:
> > On Sun, 28 May 2017, Tetsuo Handa wrote:
> >
> > > can afford enabling". And we know that we cannot merge all
> > > security modules into mainline. Thus, allowing LKM-based LSM
> > > modules is inevitable.
> >
On Tue, May 30, 2017 at 11:39:07AM -0500, Tom Lendacky wrote:
> Yes, it's from objtool:
>
> arch/x86/mm/mem_encrypt_boot.o: warning: objtool: .text+0xd2: return
> instruction outside of a callable function
Oh, well, let's make it a global symbol then. Who knows, we might have
to live-patch it som
On Wed, May 31, 2017 at 10:48 AM, Jia-Ju Bai wrote:
> The driver may sleep under a spin lock, and the function call path is:
> psbfb_2d_submit (acquire the lock by spin_lock_irqsave)
> psb_2d_wait_available
> psb_spank
> msleep --> may sleep
>
> To fix it, the "msleep" is replaced with
On 05/30/2017 02:31 PM, Peter Zijlstra wrote:
> All I see is ugly that makes maintenance worse
s/maintenance/maintenance & development & understanding & .../
+1
-- Daniel
This patchset adds PMU driver for Cavium's ThunderX2 SoC UNCORE devices.
The SoC has PMU support in its L3 cache controller (L3C) and in the
DDR4 Memory Controller (DMC).
v2:
- rebased to 4.12-rc1
- Removed Arch VULCAN dependency
- update SMC call parameters as per latest firmware.
Documentation for the UNCORE PMUs on Cavium's ThunderX2 SoC.
The SoC has PMU support in its L3 cache controller (L3C) and in the
DDR4 Memory Controller (DMC).
Signed-off-by: Ganapatrao Kulkarni
---
Documentation/perf/thunderx2-pmu.txt | 60
1 file changed, 60
This patch adds a perf driver for the PMU UNCORE devices DDR4 Memory
Controller(DMC) and Level 3 Cache(L3C).
Signed-off-by: Ganapatrao Kulkarni
---
drivers/perf/Kconfig | 9 +
drivers/perf/Makefile| 1 +
drivers/perf/thunderx2_pmu.c | 968 +
On 31/05/2017 at 12:23:12 +0300, Claudiu Beznea wrote:
> Add pwm controller bindings for sama5d2_xplained
> and enable it.
>
> Signed-off-by: Claudiu Beznea
> ---
> Changes in v3:
> - enable pwm in at91-sama5d2_xplained.dts file
>
> Changes in v2:
> - Correct the typo in patch subject.
>
> arc
Hi Kishon,
On Tue, May 16, 2017 at 6:33 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Wednesday 10 May 2017 12:24 PM, Raviteja Garimella wrote:
>> This is driver for USB DRD Phy used in Broadcom's Northstar2
>> SoC. The phy can be configured to be in Device mode or Host
>> mode based on the type
On Tue, May 30, 2017 at 12:46:14PM -0500, Tom Lendacky wrote:
> This is an area that I'm not familiar with, so I don't completely
> understand the flow in regards to where/when/how the ELF headers are
> copied and what needs to be done.
So my suggestion is still to put kexec/kdump on the backburne
101 - 200 of 1025 matches
Mail list logo
