On Wed, 9 May 2018 18:11:20 +0300
Alexey Khoroshilov wrote:
> nxp_spifi_probe() increments refcnt of SPI flash device node by
> of_get_next_available_child() and leaves it undecremented on both
> successful and error paths.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
>
On Fri, Jul 06, 2018 at 05:37:49PM +0200, Greg Kroah-Hartman wrote:
> Someone else sent this same change before you did, sorry :(
Thanks for the review anyway. I realize now that I was looking at the wrong
tree.
From: Todd Poynor
Use the refcount_read accessor function, avoid reaching into refcount
and atomic struct fields.
Signed-off-by: Todd Poynor
---
drivers/staging/gasket/gasket_sysfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/gasket/gasket_sysfs.c
b/dr
This is a temporary patch which should not go to linux.git.
syzbot is hitting hung task problems at __sb_start_write() [1]. While hung
tasks at __sb_start_write() suggest that filesystem was frozen, syzbot is
not doing ioctl(FIFREEZE) requests. Therefore, the root cause of hung tasks
is currently
On Fri, Jul 06, 2018 at 05:21:00PM +0100, Mark Rutland wrote:
> Please don't open-code this. Use of_device_is_available(), which checks
> the status property itself. e.g.
>
> void __init setup_smp(void)
> {
> struct device_node *node = NULL;
>
> while ((node = of_find_node_by_type(nod
From: Tetsuo Handa
Since syzbot is confused by concurrent printk() messages [1],
this patch changes show_opcodes() to use snprintf().
When we start adding prefix to each line of printk() output,
we will be able to handle concurrent printk() messages.
[1] https://syzkaller.appspot.com/text?tag=C
The touchpads on both T25 and T480 are accessible over SMBUS/RMI.
Signed-off-by: kitsunyan
---
drivers/input/mouse/synaptics.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
index 55d33500d55e..be934a082424 100644
--- a/dri
On Fri, Jul 06, 2018 at 06:06:10PM -0400, Steven Rostedt wrote:
>
> Peter,
>
> Want to ack this? It touches Lockdep.
>
> Joel,
>
> I got to this patch and I'm still reviewing it. I'll hopefully have my
> full review done by next week. I'll make it a priority. But I still
> would like Peter's ac
On Fri, Jul 06, 2018 at 11:43:24AM -0600, dann frazier wrote:
> Hi,
> We're seeing a regression triggered by the stress-ng[*] "chdir" test
> that I've bisected to:
>
> 044e6e3d74a3 ext4: don't update checksum of new initialized bitmaps
>
> So far we've only seen failures on servers based on HiS
Dunlap
Cc: Azael Avalos
Cc: platform-driver-...@vger.kernel.org
Cc: Darren Hart
Cc: Andy Shevchenko
---
drivers/platform/x86/toshiba_acpi.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- linux-next-20180706.orig/drivers/platform/x86/toshiba_acpi.c
+++ linux-next-20180706/driver
>I strongly advocate for vendors to have more control over their drivers,
>but this scenario really frustrates me. I don't think I can justify this
>to Linus as a fix. But before we just say "no" (because hey, I want
>these fixes available as early as possible too), let's ask Rafael if he
>has an o
The first checks in mtdchar_read() and mtdchar_write() attempt to limit
`count` such that `*ppos + count <= mtd->size`. However, they ignore the
possibility of `*ppos > mtd->size`, allowing the calculation of `count` to
wrap around. `mtdchar_lseek()` prevents seeking beyond mtd->size, but the
pread
Hi,
Kindly pull the new firmware from the following URL.
git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
Thanks
Ganesh
The following changes since commit d1147327232ec4616a66ab898df84f9700c816c1:
Merge branch 'for-upstreaming-v1.7.2-vsw' of
https://github.com/felix-cavium/linux
ASAN
> CPU: 0 PID: 4429 Comm: syz-executor697 Not tainted 4.18.0-rc3-next-20180706+
> #1
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> RIP: 0010:shmem_undo_range+0xdaa/0x29a0 mm/shmem.c:815
Pretty sure this one's mine. At least I
From: Jun Gao
DMA mode will always be used in i2c transactions, try to allocate
a DMA safe buffer if the buf of struct i2c_msg used is not DMA safe.
Signed-off-by: Jun Gao
---
drivers/i2c/busses/i2c-mt65xx.c | 62 -
1 file changed, 55 insertions(+), 7 de
This patch series based on v4.18-rc1, include i2c adapter driver register time
modification, DMA safe buffer free function and DMA safe buffers used for i2c
transactions.
Jun Gao (3):
i2c: mediatek: Register i2c adapter driver earlier
i2c: Add helper to ease DMA handling
i2c: mediatek: Use D
Add support for the Zodiac Inflight Innovations SCU2 Mezz
board (i.MX51-based).
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicet...@vger.kernel.org
Cc: linux-kerne
From: Jun Gao
As i2c adapter, i2c slave devices will depend on it. In order not to
block the initializations of i2c slave devices, register i2c adapter
driver at appropriate time.
Signed-off-by: Jun Gao
---
drivers/i2c/busses/i2c-mt65xx.c | 12 +++-
1 file changed, 11 insertions(+), 1
From: Jun Gao
This function is needed by i2c_get_dma_safe_msg_buf() potentially.
It is used to free DMA safe buffer when DMA operation fails.
Signed-off-by: Jun Gao
---
drivers/i2c/i2c-core-base.c | 14 ++
include/linux/i2c.h | 1 +
2 files changed, 15 insertions(+)
diff
Relying on serial port defaults for flow control and parity can result
in complete breakdown of communication with RAVE SP on some platforms
where defaults are not what we need them to be. One such case is
VF610-base ZII SPU3 board (not supported upstream). To avoid this
problem in the future, add
RAVE SP firmware covered by "legacy" variant uses 16-bit CCITT
checksum algorithm. Change the code to correctly reflect that.
Cc: linux-kernel@vger.kernel.org
Cc: cphe...@gmail.com
Cc: Lucas Stach
Cc: Nikita Yushchenko
Cc: Lee Jones
Signed-off-by: Andrey Smirnov
---
drivers/mfd/rave-sp.c | 2
CMD_GET_STATUS is not supported by some devices implementing
RDU2-compatible ICD as well as "legacy" devices. To account for that
fact, add code that obtains the same information (app/bootloader FW
version) using several different commands.
Cc: linux-kernel@vger.kernel.org
Cc: cphe...@gmail.com
Cc
Lee:
This series is a number of small fixes the resulted from using RAVE SP
driver on wider selection of ZII devices that initial driver was
tested on. In addition to RDU1 and RDU2, the driver is now known to
work reasonably well on SCU2 Mezz (being upstreamed currently) as well
as SPU3 (not suppo
This is needed to make rave-sp-wdt driver to properly ping the
watchdog on "legacy" firmware.
Cc: linux-kernel@vger.kernel.org
Cc: cphe...@gmail.com
Cc: Lucas Stach
Cc: Nikita Yushchenko
Cc: Lee Jones
Signed-off-by: Andrey Smirnov
---
drivers/mfd/rave-sp.c | 2 ++
1 file changed, 2 insertions
Remove unusded defines that are a leftover from earlier iterations of
the driver.
Cc: linux-kernel@vger.kernel.org
Cc: cphe...@gmail.com
Cc: Lucas Stach
Cc: Nikita Yushchenko
Cc: Lee Jones
Signed-off-by: Andrey Smirnov
---
drivers/mfd/rave-sp.c | 10 --
1 file changed, 10 deletions(-)
This is needed to make rave-sp-eeprom driver work on "legacy"
firmware.
Cc: linux-kernel@vger.kernel.org
Cc: cphe...@gmail.com
Cc: Lucas Stach
Cc: Nikita Yushchenko
Cc: Lee Jones
Signed-off-by: Andrey Smirnov
---
drivers/mfd/rave-sp.c | 2 ++
include/linux/mfd/rave-sp.h | 1 +
2 files c
This read handler had a lot of custom logic and wrote outside the bounds of
the provided buffer. This could lead to kernel and userspace memory
corruption. Just use simple_read_from_buffer() with a stack buffer.
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Cc: sta...@vger.kernel.org
Signed-off-by: Jan
From: Xiubo Li
Prepraing for changing to use mutex lock.
Signed-off-by: Xiubo Li
---
drivers/uio/uio.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index e8f4ac9..b4b2ae1 100644
--- a/drivers/uio/uio.c
+++ b/drivers/uio/uio.c
@@
From: Xiubo Li
We are hitting a regression with the following commit:
commit a93e7b331568227500186a465fee3c2cb5dffd1f
Author: Hamish Martin
Date: Mon May 14 13:32:23 2018 +1200
uio: Prevent device destruction while fds are open
The problem is the addition of spin_lock_irqsave in uio_wri
From: Xiubo Li
For the target_core_user use case, after the device is unregistered
it maybe still opened in user space, then the kernel will crash, like:
[ 251.163692] BUG: unable to handle kernel NULL pointer dereference at
0008
[ 251.163820] IP: [] show_name+0x23/0x40 [uio]
[ 2
From: Xiubo Li
V2:
- resend it with some small fix
V3:
- switch to use request_threaded_irq
V4:
- remove useless checking code, Thanks Mike.
- Thanks very much for the review from Hamish and Mike.
Xiubo Li (3):
uio: use request_threaded_irq instead
uio: change to use the mutex lock instea
BPF_SYNCHRONIZE waits for any BPF programs active at the time of
BPF_SYNCHRONIZE to complete, allowing userspace to ensure atomicity of
RCU data structure operations with respect to active programs. For
example, userspace can update a map->map entry to point to a new map,
use BPF_SYNCHRONIZE to wai
If softsynthx_read() is called with `count < 3`, `count - 3` wraps, causing
the loop to copy as much data as available to the provided buffer. If
softsynthx_read() is invoked through sys_splice(), this causes an
unbounded kernel write; but even when userspace just reads from it
normally, a small si
On Sat, Jul 07, 2018 at 03:41:30AM +0200, Tomas Bortoli wrote:
> I don't have a background on usage or internals of the driver at issue
> but I hope these clues will help in finding the proper fix.
I think anything is useful, thanks..
The truth is that nobody is left that seems to really understa
On Thu, 2018-07-05 at 10:08 -0600, Rob Herring wrote:
>
> > It's not really a SOC block from a vendor, it's a pseudo-device in a
> > way. The current one that doesn't use the coldfire offload is just
> > compatible "fsi-master-gpio".
> >
> > I can add a vendor but what should it be ? aspeed becau
On 2018/7/7 2:58, Mike Christie wrote:
On 07/05/2018 09:57 PM, xiu...@redhat.com wrote:
void uio_event_notify(struct uio_info *info)
{
- struct uio_device *idev = info->uio_dev;
+ struct uio_device *idev;
+
+ if (!info)
+ return;
+
+ idev = info->uio_dev
Hi,
I spent some time debugging the Syzkaller's found issue at subject:
https://syzkaller.appspot.com/bug?id=b8febdb3c7c8c1f1b606fb903cee66b21b2fd02f
And I've backtracked the UAF to the fact that the cma_listen_on_all()
function adds "id_priv->list" to the global var "listen_any_list" but
then s
On 2018/7/7 2:23, Mike Christie wrote:
On 07/05/2018 09:57 PM, xiu...@redhat.com wrote:
static irqreturn_t uio_interrupt(int irq, void *dev_id)
{
struct uio_device *idev = (struct uio_device *)dev_id;
- irqreturn_t ret = idev->info->handler(irq, idev->info);
+ irqreturn_t
2018-07-07 1:29 GMT+09:00 Kirill A. Shutemov :
> On Fri, Jul 06, 2018 at 11:13:02PM +0900, Masahiro Yamada wrote:
>> >> LDFLAGS is for internal-use.
>> >> Please do not override it from the command line.
>> >
>> > Can we generate a build error if a user try to override LDFLAGS, CFLAGS or
>> > other
Hello,
syzbot found the following crash on:
HEAD commit:526674536360 Add linux-next specific files for 20180706
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=116d16fc40
kernel config: https://syzkaller.appspot.com/x/.config?x=c8d1cfc0cb798e48
Hi,
This is a follow up from
lkml.kernel.org/r/<20180329004805.7278-1-labb...@redhat.com> . I was
pointed to a previous suggestion (https://lkml.org/lkml/2018/2/28/178)
to rename the variables for better namespacing. I hadn't seen anyone
follow up so this is a series to do just that. I split up th
In preparation for enabling command line CFLAGS, re-name HOSTCFLAGS to
KBUILD_HOSTCFLAGS as the internal use only flags. This should not have any
visible effects.
Signed-off-by: Laura Abbott
---
Makefile | 4 ++--
arch/alpha/boot/Makefile | 2 +-
arch/s390/tools/Makefile
In preparation for enabling command line LDFLAGS, re-name HOSTLDFLAGS to
KBUILD_HOSTLDFLAGS as the internal use only flags. This should not have any
visible effects.
Signed-off-by: Laura Abbott
---
Makefile | 4 ++--
net/bpfilter/Makefile | 2 +-
scripts/Makefile.host | 10 ++
On 07/07, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2018/7/7 6:45, Jaegeuk Kim wrote:
> > On 07/04, Chao Yu wrote:
> >> From: Chao Yu
> >>
> >> Some devices has small max_{hw,}discard_sectors, so that in
> >> __blkdev_issue_discard(), one big size discard bio can be split
> >> into multiple small size
Commit 0c3b7e42616f ("tools build: Add support for host programs format")
introduced host_c_flags which referenced CHOSTFLAGS. The actual name of the
variable is HOSTCFLAGS. Fix this up.
Fixes: 0c3b7e42616f ("tools build: Add support for host programs format")
Signed-off-by: Laura Abbott
---
This
In preparation for enabling command line CXXFLAGS, re-name HOSTCXXFLAGS to
KBUILD_HOSTCXXFLAGS as the internal use only flags. This should not have any
visible effects.
Signed-off-by: Laura Abbott
---
Makefile | 4 ++--
scripts/Makefile.host| 4 ++--
scripts/kconfig/Makefil
Now that we have the rename in place, reuse the HOST*FLAGS options as
something that can be set from the command line and included with the
rest of the flags.
Signed-off-by: Laura Abbott
---
Makefile | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/Makefile b/Makefile
The final link of fixdep uses LDFLAGS but not the existing HOSTLDFLAGS.
Fix this.
Signed-off-by: Laura Abbott
---
This was another one where I couldn't tell of the use of LDFLAGS was a
typo or intentional, hence keeping both.
---
tools/build/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 del
In preparation for enabling command line LDLIBS, re-name HOST_LOADLIBES to
KBUILD_HOSTLDLIBS as the internal use only flags. This should not have any
visible effects.
Signed-off-by: Laura Abbott
---
Makefile | 4 ++--
samples/bpf/Makefile | 2 +-
scripts/Makefile.host | 10 +-
2018-07-06 23:39 GMT+09:00 Gabriel C :
> 2018-07-06 16:13 GMT+02:00 Masahiro Yamada :
>> Hi.
>>
>> 2018-07-06 19:41 GMT+09:00 Kirill A. Shutemov :
>>> On Fri, Jul 06, 2018 at 03:37:58PM +0900, Masahiro Yamada wrote:
>> > > Also see https://bugzilla.kernel.org/show_bug.cgi?id=200385 ,
>> >
This changes the behavior of the KASLR logic for allocating memory for the text
sections of loadable modules. It randomizes the location of each module text
section with about 17 bits of entropy in typical use. This is enabled on X86_64
only. For 32 bit, the behavior is unchanged.
The algorithm ev
Add debugfs file "modfraginfo" for providing info on module space
fragmentation. This can be used for determining if loadable module
randomization is causing any problems for extreme module loading situations,
like huge numbers of modules or extremely large modules.
Sample output when RANDOMIZE_B
Create __vmalloc_node_try_addr function that tries to allocate at a specific
address and supports caller specified behavior for whether any lazy purging
happens if there is a collision.
Signed-off-by: Rick Edgecombe
---
include/linux/vmalloc.h | 3 +
mm/vmalloc.c| 174 +
Hi,
This is v2 of the "KASLR feature to randomize each loadable module" patchset.
The purpose is to increase the randomization and makes the modules randomized
in relation to each other instead of just the base, so that if one module leaks,
the location of the others can't be inferred.
This code
On Tue, 19 Jun 2018 13:53:08 +0100 Will Deacon wrote:
> In preparation for implementing the asm-generic atomic bitops in terms
> of atomic_long_*, we need to prevent asm/atomic.h implementations from
> pulling in linux/bitops.h. A common reason for this include is for the
> BITS_PER_BYTE definiti
Add binding document for Stingray PCIe PHYs for both PAXB and PAXC based
root complex
Signed-off-by: Ray Jui
Reviewed-by: Rob Herring
---
.../devicetree/bindings/phy/brcm,sr-pcie-phy.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree
Add Stingray PCIe PHY driver for both PAXB and PAXC root complex
Signed-off-by: Ray Jui
---
drivers/phy/broadcom/Kconfig | 10 ++
drivers/phy/broadcom/Makefile | 2 +
drivers/phy/broadcom/phy-bcm-sr-pcie.c | 305 +
3 files changed, 317 insert
This patch series adds PCIe PHY support for both PAXB and PAXC root complex in
Broadcom Stingray SOC
This patch series is based off v4.18-rc3 and is available on GIHUB:
repo: https://github.com/Broadcom/arm64-linux.git
branch: sr-pcie-phy-v4
Changes since v3:
- Add missing node unit address in b
Note that the LZ4 signature is different than that of modern LZ4 as we
use the "legacy" format which suffers from some downsides like inability
to disable compression.
Signed-off-by: Adam Borowski
---
The first time this was sent I managed to screw up both the subject and
scissors line, so it's l
Hello!
Here is the updated scorecard:
e9ff68680cd4 tools/memory-model: Add litmus test for full multicopy atomicity
c21fcc6594f1 tools/memory-model: Fix ISA2+pooncelock+pooncelock+pombonce name
2f5a1b9b74a2 MAINTAINERS: Add Daniel Lustig as an LKMM reviewer
e1c071fab8e1 locking/memory-barriers.tx
On Fri, Jul 06, 2018 at 02:45:34PM -0700, Andrew Morton wrote:
> On Fri, 6 Jul 2018 16:36:41 +0100 Mark Rutland wrote:
>
> > > >
> > > > Acked-by: Matthew Wilcox
> > >
> > > Cheers!
> > >
> > > I assume that Andrew will pick this up, if he's also happy with it.
> >
> > I've just started fuzz
On Thu, 5 Jul 2018, Andrew Morton wrote:
> > +#ifdef CONFIG_DEBUG_FS
> > +static int oom_free_timeout_ms_read(void *data, u64 *val)
> > +{
> > + *val = oom_free_timeout_ms;
> > + return 0;
> > +}
> > +
> > +static int oom_free_timeout_ms_write(void *data, u64 val)
> > +{
> > + if (val > 60 *
On Mon, Jul 02, 2018 at 05:06:14PM +0300, Andy Shevchenko wrote:
> On Mon, Jul 2, 2018 at 4:51 PM, wrote:
>
> >> > So there are some customers who will have issue with power button
> >> > without this patch, so it should be also marked for stable also.
> >> > Also this may be a candidate for 4.1
On 7/5/2018 4:34 PM, Rob Herring wrote:
On Wed, Jul 04, 2018 at 11:22:12AM -0700, Ray Jui wrote:
Add binding document for Stingray PCIe PHYs for both PAXB and PAXC based
root complex
Signed-off-by: Ray Jui
---
.../devicetree/bindings/phy/brcm,sr-pcie-phy.txt | 41 ++
On Mon, Jun 18, 2018 at 11:05 PM, Dan Williams wrote:
> The routines hmm_devmem_add(), and hmm_devmem_add_resource() are
> now wrappers around the functionality provided by devm_memremap_pages() to
> inject a dev_pagemap instance and hook page-idle events. The
> devm_memremap_pages() interface is
Adding Tom and Boris
On 7/6/18 12:47 PM, Paolo Bonzini wrote:
> On 06/07/2018 18:13, Thomas Gleixner wrote:
>> To allow early utilization of kvmclock it is required to remove the
>> memblock dependency. memblock is currently used to allocate the per
>> cpu data for kvmclock.
>>
>> The first pat
Dirk Gouders writes:
> Masahiro Yamada writes:
>
>> syncconfig updates the .config only when sym_change_count > 0, i.e.
>> any change in config symbols has been detected.
>>
>> Not only symbols but also comments are contained in the .config file.
>> If only comments are updated, they are not fed
Quoting Gregory CLEMENT (2018-06-29 07:44:02)
> Hi,
>
> On mar., juin 19 2018, Gregory CLEMENT wrote:
>
> > Switching the CPU from the L2 or L3 frequencies (300 and 200 Mhz
> > respectively) to L0 frequency (1.2 Ghz) requires a significant amount
> > of time to let VDD stabilize to the appropr
Quoting Taniya Das (2018-07-04 23:55:20)
> diff --git a/Documentation/devicetree/bindings/clock/qcom,lpasscc.txt
> b/Documentation/devicetree/bindings/clock/qcom,lpasscc.txt
> new file mode 100644
> index 000..fe7378b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/qcom,lpasscc
Quoting Taniya Das (2018-07-04 23:55:21)
> diff --git a/drivers/clk/qcom/lpasscc-sdm845.c
> b/drivers/clk/qcom/lpasscc-sdm845.c
> new file mode 100644
> index 000..5285b26
> --- /dev/null
> +++ b/drivers/clk/qcom/lpasscc-sdm845.c
> @@ -0,0 +1,243 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
On Thu, 5 Jul 2018 16:13:40 -0600
Mathieu Poirier wrote:
> This set adds the capability to communiate event specific configuration
> to the PMU kernel driver using an ioctl(). The functionatlity is made
> generic enough for anyone to use but is targeted at the identification
> of CoreSight sink
I'm waiting for response from makedumpfile developers.
But makedumpfile is a tool for saving kernel crash dump.
If makedumpfile cannot work, we cannot use kernel crash dump.
On 2018/07/07 8:19, Kees Cook wrote:
> On Fri, Jul 6, 2018 at 9:11 AM, Linus Torvalds
> wrote:
>> On Fri, Jul 6, 2018 at 3
A few patches have landed for the qcom-qmp PHY that affect how you
would write a device tree node. ...yet the bindings weren't updated.
Let's remedy the situation and make the bindings refelect reality.
Fixes: efb05a50c956 ("phy: qcom-qmp: Add support for QMP V3 USB3 PHY")
Fixes: ac0d239936bd ("p
Hello Andrew,
It seems that syzbot (experimentally ?) restarted testing linux-next.
May I ask you to carry temporarily debug printk() patch at
https://groups.google.com/d/msg/syzkaller-bugs/E8M8WTqt034/OpadOICfCAAJ
for "INFO: task hung in __sb_start_write" case?
The bug should be reproduced with
On Thu, Jul 05, 2018 at 03:47:03PM -0500, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Signed-off-by: Gustavo A. R. Silva
> ---
> drivers/platform/x86/sony-laptop.c | 1 +
> 1 file changed, 1 inser
On Thu, 5 Jul 2018 16:13:42 -0600
Mathieu Poirier wrote:
Hi Mathieu,
> This patch adds the mechanic needed for user space to send PMU specific
I think you meant 'mechanism' here: mechanics fix cars :)
> +static void perf_drv_config_replace(struct perf_event *eve
On Fri, Jul 6, 2018 at 9:11 AM, Linus Torvalds
wrote:
> On Fri, Jul 6, 2018 at 3:07 AM Tetsuo Handa
> wrote:
>>
>> I noticed that makedumpfile utility is failing to check kernel version, for
>> it depends on offset of "struct uts_namespace"->name being sizeof(int).
>
> For something like this, we
On Thu, Jul 05, 2018 at 03:42:21PM -0500, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Warning level 2 was used: -Wimplicit-fallthrough=2
>
> Signed-off-by: Gustavo A. R. Silva
> ---
> drivers/pla
Hello Ken'ichi,
I noticed that makedumpfile ( https://sourceforge.net/p/makedumpfile/code/ )
can no longer detect kernel version correctly because "struct uts_namespace"
(which is exposed to userspace via vmcoreinfo) is subjected to randomization
by GCC_PLUGIN_RANDSTRUCT kernel config option since
On Sat, Dec 09, 2017 at 01:32:29PM -0800, Andy Lutomirski wrote:
> On Fri, Dec 8, 2017 at 7:41 PM, wrote:
> >>> On Dec 8, 2017, at 6:34 PM, Mario Limonciello
> >>> wrote:
> >>>
> >>> It's possible for the same GUID to show up on as system twice.
> >>> This means using solely the GUID for identi
On Thu, 5 Jul 2018 08:44:18 -0700 Kees Cook wrote:
> On Thu, Jul 5, 2018 at 7:55 AM, wrote:
> > From: Oscar Salvador
> >
> > The current code does not make sure to page align bss before calling
> > vm_brk(), and this can lead to a VM_BUG_ON() in __mm_populate()
> > due to the requested lenght
Hi Lorenzo,
On 7/6/2018 9:20 AM, Lorenzo Pieralisi wrote:
On Mon, Jun 11, 2018 at 05:21:02PM -0700, Ray Jui wrote:
This patch series improves the Broadcom PAXC support by 1) adding more
quirks for specific versions of PAXC controllers; 2) adding logic to
reject internally unconfigured physical
On Fri, 6 Jul 2018 17:01:09 +0800 Jia He wrote:
> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
> where possible") optimized the loop in memmap_init_zone(). But it causes
> possible panic bug. So Daniel Vacek reverted it later.
>
> But as suggested by Daniel Vacek, it
Hello,
syzbot found the following crash on:
HEAD commit:526674536360 Add linux-next specific files for 20180706
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12d51a2c40
kernel config: https://syzkaller.appspot.com/x/.config?x=c8d1cfc0cb798e48
Hello,
syzbot found the following crash on:
HEAD commit:526674536360 Add linux-next specific files for 20180706
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13e6a50c40
kernel config: https://syzkaller.appspot.com/x/.config?x=c8d1cfc0cb798e48
Hello,
syzbot found the following crash on:
HEAD commit:526674536360 Add linux-next specific files for 20180706
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1642b73440
kernel config: https://syzkaller.appspot.com/x/.config?x=c8d1cfc0cb798e48
On Fri, 6 Jul 2018 17:01:11 +0800 Jia He wrote:
> From: Jia He
>
> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
> where possible") optimized the loop in memmap_init_zone(). But it causes
> possible panic bug. So Daniel Vacek reverted it later.
>
> But as suggested b
On Thu, Jul 05, 2018 at 10:25:11PM +0530, Balakrishna Godavarthi wrote:
> Redefinition of qca_uart_setup will help future Qualcomm Bluetooth
> SoC, to use the same function instead of duplicating the function.
> Added new arguments soc_type and soc_ver to the functions.
>
> These arguments will he
On Fri, Jul 06, 2018 at 03:14:28PM -0700, Joe Perches wrote:
> On Fri, 2018-07-06 at 15:09 -0700, Joe Perches wrote:
> > On Fri, 2018-07-06 at 17:58 -0400, Don Zickus wrote:
> > > We have an internal use case of multiple MAINTAINER files, some folks have
> > > more rights to patches than others so
On Fri, Jul 06, 2018 at 03:14:28PM -0700, Joe Perches wrote:
> On Fri, 2018-07-06 at 15:09 -0700, Joe Perches wrote:
> > On Fri, 2018-07-06 at 17:58 -0400, Don Zickus wrote:
> > > We have an internal use case of multiple MAINTAINER files, some folks have
> > > more rights to patches than others so
On Thu, Jul 05, 2018 at 10:25:15PM +0530, Balakrishna Godavarthi wrote:
> Add support to set voltage/current of various regulators
> to power up/down Bluetooth chip wcn3990.
>
> Signed-off-by: Balakrishna Godavarthi
> ---
> changes in v9:
> * moved flow control to vendor and set_baudarte func
On Fri, 2018-07-06 at 15:09 -0700, Joe Perches wrote:
> On Fri, 2018-07-06 at 17:58 -0400, Don Zickus wrote:
> > We have an internal use case of multiple MAINTAINER files, some folks have
> > more rights to patches than others so they are not allowed to be cc'd (think
> > embargoed stuff).
How abo
On Fri, Jul 06, 2018 at 03:09:17PM -0700, Joe Perches wrote:
> On Fri, 2018-07-06 at 17:58 -0400, Don Zickus wrote:
> > On Fri, Jul 06, 2018 at 02:36:28PM -0700, Joe Perches wrote:
> > > > > > > Just trying to find ways to minimize our collection of private
> > > > > > > patches.
> > > > > >
> >
On Fri, 2018-07-06 at 17:58 -0400, Don Zickus wrote:
> On Fri, Jul 06, 2018 at 02:36:28PM -0700, Joe Perches wrote:
> > > > > > Just trying to find ways to minimize our collection of private
> > > > > > patches.
> > > > >
> > > > > Perhaps that could be extended for your purpose
> > > > > with so
Peter,
Want to ack this? It touches Lockdep.
Joel,
I got to this patch and I'm still reviewing it. I'll hopefully have my
full review done by next week. I'll make it a priority. But I still
would like Peter's ack on this one, as he's the maintainer of lockdep.
Thanks,
-- Steve
On Thu, 28 J
On Fri, 6 Jul 2018 17:39:22 -0400
Steven Rostedt wrote:
> On Fri, 6 Jul 2018 17:24:28 -0400
> Steven Rostedt wrote:
>
> > I'll investigate further.
>
> Note, I enabled function tracing to trace the scheduler function:
>
> # trace-cmd start -p function -l schedule
>
> And then ran cyclicte
Now that CPUs in lazy TLB mode no longer receive TLB shootdown IPIs, except
at page table freeing time, and idle CPUs will no longer get shootdown IPIs
for things like mprotect and madvise, we can always use lazy TLB mode.
Signed-off-by: Rik van Riel
Acked-by: Dave Hansen
Tested-by: Song Liu
--
Song noticed switch_mm_irqs_off taking a lot of CPU time in recent
kernels,using 1.8% of a 48 CPU system during a netperf to localhost run.
Digging into the profile, we noticed that cpumask_clear_cpu and
cpumask_set_cpu together take about half of the CPU time taken by
switch_mm_irqs_off.
However,
On Fri, Jul 06, 2018 at 02:36:28PM -0700, Joe Perches wrote:
> > > > > Just trying to find ways to minimize our collection of private
> > > > > patches.
> > > >
> > > > Perhaps that could be extended for your purpose
> > > > with some additional argument like a specific
> > > > optional directory
On Fri, 6 Jul 2018 10:44:58 +0100 Chris Wilson
wrote:
> net_dim.h has a rather useful extension to BITS_PER_BYTE to compute the
> number of bits in a type (BITS_PER_BYTE * sizeof(T)), so promote the
> macro to bitops.h, alongside BITS_PER_BYTE, for wider usage.
A bit of grepping shows that the
1 - 100 of 584 matches
Mail list logo
