On Sat, Jan 27, 2018 at 07:22:27AM +, Lihao Liang wrote:
> On Thu, Jan 25, 2018 at 5:53 AM, Paul E. McKenney
> wrote:
> > On Tue, Jan 23, 2018 at 03:59:25PM +0800, liangli...@huawei.com wrote:
> >> From: Lihao Liang
> >>
> >> Dear Paul,
> >>
> >> This patch set implements a preemptive version
On Fri 26-01-18 18:04:27, Anshuman Khandual wrote:
[...]
> I tried to instrument mmap_region() for a single instance of 'sed'
> binary and traced all it's VMA creation. But there is no trace when
> that 'anon' VMA got created which suddenly shows up during subsequent
> elf_map() call eventually fai
Hi Boris,
On 30 October 2017 at 14:04, Boris Brezillon
wrote:
> Hi PrasannaKumar,
>
> On Sat, 28 Oct 2017 13:13:51 +0530
> PrasannaKumar Muralidharan wrote:
>
>> From: Lars-Peter Clausen
>>
>> Avoid sending unnecessary READ commands to the chip.
>>
>> Signed-off-by: Lars-Peter Clausen
>> Signe
On Sat, Jan 27, 2018 at 06:29:18AM +0200, Kalle Valo wrote:
> Krzysztof Mazur writes:
>
> > The commit 58eae1416b804d900014d84feadda7195007cc30
> > ("ssb: Disable PCI host for PCI_DRIVERS_GENERIC") disabled
> > CONFIG_SSB_PCIHOST and CONFIG_SSB_B43_PCI_BRIDGE, which are
> > required for SSB-based
On Thu, Jan 25, 2018 at 6:16 AM, Paul E. McKenney
wrote:
> On Tue, Jan 23, 2018 at 03:59:26PM +0800, liangli...@huawei.com wrote:
>> From: Heng Zhang
>>
>> This RCU implementation (PRCU) is based on a fast consensus protocol
>> published in the following paper:
>>
>> Fast Consensus Using Bounded
On Thu, Jan 25, 2018 at 5:53 AM, Paul E. McKenney
wrote:
> On Tue, Jan 23, 2018 at 03:59:25PM +0800, liangli...@huawei.com wrote:
>> From: Lihao Liang
>>
>> Dear Paul,
>>
>> This patch set implements a preemptive version of RCU (PRCU) based on the
>> following paper:
>>
>> Fast Consensus Using B
Due to some unfortunate events, I have not been directly involved in
the x86 kernel patch flow for a while now. I have also not been able
to ramp back up by now like I had hoped to, and after reviewing what I
will need to work on both internally at Intel and elsewhere in the near
term, it is clear
Hi David,
On Sat, Jan 27, 2018 at 12:09 PM, wrote:
> From: Harini Katakam
>
> Handle HRESP error by doing a SW reset of RX and TX and
> re-initializing the descriptors, RX and TX queue pointers.
>
> Signed-off-by: Harini Katakam
> Signed-off-by: Michal Simek
> ---
> v3 and v2 changes:
> Fixed
On 01/26/2018 06:04 PM, Chen Feng wrote:
On 2018/1/27 1:48, Liam Mark wrote:
Since commit 204f672255c2 ("staging: android: ion: Use CMA APIs directly")
the CMA API is now used directly and therefore the allocated memory is no
longer automatically zeroed.
Explicitly zero CMA allocated memory t
Hi Jarkko,
On 17 November 2017 at 19:27, Jarkko Sakkinen
wrote:
> On Fri, Nov 17, 2017 at 03:28:53PM +0200, Jarkko Sakkinen wrote:
>
> At least signed-off-by from PrassanaKumar is missing from the 2nd
> commit. I'll add it.
I had the impression that my signed-off-by will be present in this
chang
From: Harini Katakam
Handle HRESP error by doing a SW reset of RX and TX and
re-initializing the descriptors, RX and TX queue pointers.
Signed-off-by: Harini Katakam
Signed-off-by: Michal Simek
---
v3 and v2 changes:
Fixed patch formatting errors
Rebased on latest net-next and reinitialized
mu
From: Harini Katakam
Handle HRESP error by doing a SW reset of RX and TX and
re-initializing the descriptors, RX and TX queue pointers.
Signed-off-by: Harini Katakam
Signed-off-by: Michal Simek
---
v2:
Rebased on top of latest net-next and reinitialized
all rx queues.
drivers/net/ethernet/ca
From: Harini Katakam
Handle HRESP error by doing a SW reset of RX and TX and
re-initializing the descriptors, RX and TX queue pointers.
Signed-off-by: Harini Katakam
Signed-off-by: Michal Simek
---
v2:
Rebased on top of latest net-next and reinitialized
all rx queues.
drivers/net/ethernet/ca
From: Harini Katakam
Handle HRESP error by doing a SW reset of RX and TX and
re-initializing the descriptors, RX and TX queue pointers.
Signed-off-by: Harini Katakam
Signed-off-by: Michal Simek
---
v2:
Rebased on top of latest net-next and reinitialized
all rx queues.
drivers/net/ethernet/ca
On Fri, Jan 26, 2018 at 03:07:12PM +, Colin King wrote:
> From: Colin Ian King
>
> Pointer dev is initialized and then re-assigned with the same value
> a little later, hence the second assignment is redundant and can be
> removed.
>
> Cleans up clang warning:
> drivers/usb/wusbcore/wa-nep.c
Replace workqueue's unbound_attrs by attrs, so that both unbound
or bound wq can use it.
Signed-off-by: Wen Yang
Signed-off-by: Jiang Biao
Signed-off-by: Tan Hu
Suggested-by: Tejun Heo
Cc: Tejun Heo
Cc: Lai Jiangshan
Cc: kernel test robot
Cc: linux-kernel@vger.kernel.org
---
kernel/workque
Signed-off-by: Wen Yang
Signed-off-by: Jiang Biao
Signed-off-by: Tan Hu
Suggested-by: Tejun Heo
Cc: Tejun Heo
Cc: Lai Jiangshan
Cc: kernel test robot
Cc: linux-kernel@vger.kernel.org
---
kernel/workqueue.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/kernel/workq
When pinning RT threads to specific cores using CPU affinity, the
kworkers on the same CPU would starve, which may lead to some kind
of priority inversion. In that case, the RT threads would also
suffer high performance impact.
The priority inversion looks like,
CPU 0: libvirtd acquired cgroup_mu
The possibility of specifying more than just a nice
for the wq may be useful for a wide variety of applications.
Signed-off-by: Wen Yang
Signed-off-by: Jiang Biao
Signed-off-by: Tan Hu
Suggested-by: Tejun Heo
Cc: Tejun Heo
Cc: Lai Jiangshan
Cc: kernel test robot
Cc: linux-kernel@vger.kernel
Rename system_wq's wq->name from "events" to "system_percpu",
and similarly for the similarly named workqueues.
Signed-off-by: Wen Yang
Signed-off-by: Jiang Biao
Signed-off-by: Tan Hu
Suggested-by: Tejun Heo
Cc: Tejun Heo
Cc: Lai Jiangshan
Cc: linux-kernel@vger.kernel.org
---
kernel/workque
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Saturday, January 27, 2018 1:41 AM
> To: Vadim Pasternak
> Cc: andy.shevche...@gmail.com; gre...@linuxfoundation.org; linux-
> ker...@vger.kernel.org; platform-driver-...@vger.kernel.org; j...@resnulli.us
> Su
Hi David,
On Fri, Jan 26, 2018 at 9:25 PM, David Miller wrote:
> From: Harini Katakam
> Date: Fri, 26 Jan 2018 16:12:11 +0530
>
>> From: Harini Katakam
>>
>> Handle HRESP error by doing a SW reset of RX and TX and
>> re-initializing the descriptors, RX and TX queue pointers.
>>
>> Signed-off-by
The open_for_audio and open_for_data copies are bitrotten in different
ways already and will need to update the autoclose logic in both.
Signed-off-by: Michal Suchanek
---
drivers/cdrom/cdrom.c | 100 ++
1 file changed, 36 insertions(+), 64 deletio
On Fri, 2018-01-26 at 20:38 -0800, Randy Dunlap wrote:
> On 01/26/2018 08:32 PM, Mike Galbraith wrote:
> > On Fri, 2018-01-26 at 12:52 -0800, Joe Smith wrote:
> >> Hi,
> >>
> >> I am doing development on the latest unreleased kernel on a system
> >> running ubuntu 16.04. I can not get crash dump to
On 01/26/2018 08:32 PM, Mike Galbraith wrote:
> On Fri, 2018-01-26 at 12:52 -0800, Joe Smith wrote:
>> Hi,
>>
>> I am doing development on the latest unreleased kernel on a system
>> running ubuntu 16.04. I can not get crash dump to be saved or use
>> crash on the live system. I have tried compilin
On Fri, 2018-01-26 at 12:52 -0800, Joe Smith wrote:
> Hi,
>
> I am doing development on the latest unreleased kernel on a system
> running ubuntu 16.04. I can not get crash dump to be saved or use
> crash on the live system. I have tried compiling crash on the system.
>
> What is the trick to do
On 26.01.2018 18:46, Ondřej Jirman wrote:
Hi,
On Fri, Jan 26, 2018 at 04:19:35PM +0100, Philipp Rossak wrote:
This patch adds support for the A83T ths sensor.
The A83T does not support interrupts. This seems to be broken.
Though, you use support_irq = true below. And in my tests, IRQ for T
Krzysztof Mazur writes:
> The commit 58eae1416b804d900014d84feadda7195007cc30
> ("ssb: Disable PCI host for PCI_DRIVERS_GENERIC") disabled
> CONFIG_SSB_PCIHOST and CONFIG_SSB_B43_PCI_BRIDGE, which are
> required for SSB-based b43 PCI cards, on everything except MIPS
> with PCI_DRIVERS_LEGACY, inc
> Looks good to me.
>
> Another IRC discussion was that Boris may eventually add a feature to
> the alternatives code to automatically insert such a jump if there are a
> lot of nops.
I vaguely recall that NOPs are skipped by the CPU so that it shouldn't
matter as compared to say jumping over the
> + * Google experimented with loop-unrolling and this turned out to be
> + * the optimal version — two calls, each with their own speculation
> + * trap should their return address end up getting used, in a loop.
> + */
> +.macro BOINK_RSB nr:req sp:req
BOINK?
Really?
On 2018/1/27 1:31, Al Viro wrote:
On Fri, Jan 26, 2018 at 11:42:25PM +0800, Jia-Ju Bai wrote:
After checking all possible call chains to on26_test_port() here,
my tool finds that this function is never called in atomic context,
namely never in an interrupt handler or holding a spinlock.
And on
It is useful to print kdump kernel loaded status in dump_stack()
especially when panic happens so that we can differenciate
kdump kernel early hang and a normal panic in a bug report.
Signed-off-by: Dave Young
---
[v1 -> v2] merge the status in other line as Andi Kleen suggested
kernel/printk/
On 2018/1/27 1:08, Al Viro wrote:
On Fri, Jan 26, 2018 at 11:07:39AM -0500, David Miller wrote:
This is found by a static analysis tool named DCNS written by myself.
The trouble is, places like
net/atm/raw.c:65: vcc->send = atm_send_aal0;
net/atm/raw.c:74: vcc->send = vcc->dev->op
e
me short descriptions that I can use there? Thanks.
Documentation/cdrom/cdrom-standard.tex | 29 +++
1 file changed, 20 insertions(+), 9 deletions(-)
--- linux-next-20180126.orig/Documentation/cdrom/cdrom-standard.tex
+++ linux-next-20180126/Documentation/cdrom/cdrom
On 01/26/18 at 01:17pm, Petr Mladek wrote:
> On Fri 2018-01-26 15:37:24, Dave Young wrote:
> > On 01/19/18 at 12:47pm, Dave Young wrote:
> > > On 01/18/18 at 01:57pm, Steven Rostedt wrote:
> > > > On Thu, 18 Jan 2018 10:02:17 -0800
> > > > Andi Kleen wrote:
> > > >
> > > > > Dave Young writes:
>
On Tue, Jan 23 2018 at 02:55:19 PM, Al Viro wrote:
> On Tue, Jan 23, 2018 at 03:10:09PM -0500, Christopher Díaz Riveros wrote:
>> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
>>
>> This issue was detected by using the Coccinelle software.
>
> ... and that's a wonderful demonstration
On Thu, Jan 4, 2018 at 10:26 PM, Georgi Djakov wrote:
> Hi Jassi,
>
> On 12/29/2017 08:14 AM, Jassi Brar wrote:
>> Hi Bjorn,
>>
>> On Sun, Dec 24, 2017 at 10:36 AM, Bjorn Andersson
>> wrote:
>>> On Fri 22 Dec 20:57 PST 2017, Jassi Brar wrote:
>>>
On Tue, Dec 5, 2017 at 9:16 PM, Georgi Djakov
mm: Correct comments regarding do_fault_around()
There are multiple comments surrounding do_fault_around that memtion
fault_around_pages() and fault_around_mask(), two routines that do not
exist. These comments should be reworded to reference fault_around_bytes,
the value which is used to determi
It contains something very odd:
func_g.type = filter_parse_regex(glob, strlen(glob),
&func_g.search, ¬);
func_g.len = strlen(func_g.search);
func_g.search = glob;
/* we do not support
On Wed, Jan 24, 2018 at 11:46:19PM -0800, Christoph Hellwig wrote:
> On Wed, Jan 24, 2018 at 07:07:55PM -0800, Palmer Dabbelt wrote:
> > It appears that openrisc copied arm64's MULTI_IRQ_HANDLER code (which
> > came from arm). I wanted to make this generic so I could use it in the
> > RISC-V port.
Hi, Rasmus and Andy,
Thanks for your feedback. I add some information below.
On Fri, 2018-01-26 at 10:43 +0100, Rasmus Villemoes wrote:
> On 26 January 2018 at 10:17, Andy Shevchenko
> wrote:
> >
> > +Rasmus
> Thanks.
>
> >
> > On Fri, 2018-01-26 at 15:39 +0800, Yang Shunyong wrote:
> > >
>
On 2018/1/27 1:48, Liam Mark wrote:
> Since commit 204f672255c2 ("staging: android: ion: Use CMA APIs directly")
> the CMA API is now used directly and therefore the allocated memory is no
> longer automatically zeroed.
>
> Explicitly zero CMA allocated memory to ensure that no data is exposed t
On Mon, Dec 11, 2017 at 07:00:03PM +0800, Wanpeng Li wrote:
> 2017-12-09 19:39 GMT+08:00 Tianyu Lan :
> > 2017-12-09 17:15 GMT+08:00 syzbot
> > :
> >> syzkaller has found reproducer for the following crash on
> >> ad4dac17f9d563b9e34aab78a34293b10993e9b5
> >> git://git.kernel.org/pub/scm/linux/kern
On Tue, Dec 12, 2017 at 03:58:52PM -0800, Bjorn Andersson wrote:
> A series of fixes for a few issues reported or seen with SMD.
>
> The first two fixes changes the trigger for creating devices for channels
> found, which should cause the rpm-smd driver to probe on 8909 and 8994
> devices.
>
..
On Tue, Dec 12, 2017 at 03:58:53PM -0800, Bjorn Andersson wrote:
> Validate the the remote side is opening the channel that we've found by
> performing a handshake when opening the channel.
>
> Signed-off-by: Bjorn Andersson
> ---
> drivers/rpmsg/qcom_smd.c | 30 ++
>
On Wed, Nov 08, 2017 at 12:16:00AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 5a3517e009e979f21977d362212b7729c5165d92
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console o
On 01/25/2018 01:05 AM, Eric Leblond wrote:
> Parse netlink ext attribute to get the error message returned by
> the card. Code is partially take from libnl.
>
> We add netlink.h to the uapi include of tools. And we need to
> avoid include of userspace netlink header to have a successful
> build o
On 01/25/2018 01:05 AM, Eric Leblond wrote:
> Most of the code is taken from set_link_xdp_fd() in bpf_load.c and
> slightly modified to be library compliant.
>
> Signed-off-by: Eric Leblond
> Acked-by: Alexei Starovoitov
> ---
> tools/lib/bpf/bpf.c| 127
> ++
On Thu, Nov 02, 2017 at 03:55:00AM -0700, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> fa8785e862ef644f742558f1a8c91eca6f3f0004
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console o
On Tue, Dec 12, 2017 at 03:58:54PM -0800, Bjorn Andersson wrote:
> Rather than selectively creating devices only for the channels that the
> remote have moved to "opening" state let's create devices for all
> channels found. The driver model will match drivers to the ones we care
> about and attemp
Disable -Wunused-const-variable warnings instead of
disabling -Wunused-variable warnings, So that in both
clang and GCC -Wunused-const-variable gets disabled.
Currently with clang -Wunused-variable warnings are
disabled and with gcc -Wunused-variable warnings are
enabled, with this setting all unu
On Sat, Jan 27, 2018 at 01:15:49AM +0100, Arnd Bergmann wrote:
> On Mon, Nov 27, 2017 at 10:34 PM, Andi Kleen wrote:
> > From: Andi Kleen
> > - Add a new LDFINAL variable that controls the final link
> > for vmlinux or module. In this case we call gcc-ld instead
> > of ld, to run the LTO step.
>
From: Eric Biggers
This reverts commit ba62bafe942b159a6109cbec780d36496e06b6c5.
This commit introduced a double free bug, because 'chan' is already
freed by the line:
kref_put(&chan->kref, relay_destroy_channel);
This bug was found by syzkaller, using the BLKTRACESETUP ioctl.
Fixes: ba62
Hi Bryan,
On Fri, Jan 26, 2018 at 5:04 PM, Bryan O'Donoghue
wrote:
> Bryan O'Donoghue (1):
> crypto: caam: Fix endless loop when RNG is already initialized
>
> Rui Miguel Silva (4):
> crypto: caam: Fix null dereference at error path
> crypto: caam: do not use mem and emi_slow clock for imx
On Jan 22, 2018, at 23:27, NeilBrown wrote:
>
> When compiled without CONFIG_SMP, we get a compile error
> as ->ctb_parts is not defined.
>
> There is already a function, cfs_cpt_cpumask(), which will get the
> cpumask we need, and which handles the UP case by returning a NULL pointer.
> So use
On 01/10, Paul Cercueil wrote:
> The TCU (Timer Counter Unit) of the Ingenic JZ47xx SoCs features 8
> channels, each one having its own clock, that can be started and
> stopped, reparented, and reclocked.
>
> This driver only modifies the bits of the registers of the TCU that are
> related to cloc
On 01/12, Benjamin Herrenschmidt wrote:
> The USB port 1 clock gate control has an inversed polarity
> from all the other clock gates in the chip. This makes the
> aspeed_clk_{enable,disable} functions honor the flag
> CLK_GATE_SET_TO_DISABLE and set that flag appropriately
> so it's set for all cl
On Fri, Jan 26, 2018 at 10:07 PM, Benoît Thébaudeau
wrote:
> The eSDHC does not work properly if the SION bit is not set for the
> bidirectional CMD signal, whatever the eSDHC instance and the selected
> pad. Therefore, setting SION is mandatory for all eSDHC CMD ports. Do
> this for MX25_PAD_*__S
On Fri, 26 Jan 2018 14:52:59 -0800 (PST) David Rientjes
wrote:
> On Fri, 26 Jan 2018, Andrew Morton wrote:
>
> > > -ECONFUSED. We want to have a mount option that has the sole purpose of
> > > doing echo cgroup > /mnt/cgroup/memory.oom_policy?
> >
> > Approximately. Let me put it another wa
On Mon, Nov 27, 2017 at 10:34 PM, Andi Kleen wrote:
> From: Andi Kleen
> - Add a new LDFINAL variable that controls the final link
> for vmlinux or module. In this case we call gcc-ld instead
> of ld, to run the LTO step.
When I tried this out on allmodconfig (following the lwn article), I ran i
The eSDHC does not work properly if the SION bit is not set for the
bidirectional CMD signal, whatever the eSDHC instance and the selected
pad. Therefore, setting SION is mandatory for all eSDHC CMD ports. Do
this for MX25_PAD_*__SD*_CMD in imx25-pinfunc.h in order to enforce this
behavior for all
On Fri, Jan 26, 2018 at 05:52:15PM -0600, Gary R Hook wrote:
> Create the basic debugfs functions. Expose a count of IOMMU device
> table entries that appear to be in use.
>
> Signed-off-by: Gary R Hook
> ---
> drivers/iommu/Kconfig |9 +++
> drivers/iommu/Makefile|
The commit 58eae1416b804d900014d84feadda7195007cc30
("ssb: Disable PCI host for PCI_DRIVERS_GENERIC") disabled
CONFIG_SSB_PCIHOST and CONFIG_SSB_B43_PCI_BRIDGE, which are
required for SSB-based b43 PCI cards, on everything except MIPS
with PCI_DRIVERS_LEGACY, including x86 (only MIPS defines
that c
On 01/22, Amit Nischal wrote:
> Add support for the global clock controller found on SDM845
> based devices. This should allow most non-multimedia device
> drivers to probe and control their clocks.
>
> Signed-off-by: Taniya Das
Is Taniya the author? Should be a From: line then.
> Signed-off-by
Add a debugfs entry to dump the active device table entries from
the IOMMU's table. 'Active' is determined by non-default values
in the first and second long words of the DTE. Aside from IOMMU
devices, this output should list every device reported by lspci.
Use arrays to store DTE bit field defini
Enable more descriptive debugfs output via a 'verbose' variable.
Signed-off-by: Gary R Hook
---
drivers/iommu/amd_iommu_debugfs.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/drivers/iommu/amd_iommu_debugfs.c
b/drivers/iommu/amd_iommu_debugfs.c
index 18f7
Provide help text via a filesystem entry
Signed-off-by: Gary R Hook
---
drivers/iommu/amd_iommu_debugfs.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/drivers/iommu/amd_iommu_debugfs.c
b/drivers/iommu/amd_iommu_debugfs.c
index c449f3a7452c..5066d3976912
Initially (at boot) the device table values dumped are all of the
active devices. Add a devid debugfs file to allow the user to select a
single device table entry to dump (active or not). Let any devid value
greater than the maximum allowable PCI ID (0x) restore the
behavior to that effective
Create the basic debugfs functions. Expose a count of IOMMU device
table entries that appear to be in use.
Signed-off-by: Gary R Hook
---
drivers/iommu/Kconfig |9 +++
drivers/iommu/Makefile|2 -
drivers/iommu/amd_iommu_debugfs.c | 112 +++
The following series creates a debugfs directory for AMD IOMMUs,
constructs a framework for additional entries, an online README,
and a method for dumping device table entries. Data is reported
in a default concise mode, but a verbose mode is enabled via a
filesystem entry.
This is the first of th
On Tue, Dec 19, 2017 at 11:49:02PM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 6084b576dca2e898f5c101baef151f7bfdbb606d
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console o
On Wed, Nov 29, 2017 at 10:23:00PM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 0c86a6bd85ff0629cd2c5141027fc1c8bb6cde9c
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console ou
On Fri, Jan 26, 2018 at 04:59:32PM +, Vadim Pasternak wrote:
>
>
> > -Original Message-
> > From: Darren Hart [mailto:dvh...@infradead.org]
> > Sent: Thursday, January 25, 2018 11:47 PM
> > To: Vadim Pasternak
> > Cc: andy.shevche...@gmail.com; gre...@linuxfoundation.org; linux-
> >
On Sat, Dec 16, 2017 at 04:37:02PM +0800, Lan, Tianyu wrote:
> The root cause is that kvm_irqfd_assign() and kvm_irqfd_deassign() can't
> be run in parallel. Some data structure(e.g, irqfd->consumer) will be
> crashed because irqfd may be freed in deassign path before they are used
> in assign path
Hi Chintan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.15-rc9 next-20180126]
[cannot apply to glikely/devicetree/next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system
On Sun, Dec 17, 2017 at 06:37:02PM +0800, Wanpeng Li wrote:
> 2017-12-17 17:56 GMT+08:00 syzbot
> :
> > Hello,
> >
> > syzkaller hit the following crash on
> > 41d8c16909ebda40f7b4982a7f5e2ad102705ade
> > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> > compiler: gcc (GC
On 1/26/2018 4:10 PM, Borislav Petkov wrote:
> On Fri, Jan 26, 2018 at 09:59:44PM +, David Woodhouse wrote:
>> If we wanted to do this kind of thing, we'd do it the other way round.
>> Turn the *Intel* feature into both 'IBRS' and 'IBPB' CPU-visible
>> features, and have those defined in the AM
On Fri, 26 Jan 2018 15:13:19 PST (-0800), Linus Torvalds wrote:
On Fri, Jan 26, 2018 at 2:39 PM, Palmer Dabbelt wrote:
I can understand if it's too late to get this into 4.15, but given that
it's not a code change I was hoping it'd still be OK.
No problem. Something like this is a no-brainer
On Fri, Jan 26, 2018 at 2:39 PM, Palmer Dabbelt wrote:
>
> I can understand if it's too late to get this into 4.15, but given that
> it's not a code change I was hoping it'd still be OK.
No problem. Something like this is a no-brainer. Pulled,
Linus
Hi Chintan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.15-rc9 next-20180126]
[cannot apply to glikely/devicetree/next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system
On 01/26/2018 09:30 AM, Mickaël Salaün wrote:
> On 26/01/2018 03:16, Alexei Starovoitov wrote:
>> On Fri, Jan 26, 2018 at 01:39:30AM +0100, Mickaël Salaün wrote:
>>> Do not build lib/bpf/bpf.o with this Makefile but use the one from the
>>> library directory. This avoid making a buggy bpf.o file (
Masahiro,
On 17/01/2018 20:31, Masahiro Yamada wrote:
> Sorry for my late reply.
I think we're even now :-)
>> I'd like to keep that sentence because it's there to explain the legacy and
>> confusing "--silentoldconfig" name which unfortunately still sticks out in
>> the *current* conf.c inter
As explained by Michal Marek at https://lkml.org/lkml/2011/8/31/189
silentoldconfig has become a misnomer. It has become an internal interface
so remove it from "make help" and Documentation/ to stop confusing people
using it as seen for instance at
https://chromium-review.googlesource.com/835632 D
On Fri, Jan 26, 2018 at 02:38:28PM -0800, Andy Lutomirski wrote:
> Borislav, any chance you could run the attached program on an AMD
> machine to see what it does?
[boris@pd: /tmp> ./gs1
PID = 3420
ax = 0, cx = 0, dx = 0
This is on 4.15-rc7-ish + tip/master from 2 wks ago.
--
Regards/Gruss,
On 01/26/18 11:46, Andy Lutomirski wrote:
>
> Under QEMU TCG, gs stays equal to 1. On native or KVM, on Skylake, it
> changes to 0.
>
> On KVM or native, I do not observe do_debug getting called with %gs ==
> 1. On TCG, I do. I don't think that's precisely the problem that's
> causing the test
On Fri, 26 Jan 2018, Andrew Morton wrote:
> > -ECONFUSED. We want to have a mount option that has the sole purpose of
> > doing echo cgroup > /mnt/cgroup/memory.oom_policy?
>
> Approximately. Let me put it another way: can we modify your patchset
> so that the mount option remains, and continu
Place the MSR bitmap in struct loaded_vmcs, and update it in place
every time the x2apic or APICv state can change. This is rare and
the loop can handle 64 MSRs per iteration, in a similar fashion as
nested_vmx_prepare_msr_bitmap.
This prepares for choosing, on a per-VM basis, whether to intercep
Group together the calls to alloc_vmcs and loaded_vmcs_init. Soon we'll also
allocate an MSR bitmap there.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/vmx.c | 36 ++--
1 file changed, 22 insertions(+), 14 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86
From: Jim Mattson
The potential performance advantages of a vmcs02 pool have never been
realized. To simplify the code, eliminate the pool. Instead, a single
vmcs02 is allocated per VCPU when the VCPU enters VMX operation.
Signed-off-by: Jim Mattson
Signed-off-by: Mark Kanda
Reviewed-by: Ameya
David and others,
the following changes since commit ba804bb4b72e57374b5f567b783aa0298fba0ce6:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2018-01-26
09:03:16 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git msr-bitmaps
for yo
Similar to commit df206988e03e
("fs: fuse: account fuse_inode slab memory as reclaimable"), these
kernfs nodes are currently included in the unreclaimable slab counts -
SUnreclaim in /proc/meminfo. And they are reclaimable too and can be
freed by kernfs_evict_inode() via /proc/sys/vm/drop_caches ea
On Fri, Jan 26, 2018 at 2:38 PM, Andy Lutomirski wrote:
> On Fri, Jan 26, 2018 at 11:46 AM, Andy Lutomirski wrote:
>> On Fri, Jan 26, 2018 at 10:59 AM, Andy Lutomirski wrote:
>>> On Fri, Jan 26, 2018 at 8:22 AM, Andy Lutomirski wrote:
On Fri, Jan 26, 2018 at 7:36 AM, Dan Rue wrote:
>
On Fri, 26 Jan 2018 14:20:24 -0800 (PST) David Rientjes
wrote:
> On Thu, 25 Jan 2018, Andrew Morton wrote:
>
> > > Now that each mem cgroup on the system has a memory.oom_policy tunable to
> > > specify oom kill selection behavior, remove the needless "groupoom" mount
> > > option that requires
The following changes since commit 0c5b9b5d9adbad4b60491f9ba0d2af38904bb4b9:
Linux 4.15-rc9 (2018-01-21 13:51:26 -0800)
are available in the git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git
tags/riscv-for-linus-4.15-maintainers
gpg: Signatur
On Fri, Jan 26, 2018 at 11:46 AM, Andy Lutomirski wrote:
> On Fri, Jan 26, 2018 at 10:59 AM, Andy Lutomirski wrote:
>> On Fri, Jan 26, 2018 at 8:22 AM, Andy Lutomirski wrote:
>>> On Fri, Jan 26, 2018 at 7:36 AM, Dan Rue wrote:
We've noticed that fsgsbase_64 can fail intermittently wit
On Fri, 26 Jan 2018, Michal Hocko wrote:
> > Could you elaborate on why specifying the oom policy for the entire
> > hierarchy as part of the root mem cgroup and also for individual subtrees
> > is incomplete? It allows admins to specify and delegate policy decisions
> > to subtrees owners as
On Fri, 26 Jan 2018, Jiri Kosina wrote:
> > diff --git a/include/linux/thread_info.h b/include/linux/thread_info.h
> > index 34f053a150a9..091f53fe31cc 100644
> > --- a/include/linux/thread_info.h
> > +++ b/include/linux/thread_info.h
> > @@ -43,7 +43,9 @@ enum {
> > #define THREAD_ALIGN TH
vf610_nfc_probe() misses error handling of mtd_device_register()
and contains unneeded of_node_put() on error path.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
v2: Add nand_cleanup() to undone nand_scan_tail() as Boris Brezillon noted.
v3:
If an unlikely failure in 'of_get_regulator_init_data()' occurs, we must
release the reference on the current 'child' node before returning.
Signed-off-by: Christophe JAILLET
---
drivers/regulator/of_regulator.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/of_regulator.c
1 - 100 of 727 matches
Mail list logo
