On Fri, 19 Jul 2019 11:07:33 +0100
James Morse wrote:
> Hi!
>
> On 18/07/2019 06:43, Masami Hiramatsu wrote:
> > On arm64, if a nested kprobes hit, it can crash the kernel with below
> > error message.
> >
> > [ 152.118921] Unexpected kernel single-step exception at EL1
> >
> > This is becaus
From: lsh <410860...@qq.com>
Modification of leap seconds from 58 59 59 00 to 58 59 00 00
---
kernel/time/ntp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/ntp.c b/kernel/time/ntp.c
index 65eb796..7edae41 100644
--- a/kernel/time/ntp.c
+++ b/kernel/time/ntp.c
@
Add device-links to track functional dependencies between devices
after they are created (but before they are probed) by looking at
their common DT bindings like clocks, interconnects, etc.
Having functional dependencies automatically added before the devices
are probed, provides the following ben
A parent device can have child devices that it adds when it probes. But
this probing of the parent device can happen way after kernel init is done
-- for example, when the parent device's driver is loaded as a module.
In such cases, if the child devices depend on a supplier in the system, we
need
When devices are added, the bus might want to create device links to track
functional dependencies between supplier and consumer devices. This
tracking of supplier-consumer relationship allows optimizing device probe
order and tracking whether all consumers of a supplier are active. The
add_links b
Default busses also have devices created for them. But there's no point
in creating device links for them. It's especially wasteful as it'll
cause the traversal of the entire device tree and also spend a lot of
time checking and figuring out that creating those links isn't allowed.
So check for def
The driver core/bus adding supplier-consumer dependencies by default
enables functional dependencies to be tracked correctly even when the
consumer devices haven't had their drivers registered or loaded (if they
are modules).
However, when the bus incorrectly adds dependencies that it shouldn't
ha
When all the top level devices are populated from DT during kernel
init, the supplier devices could be added and probed before the
consumer devices are added and linked to the suppliers. To avoid the
sync_state() callback from being called prematurely, pause the
sync_state() callbacks before popula
This sync_state driver/bus callback is called once all the consumers
of a supplier have probed successfully.
This allows the supplier device's driver/bus to sync the supplier
device's state to the software state with the guarantee that all the
consumers are actively managing the resources provided
Add device-links after the devices are created (but before they are
probed) by looking at common DT bindings like clocks and
interconnects.
Automatically adding device-links for functional dependencies at the
framework level provides the following benefits:
- Optimizes device probe order and avoi
Syzbot reported global-out-of-bounds Read in dvb_pll_attach, while
accessing id[dvb_pll_devcount], because dvb_pll_devcount was 65,
that is more than size of 'id' which is DVB_PLL_MAX(64).
Fix would be to check if DVB_PLL_MAX devices are attached and if so return
NULL from dvb_pll_attach(). But th
Running stress-test test_2 in mtd-utils on ubi device, sometimes we can
get following oops message:
BUG: unable to handle page fault for address: 0140
#PF: supervisor read access in kernel mode
#PF: error_code(0x) - not-present page
PGD 280a067 P4D 280a067 PUD 0
Oops: 000
On Fri, Jul 19, 2019 at 08:52:20PM +0900, Greg Kroah-Hartman wrote:
> On Sat, Jul 06, 2019 at 10:39:38AM -0700, Dmitry Torokhov wrote:
> > On Sat, Jul 6, 2019 at 10:19 AM Greg Kroah-Hartman
> > wrote:
> > >
> > > On Sat, Jul 06, 2019 at 10:04:39AM -0700, Dmitry Torokhov wrote:
> > > > Hi Greg,
> >
Memory allocated by devm_ alloc will be freed upon device detachment. So
we may not require free memory.
Signed-off-by: Hariprasad Kelam
---
v2: correct the subject line
drivers/irqchip/irq-stm32-exti.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/irqchip/irq-stm32-exti.c b/driv
On 2019/07/19 5:27, Andy Lutomirski wrote:
> Hi all-
>
> I suspect that a bunch of the bugs you're all finding boil down to:
>
> - Nested debug exceptions could corrupt the outer exception's DR6.
> - Nested debug exceptions in which *both* exceptions came from the
> kernel were probably all k
Much like commit 18c9a99bce2a ("libata: zpodd: small read overflow in
eject_tray()"), this fixes a cdb[] buffer length, this time in
zpodd_get_mech_type():
We read from the cdb[] buffer in ata_exec_internal_sg(). It has to be
ATAPI_CDB_LEN (16) bytes long, but this buffer is only 12 bytes.
The KA
Hi.
I see several platform-data headers
that are not used in upstream.
For instance, please look at this driver:
drivers/leds/leds-netxbig.c
If I understood it correctly, this driver
supports both device tree and legacy board-file.
I grepped 'netxbig_led_platform_data', but
I only found the d
Hi Joe,
On Fri, 19 Jul 2019 20:09:19 -0700 Joe Perches wrote:
>
> On Sat, 2019-07-20 at 12:22 +1000, Stephen Rothwell wrote:
> > Hi Joe,
> >
> > On Fri, 19 Jul 2019 15:31:33 -0700 Joe Perches wrote:
> > > Use perl's m@@ match and not // comparisons to avoid
> > > an error using c90's // comme
On Sat, 2019-07-20 at 12:22 +1000, Stephen Rothwell wrote:
> Hi Joe,
>
> On Fri, 19 Jul 2019 15:31:33 -0700 Joe Perches wrote:
> > Use perl's m@@ match and not // comparisons to avoid
> > an error using c90's // comment style.
> >
> > Miscellanea:
> >
> > o Use normal tab indentation and alignm
Le vendredi 19 juillet 2019 à 14:45 +0900, Tomasz Figa a écrit :
> On Wed, Jul 17, 2019 at 9:18 PM Nicolas Dufresne wrote:
> > Hello,
> >
> > there is one little detail/proposal, see inline .
> >
> > Le lundi 03 juin 2019 à 13:28 +0200, Hans Verkuil a écrit :
> > > From: Tomasz Figa
> > >
> >
Hi maxime:
>-Original Message-
>From: Maxime Ripard [mailto:maxime.rip...@bootlin.com]
>Sent: Thursday, July 18, 2019 12:38 AM
>To: Zengtao (B)
>Cc: kis...@ti.com; Chen-Yu Tsai ; Paul Kocialkowski
>; Sakari Ailus ;
>linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org
>Subj
Saner handling of refcounts to mountpoints.
Transfer the counting reference from struct mount ->mnt_mountpoint
over to struct mountpoint ->m_dentry. That allows to get rid of
the convoluted games with ordering of mount shutdowns. The cost
is in teaching shrink_dcache_{parent,for_umount} t
On Sat, Jul 20, 2019 at 4:28 AM Eugeniy Paltsev
wrote:
>
> As of today we are able to pass custom flags to dtc compiler but not
> to dtc preprocessor.
> This ability is required for including some board-specific header files.
> It allows us to pass defined constants to dts without their duplicatio
When an unhandled data or prefetch abort occurs, the die() string
is empty resulting in backtrace messages similar to the following:
Internal error: : 1 [#1] PREEMPT SMP ARM
Replace the null string with the name of the abort handler in order
to provide more meaningful hints as to the caus
Hi Linus,
Please pull some more Kbuild updates.
Thanks!
The following changes since commit 9637d517347e80ee2fe1c5d8ce45ba1b88d8b5cd:
Merge tag 'for-linus-20190715' of git://git.kernel.dk/linux-block
(2019-07-15 21:20:52 -0700)
are available in the Git repository at:
git://git.kernel.org/p
On Sat, Jul 20, 2019 at 8:38 AM James Bottomley
wrote:
>
> This is the final round of mostly small fixes in our initial
> submit. It's mostly minor fixes and driver updates. The only change
> of note is adding a virt_boundary_mask to the SCSI host and host
> template to parametrise this for NVMe
While attempting to debug slub freelist pointer corruption bugs
caused by a module, I discovered that the kmem call_site addresses are
not at all user friendly for modules unless you manage to save a copy
of kallsyms for the running kernel beforehand.
So convert kmem call_site addresses to user fr
Hi Joe,
On Fri, 19 Jul 2019 15:31:33 -0700 Joe Perches wrote:
>
> Use perl's m@@ match and not // comparisons to avoid
> an error using c90's // comment style.
>
> Miscellanea:
>
> o Use normal tab indentation and alignment
>
> Link:
> http://lkml.kernel.org/r/5e4a8fa7901148fbcd77ab391e6dd0e6
Hi Joe,
On Fri, 19 Jul 2019 15:31:32 -0700 Joe Perches wrote:
>
> Add more types of lines that appear to be stack dumps that also include
> hex lines that might otherwise be interpreted as commit IDs.
>
> Link:
> http://lkml.kernel.org/r/ff00208289224f0ca4eaf4ff7c9c6e087dad0a63.ca...@perches.co
On 7/19/19 4:32 PM, Ralph Campbell wrote:
> When CONFIG_MIGRATE_VMA_HELPER is enabled, migrate_vma() calls
> migrate_vma_collect() which initializes a struct mm_walk but
> didn't initialize mm_walk.pud_entry. (Found by code inspection)
> Use a C structure initialization to make sure it is set to NU
Hello, my name is Rose,
I have a business proposal that will benefit us, it is a business
worth 3.5million USD, Kindly get back to us if your interested for
more details.
Regards
Rose
Compiling a kernel with both FAIR_GROUP_SCHED=n and RT_GROUP_SCHED=n
will generate a compiler warning,
kernel/sched/core.c: In function 'sched_init':
kernel/sched/core.c:5906:32: warning: variable 'ptr' set but not used
[-Wunused-but-set-variable]
unsigned long alloc_size = 0, ptr;
Almost all directory file patterns in MAINTAINERS end with a trailing /.
There are some directory file patterns that do not.
It'd be nice to update those without the trailing / properly.
Can you please run and apply this script after rc1 ?
$ git grep -h "^[FX]:" MAINTAINERS | \
cut -f2- | grep
On Sat, 2019-07-20 at 00:30 +0100, Al Viro wrote:
> On Sat, Jul 20, 2019 at 12:23:08AM +0100, Al Viro wrote:
> > On Fri, Jul 19, 2019 at 07:07:49PM -0400, Jeff Layton wrote:
> >
> > > Al pointed out on IRC that vfree should be callable under spinlock.
> >
> > Al had been near-terminally low on ca
The pull request you sent on Fri, 19 Jul 2019 16:54:31 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/armsoc-soc
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/24e44913aa746098349370a0f279733c0cadcba7
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 19 Jul 2019 16:54:32 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/armsoc-drivers
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8362fd64f07eaef7155c94fca8dee91c4f99a666
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 19 Jul 2019 16:54:34 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git
> tags/armsoc-defconfig
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/abdfd52a295fb5731ab07b5c9013e2e39f4d1cbe
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Fri, 19 Jul 2019 16:54:33 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/armsoc-dt
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/af6af87d7e4ff67324425daa699b9cda32e3161d
Thank you!
--
Deet-doot-dot, I am a bot.
You maybe wondering how i get into you but it's God's doing.
I have a top secret business proposal, $10 Million usd, to be transfer
into your bank account, if you are ready let me know so that i will
detail you for us to move forward.
Waiting to hear from you,
Thanks, Manager Mr. Juff Firti.
On Fri, Jul 19, 2019 at 4:54 PM Olof Johansson wrote:
>
> Various driver updates for platforms and a couple of the small driver
> subsystems we merge through our tree:
>
> - A driver for SCU (system control) on NXP i.MX8QXP
> - Qualcomm Always-on Subsystem messaging driver (AOSS QMP)
> - Qualcomm
Previously, using "%m" in a ksft_* format string can result in strange
output because the errno value wasn't saved before calling other libc
functions. The solution is to simply save and restore the errno before
we format the user-supplied format string.
Signed-off-by: Aleksa Sarai
---
tools/tes
We keep this in a separate branch to avoid cross-branch conflicts, but
most of the material here is fairly boring -- some new drivers turned on
for hardware since they were merged, and some refreshed files due to
time having moved a lot of entries around.
Merge conflicts:
arch/arm/configs/exynos_
SoC platform changes. Main theme this merge window:
- The Netx platform (Netx 100/500) platform is removed by Linus Walleij--
the SoC doesn't have active maintainers with hardware, and in
discussions with the vendor the agreement was that it's OK to remove.
- Russell King has a series of patches
Various driver updates for platforms and a couple of the small driver
subsystems we merge through our tree:
- A driver for SCU (system control) on NXP i.MX8QXP
- Qualcomm Always-on Subsystem messaging driver (AOSS QMP)
- Qualcomm PM support for MSM8998
- Support for a newer version of DRAM PHY dri
Squeaking in on the last few days of the merge window, here's the ARM
SoC contents for this merge window.
It's again another cycle of business-as-usual. We've seen a few new
SoCs, a handful of better supported boards (and new boards), and the
general tweaks, improvements and cleanups. Most of the
We continue to see a lot of new material. I've highlighted some of it
below, but there's been more beyond that as well.
One of the sweeping changes is that many boards have seen their ARM Mali
GPU devices added to device trees, since the DRM drivers have now been
merged.
So, with the caveat that
Hi Doug,
On Tue, Jul 16, 2019 at 09:42:09AM -0700, Doug Anderson wrote:
> As described in the patch ("mmc: core: Add sdio_trigger_replug()
> API"), the current mwifiex_sdio_card_reset() is broken in the cases
> where we're running Bluetooth on a second SDIO func on the same card
> as WiFi. The pr
This is the final round of mostly small fixes in our initial
submit. It's mostly minor fixes and driver updates. The only change
of note is adding a virt_boundary_mask to the SCSI host and host
template to parametrise this for NVMe devices instead of having them do
a call in slave_alloc. It's a
When CONFIG_MIGRATE_VMA_HELPER is enabled, migrate_vma() calls
migrate_vma_collect() which initializes a struct mm_walk but
didn't initialize mm_walk.pud_entry. (Found by code inspection)
Use a C structure initialization to make sure it is set to NULL.
Fixes: 8763cb45ab967 ("mm/migrate: new memory
On Sat, Jul 20, 2019 at 12:23:08AM +0100, Al Viro wrote:
> On Fri, Jul 19, 2019 at 07:07:49PM -0400, Jeff Layton wrote:
>
> > Al pointed out on IRC that vfree should be callable under spinlock.
>
> Al had been near-terminally low on caffeine at the time, posted
> a retraction a few minutes later
syzbot reported general protection fault in kstrtouint:
https://lkml.org/lkml/2019/7/18/328
>From the log, if the mount option is something like:
fd,
The default parameter (which has NULL param->string) will be
passed to vfs_parse_fs_param. Finally, this NULL param->string
On Fri, Jul 19, 2019 at 07:38:11PM +0200, Greg KH wrote:
> On Fri, Jul 19, 2019 at 08:43:29PM +0800, Yin Fengwei wrote:
> > syzbot reported general protection fault in kstrtouint:
> > https://lkml.org/lkml/2019/7/18/328
> >
> > >From the log, if the mount option is something like:
> >fd,XX
On Fri, Jul 19, 2019 at 03:37:37PM +0200, Dmitry Vyukov wrote:
> On Fri, Jul 19, 2019 at 2:44 PM Yin Fengwei wrote:
> >
> > syzbot reported general protection fault in kstrtouint:
> > https://lkml.org/lkml/2019/7/18/328
> >
> > From the log, if the mount option is something like:
> >fd,XXX
On Fri, Jul 19, 2019 at 07:07:49PM -0400, Jeff Layton wrote:
> Al pointed out on IRC that vfree should be callable under spinlock.
Al had been near-terminally low on caffeine at the time, posted
a retraction a few minutes later and went to grab some coffee...
> It
> only sleeps if !in_interrupt(
On Fri, 2019-07-19 at 15:32 +0100, Luis Henriques wrote:
> Calling ceph_buffer_put() in __ceph_setxattr() may end up freeing the
> i_xattrs.prealloc_blob buffer while holding the i_ceph_lock. This can be
> fixed by postponing the call until later, when the lock is released.
>
> The following back
> On Jul 19, 2019, at 3:44 PM, Joe Perches wrote:
>
> On Fri, 2019-07-19 at 18:41 +, Nadav Amit wrote:
>>> On Jul 19, 2019, at 11:36 AM, Dave Hansen wrote:
>>>
>>> On 7/18/19 5:58 PM, Nadav Amit wrote:
@@ -865,7 +893,7 @@ void arch_tlbbatch_flush(struct
arch_tlbflush_unmap_batch
On Sat, 20 Jul 2019, Thomas Gleixner wrote:
> On Fri, 19 Jul 2019, Sean Christopherson wrote:
> > On Tue, Jul 02, 2019 at 01:39:05PM -0400, Steven Rostedt wrote:
> >
> > I'm hitting a similar panic that bisects to commit
> >
> > a0d14b8909de ("x86/mm, tracing: Fix CR2 corruption")
> >
> > exc
On Wed, Jul 17, 2019 at 5:51 AM Alexandru Ardelean
wrote:
>
> This change adds device-tree bindings for the ADIS16460.
>
> Signed-off-by: Alexandru Ardelean
> ---
> .../bindings/iio/imu/adi,adis16460.yaml | 53 +++
> MAINTAINERS | 1 +
> 2
On Fri, 2019-07-19 at 18:41 +, Nadav Amit wrote:
> > On Jul 19, 2019, at 11:36 AM, Dave Hansen wrote:
> >
> > On 7/18/19 5:58 PM, Nadav Amit wrote:
> > > @@ -865,7 +893,7 @@ void arch_tlbbatch_flush(struct
> > > arch_tlbflush_unmap_batch *batch)
> > > if (cpumask_test_cpu(cpu, &batch->cpum
On Sat, Jul 20, 2019 at 12:45 AM Navid Emamdoost
wrote:
>
> pci_ioremap_bar may return null. This is eventually de-referenced at
> drivers/dma/dw/core.c:1154 and drivers/dma/dw/core.c:1168. A null check
> is needed to prevent null de-reference. I am adding the check and in case
> of failure. Than
On Sat, Jul 20, 2019 at 1:23 AM Navid Emamdoost
wrote:
>
> in lpss8250_dma_setup, we need to release the first dma slave object
> allocated in case of the second allocation failure.
>
This will bring a double free instead of fixing anything.
NAK.
> Signed-off-by: Navid Emamdoost
> ---
> drive
Hi!
> Without this, the following trace may be observed when a volume-break
> callback is received:
>
> INFO: trying to register non-static key.
> the code is fine but needs lockdep annotation.
I'm sure this fixes the warning...
> diff --git a/fs/afs/callback.c b/fs/afs/callback.c
> index 5
Use perl's m@@ match and not // comparisons to avoid
an error using c90's // comment style.
Miscellanea:
o Use normal tab indentation and alignment
Link:
http://lkml.kernel.org/r/5e4a8fa7901148fbcd77ab391e6dd0e6bf95777f.ca...@perches.com
Signed-off-by: Joe Perches
Signed-off-by: Andrew Morton
Add more types of lines that appear to be stack dumps that also include
hex lines that might otherwise be interpreted as commit IDs.
Link:
http://lkml.kernel.org/r/ff00208289224f0ca4eaf4ff7c9c6e087dad0a63.ca...@perches.com
Signed-off-by: Joe Perches
Signed-off-by: Andrew Morton
Signed-off-by:
> On 20 Jul 2019, at 1:21, Paolo Bonzini wrote:
>
> On 20/07/19 00:06, Liran Alon wrote:
>>
>>
>>> On 20 Jul 2019, at 0:39, Paolo Bonzini wrote:
>>>
>>> If a KVM guest is reset while running a nested guest, free_nested will
>>> disable the shadow VMCS execution control in the vmcs01. Howe
On Fri, 19 Jul 2019, Sean Christopherson wrote:
> On Tue, Jul 02, 2019 at 01:39:05PM -0400, Steven Rostedt wrote:
>
> I'm hitting a similar panic that bisects to commit
>
> a0d14b8909de ("x86/mm, tracing: Fix CR2 corruption")
>
> except I'm experiencing death immediately after starting init.
>
On 20/07/19 00:06, Liran Alon wrote:
>
>
>> On 20 Jul 2019, at 0:39, Paolo Bonzini wrote:
>>
>> If a KVM guest is reset while running a nested guest, free_nested will
>> disable the shadow VMCS execution control in the vmcs01. However,
>> on the next KVM_RUN vmx_vcpu_run would nevertheless try
> On 20 Jul 2019, at 0:39, Paolo Bonzini wrote:
>
> If a KVM guest is reset while running a nested guest, free_nested will
> disable the shadow VMCS execution control in the vmcs01. However,
> on the next KVM_RUN vmx_vcpu_run would nevertheless try to sync
> the VMCS12 to the shadow VMCS whic
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit f1a170cb3289a48df26cae3c60d77608f7a988bb ]
Drop the RT fixup, the futex code will be changed to avoid the need for
the workaround.
Signe
Dear RT Folks,
This is the RT stable review cycle of patch 4.19.59-rt24-rc1.
Please scream at me if I messed something up. Please test the patches too.
The -rc release will be uploaded to kernel.org and will be deleted when
the final release is out. This is just a review release (or release ca
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit c71273154c2ad12e1aada340ff30e826a11b ]
Rework of the hrtimer, timer and posix-timer cancelation interface
on -RT. Instead of the swai
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit c6c058c10577815a2491ce661876cff00a4c3b15 ]
On RT rcu_normal_after_boot is enabled by default.
Don't allow to disable it on RT because the
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit bbc4d2a7d6ff54ba923640d9a42c7bef7185fe98 ]
The backported stable commit
59c39840f5abf ("genirq: Prevent use-after-free and work list c
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 0532e87d9d44795221aa921ba7024bde689cc894 ]
Add kthread_schedule_work() which uses a global kthread for all its
jobs.
Split the cgroup inc
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 6a773b70cf105b46298ed3b44e77c102ce31d9ec ]
Drop the RT fixup, the futex code will be changed to avoid the need for
the workaround.
Signe
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
[ Upstream commit d7c7cf8cb68b7df17e6e50be1f25f35d83e686c7 ]
On -RT we can't invoke kfree() in a non-preemptible context.
Defer the deallocation of pi_state to pree
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit a71221d81cc4873891ae44f3aa02df596079b786 ]
Drop the RT fixup, the futex code will be changed to avoid the need for
the workaround.
Signe
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 761126efdcbe3fa3e99c9079fa0ad6eca2f251f2 ]
The caller holds a lock which already disables preemption.
Drop the preempt_disable_rt() state
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit f646521aadedab78801c9befe193e2e8a0c99298 ]
Since commit 1a1fb985f2e2b ("futex: Handle early deadlock return
correctly") we can deadlock w
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 9e0265c21af4d6388d47dcd5ce20f76ec3a2e468 ]
Drop the RT fixup, the futex code will be changed to avoid the need for
the workaround.
Signe
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Luis Claudio R. Goncalves"
[ Upstream commit 4e4cf4be79635e67144632d9135286381acbc95a ]
Zswap causes "BUG: scheduling while atomic" by blocking on a rt_spin_lock() with
preemption
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: kbuild test robot
[ Upstream commit 9462c69e29307adc95c289f50839d5d683973891 ]
drivers/pci/switch/switchtec.c:395:1-17: ERROR: switchtec_fops: .read() can
deadlock .write(); change
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 2122adbe011cdc0eb62ad62494e181005b23c76a ]
Joe Korty reported, that __irq_set_affinity_locked() schedules a
workqueue while holding a raw
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 40d0332ec8312e9c090f0a5414d9c90e12b13611 ]
The idle call back is invoked with disabled interrupts and requires
raw_spinlock_t locks to wo
4.19.59-rt24-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Steven Rostedt (VMware)"
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index 9a218ca23053..538297c53ccc
On Thu, 2019-07-18 at 16:29 -0700, David Miller wrote:
> From: Qian Cai
> Date: Thu, 18 Jul 2019 19:26:47 -0400
>
> >
> >
> >> On Jul 18, 2019, at 5:21 PM, Bill Wendling wrote:
> >>
> >> [My previous response was marked as spam...]
> >>
> >> Top-of-tree clang says that it's const:
> >>
> >>
On 7/19/19 12:29 PM, Ralph Campbell wrote:
> When a ZONE_DEVICE private page is freed, the page->mapping field can be
> set. If this page is reused as an anonymous page, the previous value can
> prevent the page from being inserted into the CPU's anon rmap table.
> For example, when migrating a pte
On 7/19/19 12:29 PM, Ralph Campbell wrote:
> Struct page for ZONE_DEVICE private pages uses the page->mapping and
> and page->index fields while the source anonymous pages are migrated to
> device private memory. This is so rmap_walk() can find the page when
> migrating the ZONE_DEVICE private page
On 19/07/19 22:41, Sean Christopherson wrote:
> Remove the kvm_rebooting check from VMX/SVM instruction exception fixup
> now that kvm_spurious_fault() conditions its BUG() on !kvm_rebooting.
> Because the 'cleanup_insn' functionally is also gone, deferring to
> kvm_spurious_fault() means __kvm_han
If a KVM guest is reset while running a nested guest, free_nested will
disable the shadow VMCS execution control in the vmcs01. However,
on the next KVM_RUN vmx_vcpu_run would nevertheless try to sync
the VMCS12 to the shadow VMCS which has since been freed.
This causes a vmptrld of a NULL pointe
On 19/07/19 23:01, Liran Alon wrote:
>
>
>> On 19 Jul 2019, at 19:42, Paolo Bonzini wrote:
>>
>> If a KVM guest is reset while running a nested guest, free_nested will
>> disable the shadow VMCS execution control in the vmcs01. However,
>> on the next KVM_RUN vmx_vcpu_run would nevertheless try
Thanks for doing this, it's something I've been hoping someone would do
for a long time.
While I kinda wish we had performance data for each individual patch (at
least the behavior-changing ones), this does look like a good
improvement. That might, for instance, tell is a bit about how the
separa
On 7/19/19 1:02 PM, Bharath Vedartham wrote:
> There have been issues with coordination of various subsystems using
> get_user_pages. These issues are better described in [1].
>
> An implementation of tracking get_user_pages is currently underway
> The implementation requires the use put_user_page
;
- ret = __phy_write(phydev, regnum, new);
+ __phy_write(phydev, regnum, new);
- return ret < 0 ? ret : 1;
+ return new != ret;
}
EXPORT_SYMBOL_GPL(__phy_modify_changed);
Took your patch on top of next-20190719.
See attached dmesg.
It didn't work. Same thing, lots
On Fri, 19 Jul 2019, Joerg Roedel wrote:
> On Thu, Jul 18, 2019 at 11:04:57AM +0200, Thomas Gleixner wrote:
> > Joerg,
> >
> > On Thu, 18 Jul 2019, Joerg Roedel wrote:
> > > On Wed, Jul 17, 2019 at 11:43:43PM +0200, Thomas Gleixner wrote:
> > > > On Wed, 17 Jul 2019, Joerg Roedel wrote:
> > > > >
Hi Zeng,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.2 next-20190719]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Zeng-Tao
On 7/19/19 1:59 PM, Matt Sickler wrote:
>> From: Bharath Vedartham
>> Changes since v2
>>- Added back PageResevered check as suggested by John Hubbard.
>>
>> The PageReserved check needs a closer look and is not worth messing
>> around with for now.
>>
>> Matt, Could you give any suggestio
Dear RT Folks,
I'm pleased to announce the 4.19.59-rt23 stable release.
This release is just an update to the new stable 4.19.59 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-r
> On 19 Jul 2019, at 19:42, Paolo Bonzini wrote:
>
> This is useful for debugging, and is ratelimited nowadays.
>
> Signed-off-by: Paolo Bonzini
Reviewed-by: Liran Alon
> ---
> arch/x86/kvm/vmx/vmx.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x8
> On 19 Jul 2019, at 19:42, Paolo Bonzini wrote:
>
> If a KVM guest is reset while running a nested guest, free_nested will
> disable the shadow VMCS execution control in the vmcs01. However,
> on the next KVM_RUN vmx_vcpu_run would nevertheless try to sync
> the VMCS12 to the shadow VMCS whi
1 - 100 of 520 matches
Mail list logo
