On Tue, 2 Jul 2019 at 06:33, Nathan Chancellor wrote:
>
> Hi Joel,
>
> On Tue, Jul 02, 2019 at 02:07:05PM +0930, Joel Stanley wrote:
> > The subsystem was merged some time ago but we did not have a maintainers
> > entry.
> >
> > Signed-off-by: Joel Stanley
> > ---
> > MAINTAINERS | 13 ++
Commit-ID: 539bca535decb11a0861b6205c6684b8e908589b
Gitweb: https://git.kernel.org/tip/539bca535decb11a0861b6205c6684b8e908589b
Author: Andy Lutomirski
AuthorDate: Mon, 1 Jul 2019 20:43:21 -0700
Committer: Thomas Gleixner
CommitDate: Tue, 2 Jul 2019 08:45:20 +0200
x86/entry/64: Fix and
Commit-ID: dffb3f9db6b593f3ed6ab4c8d8f10e0aa6aa7a88
Gitweb: https://git.kernel.org/tip/dffb3f9db6b593f3ed6ab4c8d8f10e0aa6aa7a88
Author: Andy Lutomirski
AuthorDate: Mon, 1 Jul 2019 20:43:20 -0700
Committer: Thomas Gleixner
CommitDate: Tue, 2 Jul 2019 08:45:20 +0200
x86/entry/64: Don't c
Commit-ID: 9402eaf4c11f0b892eda7b2bcb4654ab34ce34f9
Gitweb: https://git.kernel.org/tip/9402eaf4c11f0b892eda7b2bcb4654ab34ce34f9
Author: Andy Lutomirski
AuthorDate: Mon, 1 Jul 2019 20:43:19 -0700
Committer: Thomas Gleixner
CommitDate: Tue, 2 Jul 2019 08:45:20 +0200
selftests/x86: Test S
On 01/07/2019 23:43, Martin Blumenstingl wrote:
> On Fri, Jun 28, 2019 at 6:05 PM Martin Blumenstingl
> wrote:
>>
>> Hi Colin,
>>
>> On Fri, Jun 28, 2019 at 10:32 AM Colin Ian King
>> wrote:
>>>
>>> On 28/06/2019 05:15, Martin Blumenstingl wrote:
On Tue, Jun 25, 2019 at 9:58 AM Colin Ian Kin
On 28.06.19 10:54, Abel Vesa wrote:
> On 19-06-23 13:47:26, Martin Kepplinger wrote:
>> On 10.06.19 14:13, Abel Vesa wrote:
>>> This is another alternative for the RFC:
>>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flkml.org%2Flkml%2F2019%2F3%2F27%2F545&data=02%7C01%7Cabel.ve
Commit-ID: ede7c247abfaeef62484cfff320b072ec2b1dca0
Gitweb: https://git.kernel.org/tip/ede7c247abfaeef62484cfff320b072ec2b1dca0
Author: YueHaibing
AuthorDate: Tue, 2 Jul 2019 14:18:47 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 2 Jul 2019 08:41:37 +0200
rslib: Make some functions
On Tue, Jul 2, 2019 at 8:38 AM Hillf Danton wrote:
>
>
> On Wed, 26 Jun 2019 20:59:05 -0700 (PDT)
> > syzbot has found a reproducer for the following crash on:
> >
> > HEAD commit:249155c2 Merge branch 'parisc-5.2-4' of git://git.kernel.o..
> > git tree: upstream
> > console output: http
Hi Anson,
On 19-06-27 07:01, Anson Huang wrote:
> Hi, Daniel
>
> > -Original Message-
> > From: Daniel Baluta
> > Sent: Thursday, June 27, 2019 2:44 PM
> > To: Anson Huang
> > Cc: Shawn Guo ; Sascha Hauer
> > ; Pengutronix Kernel Team
> > ; Fabio Estevam ; Aisheng
> > Dong ; Abel Vesa ;
Hi David,
Sorry for the late reply.
On Wed, 2019-06-26 at 10:28 +0200, David Hildenbrand wrote:
> On 26.06.19 10:15, Oscar Salvador wrote:
> > On Wed, Jun 26, 2019 at 10:11:06AM +0200, David Hildenbrand wrote:
> > > Back then, I already mentioned that we might have some users that
> > > remove_me
Wanpeng,
On Tue, 2 Jul 2019, Wanpeng Li wrote:
> On Tue, 2 Jul 2019 at 06:44, Thomas Gleixner wrote:
> >
> > While that CPU0 hotplug test case is surely an esoteric issue, the APIC
> > emulation is still wrong, Even if the play_dead() code would not enable
> > interrupts then the pending IRR bit
Hi,
Apologies in advance for extra CC list.
I'm trying to hack linux kernel (v4.14 LTS) for Raspberry PI 3 (ARM32 build), to
enable early boot code switch to secure mode using SMC #0 instruction and return
(and later tinker with some secure mode registers).
While this may generally not be possib
Hi Joel,
On Tue, Jul 02, 2019 at 02:07:05PM +0930, Joel Stanley wrote:
> The subsystem was merged some time ago but we did not have a maintainers
> entry.
>
> Signed-off-by: Joel Stanley
> ---
> MAINTAINERS | 13 +
> 1 file changed, 13 insertions(+)
>
> diff --git a/MAINTAINERS b/M
On Tue, Jun 11, 2019 at 12:23:12PM -0400, Benjamin Coddington wrote:
> Ugh.. Now that you can cancel the wait, you have to also handle if "new" was
> allocated. I think this needs:
>
> diff --git a/fs/nfs/client.c b/fs/nfs/client.c
> index d7e4f0848e28..4d90f5bf0b0a 100644
> --- a/fs/nfs/client.c
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 18 of them as possibly being bugs in the "fs/9p" subsyst
On Mon 01 Jul 00:02 PDT 2019, Clement Leger wrote:
> When preparing the subdevice for the vdev, also copy dma_pfn_offset
> since this is used for sub device dma allocations. Without that, there
> is incoherency between the parent dma settings and the childs one,
> potentially leading to dma_alloc_
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 5 of them as possibly being bugs in the "net/hsr" subsys
The ftrace test will need to have CONFIG_FTRACE enabled to make the
ftrace directory available.
Add an additional check to skip this test if the CONFIG_FTRACE was not
enabled.
This will be helpful to avoid a false-positive test result when testing
it directly with the following commad against a k
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 6 of them as possibly being bugs in the "net/smc" subsys
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 3 of them as possibly being bugs in the "net/rxrpc" subs
There is no caller of function iavf_debug_d() in tree since
commit 75051ce4c5d8 ("iavf: Fix up debug print macro"),
so it can be removed.
Reported-by: Hulk Robot
Signed-off-by: YueHaibing
---
drivers/net/ethernet/intel/iavf/iavf_main.c | 22 --
1 file changed, 22 deletions(-
Fix sparse warnings:
lib/reed_solomon/test_rslib.c:313:5: warning: symbol 'ex_rs_helper' was not
declared. Should it be static?
lib/reed_solomon/test_rslib.c:349:5: warning: symbol 'exercise_rs' was not
declared. Should it be static?
lib/reed_solomon/test_rslib.c:407:5: warning: symbol 'exercise
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 6 of them as possibly being bugs in the "net/dccp" subsy
On Tue, 2019-07-02 at 08:13 +0200, Michal Hocko wrote:
> On Tue 02-07-19 14:13:25, Alastair D'Silva wrote:
> > On Mon, 2019-07-01 at 12:46 +0200, Michal Hocko wrote:
> > > On Fri 28-06-19 10:46:28, Alastair D'Silva wrote:
> > > [...]
> > > > Given that there is already a VM_BUG_ON in the code, how
On Tue 02-07-19 14:13:25, Alastair D'Silva wrote:
> On Mon, 2019-07-01 at 12:46 +0200, Michal Hocko wrote:
> > On Fri 28-06-19 10:46:28, Alastair D'Silva wrote:
> > [...]
> > > Given that there is already a VM_BUG_ON in the code, how do you
> > > feel
> > > about broadening the scope from 'VM_BUG_O
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
Signed-off-by: YueHaibing
---
sound/soc/codecs/rt1308.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/soc/codecs/rt1308.c b/sound/soc/codecs/rt1308.c
index
On 02.07.2019 02:09, Matthias Kaehlcke wrote:
> On Mon, Jul 01, 2019 at 11:09:02PM +0200, Andrew Lunn wrote:
>> On Mon, Jul 01, 2019 at 10:37:16PM +0200, Heiner Kallweit wrote:
>>> On 01.07.2019 22:02, Andrew Lunn wrote:
On Mon, Jul 01, 2019 at 12:52:24PM -0700, Matthias Kaehlcke wrote:
>
From: Erin Lo
Provide a basic driver to control Cortex M4 co-processor
Signed-off-by: Erin Lo
Signed-off-by: Nicolas Boichat
Signed-off-by: Pi-Hsun Shih
---
Changes from v11:
- No change.
Changes from v10:
- Add a clock reset before loading firmware.
Changes from v9:
- No change.
Change
From: Erin Lo
Add memory table mapping API for other driver to lookup
reserved physical and virtual memory
Signed-off-by: Erin Lo
Signed-off-by: Pi-Hsun Shih
---
Changes from v11:
- No change.
Changes from v10:
- Fix some type mismatch warnings when printing debug messages.
Changes from v9
Add a simple rpmsg support for mt8183 SCP, that use IPI / IPC directly.
Signed-off-by: Pi-Hsun Shih
---
Changes from v11:
- Fix a bug that when rproc_boot fails, the ns_ept won't be properly
destroyed, causing memory leak.
- Add documentation for mtk_rpmsg_info.
Changes from v10, v9, v8, v7
From: Eddie Huang
Add scp node to mt8183 and mt8183-evb
Signed-off-by: Erin Lo
Signed-off-by: Pi-Hsun Shih
Signed-off-by: Eddie Huang
---
Changes from v11, v10:
- No change.
Changes from v9:
- Remove extra reserve-memory-vpu_share node.
Changes from v8:
- New patch.
---
arch/arm64/boot/
Add support for controlling and communicating with mt8183's system
control processor (SCP), using the remoteproc & rpmsg framework.
And also add a cros_ec driver for CrOS EC host command over rpmsg.
The overall structure of the series is:
* remoteproc/mtk_scp.c: Control the start / stop of SCP (Pa
From: Erin Lo
Add a DT binding documentation of SCP for the
MT8183 SoC from Mediatek.
Signed-off-by: Erin Lo
Signed-off-by: Pi-Hsun Shih
Reviewed-by: Rob Herring
---
Changes from v11, v10, v9, v8, v7, v6:
- No change.
Changes from v5:
- Remove dependency on CONFIG_RPMSG_MTK_SCP.
Changes f
On 6/27/2019 12:55 PM, Aniket Masule wrote:
From: Malathi Gottam
This adds video nodes to sdm845 based on the examples
in the bindings.
Signed-off-by: Malathi Gottam
Co-developed-by: Aniket Masule
Signed-off-by: Aniket Masule
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 30 ++
On Tue, 2 Jul 2019 10:25:04 +0530
Kirti Wankhede wrote:
> On 7/2/2019 1:34 AM, Alex Williamson wrote:
> > On Mon, 1 Jul 2019 23:20:35 +0530
> > Kirti Wankhede wrote:
> >
> >> On 7/1/2019 10:54 PM, Alex Williamson wrote:
> >>> On Mon, 1 Jul 2019 22:43:10 +0530
> >>> Kirti Wankhede wrote:
>
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 22 of them as possibly being bugs in the perf subsystem.
On Tue, 2 Jul 2019 10:25:04 +0530
Kirti Wankhede wrote:
> On 7/2/2019 1:34 AM, Alex Williamson wrote:
> > On Mon, 1 Jul 2019 23:20:35 +0530
> > Kirti Wankhede wrote:
> >
> >> On 7/1/2019 10:54 PM, Alex Williamson wrote:
> >>> On Mon, 1 Jul 2019 22:43:10 +0530
> >>> Kirti Wankhede wrote:
>
Hi Stan,
On 2019-07-01 21:15, Stanimir Varbanov wrote:
Hi Aniket,
On 6/26/19 11:23 AM, Aniket Masule wrote:
Introduced clock scaling using bitrate, current
calculations consider only the cycles per mb.
Also, clock scaling is now triggered before every
buffer being queued to the device. This he
This helper is required from generic huge_pte_alloc() which is available
when arch subscribes ARCH_WANT_GENERAL_HUGETLB. arm64 implements it's own
huge_pte_alloc() and does not depend on the generic definition. Drop this
helper which is redundant on arm64.
Cc: Catalin Marinas
Cc: Will Deacon
Cc:
Hi all,
After merging the tip tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/btrfs/ctree.c: In function '__tree_mod_log_insert':
fs/btrfs/ctree.c:388:2: error: implicit declaration of function
'lockdep_assert_held_exclusive'; did you mean 'lockdep_assert_held_once'
Put the boundary check before it accesses user space to prevent unnecessary
access which might crash the machine.
Especially, ftrace preemptirq/irq_disable event with user stack trace
option can trigger SEGV in pid 1 which leads to panic.
Reproducer:
CONFIG_PREEMPTIRQ_TRACEPOINTS=y
# echo 1
On Tue, Jul 02, 2019 at 01:24:43PM +0800, Jason Wang wrote:
> >
> > Title: INFO: task hung in vhost_init_device_iotlb
> > Last occurred: 125 days ago
> > Reported: 153 days ago
> > Branches:
Hi Thomas,
On Tue, 2 Jul 2019 at 06:44, Thomas Gleixner wrote:
>
> Folks,
>
> after chasing a 0-day test failure for a couple of days, I was finally able
> to reproduce the issue.
>
> Background:
>
>In preparation of supporting IPI shorthands I changed the CPU offline
>code to software dis
ptrace-hwbreak.c selftest is logically broken. On powerpc, when
watchpoint is created with ptrace, signals are generated before
executing the instruction and user has to manually singlestep
the instruction with watchpoint disabled, which selftest never
does and thus it keeps on getting the signal a
Watchpoint match range is always doubleword(8 bytes) aligned on
powerpc. If the given range is crossing doubleword boundary, we
need to increase the length such that next doubleword also get
covered. Ex,
address len = 6 bytes
|=.
|v--|--v-
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 5 of them as possibly being bugs in the "fs/fuse" subsys
On 2019/7/2 下午1:17, Eric Biggers wrote:
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 2 of them as
Map 'xen_nopv' to 'nopv' and mark 'xen_nopv' obsolete in
kernel-parameters.txt
Signed-off-by: Zhenzhong Duan
Cc: Boris Ostrovsky
Cc: Juergen Gross
Cc: Stefano Stabellini
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
---
Documentation/admin-guide/kernel-parameters.txt | 6 ++
This reverts commit 8d693b911bb9c57009c24cb1772d205b84c7985c.
Instead we use an unified parameter 'nopv' for all the hypervisor
platforms.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Juergen Gross
Cc: Boris Ostrovsky
Cc: Juergen Gross
Cc: Stefano Stabellini
Cc: Thomas Gleixner
Cc: Ingo Molna
In virtualization environment, PV extensions (drivers, interrupts,
timers, etc) are enabled in the majority of use cases which is the
best option.
However, in some cases (kexec not fully working, benchmarking)
we want to disable PV extensions. As such introduce the
'nopv' parameter that will do it
PVH guest needs PV extentions to work, so 'nopv' parameter should be
ignored for PVH but not for HVM guest.
If PVH guest boots up via the Xen-PVH boot entry, xen_pvh is set early,
we know it's PVH guest and ignore 'nopv' parameter directly.
If PVH guest boots up via the normal boot entry same as
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 2 of them as possibly being bugs in the vhost subsystem.
.. as they are only called at early bootup stage. In fact, other
functions in x86_hyper_xen_hvm.init.* are all marked as __init.
Unexport xen_hvm_need_lapic as it's never used outside.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Juergen Gross
Cc: Boris Ostrovsky
Cc: Stefano Stabellini
Cc: Thom
Hi,
In virtualization environment, PV extensions (drivers, interrupts,
timers, etc) are enabled in the majority of use cases which is the
best option.
However, in some cases (kexec not fully working, benchmarking, etc)
we want to disable PV extensions. We have xen_nopv for that purpose
but only f
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 2 of them as possibly being bugs in the "security/tomoyo
On Mon, Jul 01, 2019 at 01:12:16PM -0700, Paul E. McKenney wrote:
> On Mon, Jul 01, 2019 at 09:40:39AM +0900, Byungchul Park wrote:
> > Hello,
> >
> > I tested again if the WARN_ON_ONCE() is fired with my box.
> >
> > And it was OK.
> >
> > Thanks,
> > Byungchul
>
> And it now applies just fine
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 1 of them as possibly being a bug in the "security/smack
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 1 of them as possibly being a bug in the rtc subsystem.
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 1 of them as possibly being a bug in the hid subsystem.
Hi Jolly,
> -Original Message-
> From: Jolly Shah
> Sent: Monday, July 1, 2019 11:36 PM
> To: Manish Narani ; ulf.hans...@linaro.org;
> robh...@kernel.org; mark.rutl...@arm.com; he...@sntech.de; Michal Simek
> ; adrian.hun...@intel.com;
> christoph.muell...@theobroma-systems.com; philipp.
Hi Stan,
On 2019-07-01 19:28, Stanimir Varbanov wrote:
Hi,
On 6/25/19 7:27 PM, Aniket Masule wrote:
Present core assignment is static. Introduced load balancing
across the cores. Load on earch core is calculated and core
with minimum load is assigned to given instance.
Signed-off-by: Aniket M
Hi Stan,
On 2019-07-01 18:41, Stanimir Varbanov wrote:
On 6/25/19 7:27 PM, Aniket Masule wrote:
Current clock scaling calculations are same for vpu4 and
previous versions. For vpu4, Clock scaling calculations
are updated with cycles/mb. This helps in getting precise
clock required.
Signed-off-
Hi Stan,
On 2019-07-01 17:13, Stanimir Varbanov wrote:
On 6/25/19 7:27 PM, Aniket Masule wrote:
Add vpp cycles for for different types of codec
It indicates the cycles required by video hardware
to process each macroblock. Initialize the codec
data with core resources.
Signed-off-by: Aniket Ma
On 7/2/2019 1:34 AM, Alex Williamson wrote:
> On Mon, 1 Jul 2019 23:20:35 +0530
> Kirti Wankhede wrote:
>
>> On 7/1/2019 10:54 PM, Alex Williamson wrote:
>>> On Mon, 1 Jul 2019 22:43:10 +0530
>>> Kirti Wankhede wrote:
>>>
On 7/1/2019 8:24 PM, Alex Williamson wrote:
> This allows
Hi Joel,
> The subsystem was merged some time ago but we did not have a
> maintainers
> entry.
Acked-by: Jeremy Kerr
Cheers,
Jeremy
On 2019/7/2 11:48, Boris Ostrovsky wrote:
On Mon, Jul 01, 2019 at 10:20:27AM +0800, Zhenzhong Duan wrote:
This reverts commit 8d693b911bb9c57009c24cb1772d205b84c7985c.
Instead we use an unified parameter 'nopv' for all the hypervisor
platforms.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Juer
The subsystem was merged some time ago but we did not have a maintainers
entry.
Signed-off-by: Joel Stanley
---
MAINTAINERS | 13 +
1 file changed, 13 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 01a52fc964da..2a5df9c20ecb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@
With OPP core now supporting DVFS for IO devices, we have instances of
IO devices (same IP block) with require an OPP on some platforms/SoCs
while just needing to scale the clock on some others.
In order to avoid conditional code in every driver, (to check for
availability of OPPs and then decidin
Export dev_pm_opp_set_genpd_virt_dev() so loadable modules can use it.
Signed-off-by: Rajendra Nayak
---
drivers/opp/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/opp/core.c b/drivers/opp/core.c
index 8fbdbedc009c..ae033bb1e5b7 100644
--- a/drivers/opp/core.c
+++ b/drivers/o
Sorry to break into your privacy in this manner,
I'm Smadar Barber-Tsadik, Deputy Chief Executive Officer
of First International Bank of Israel Ltd (FIBI).
I am getting in touch with you regarding an extremely
important and urgent matter. If you would oblige me the
opportunity, I shall provide
Hi Stephen,
You are correct, Its
Fixes: ba94c753ccb4 ("ath10k: add QMI message handshake for wcn3990 client")
My bad, I added last 12 digits instead of first 12 digits of SHA1.
Regards,
Dundi
-Original Message-
From: Stephen Rothwell
Sent: Tuesday, July 2, 2019 3:03 AM
To: Kalle Valo
On 7/1/19 4:44 AM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Both the PCI bus type and the ACPI PM domain avoid resuming
> runtime-suspended devices with DPM_FLAG_SMART_SUSPEND set during
> hibernation (before creating the snapshot image of system memory),
> but that turns out to be
On Mon, 2019-07-01 at 12:46 +0200, Michal Hocko wrote:
> On Fri 28-06-19 10:46:28, Alastair D'Silva wrote:
> [...]
> > Given that there is already a VM_BUG_ON in the code, how do you
> > feel
> > about broadening the scope from 'VM_BUG_ON(!root)' to
> > 'VM_BUG_ON(!root
> > > > (root_nr == NR_SECTI
On Tue, Jul 02, 2019 at 10:05:33AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 16fff98a7e82 ("net/mlx5: E-Switch, Reg/unreg function changed event at
> correct stage")
>
> Fixes tag
>
> Fixes: 61fc880839e6 ("net/mlx5: E-Switch, Handle representors creation in
> handler context"
On Tue, Jul 02, 2019 at 01:13:27PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the mlx5-next tree got a conflict in:
>
> drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c
>
> between commit:
>
> 955858009708 ("net/mlx5e: Fix number of vports for ingress ACL
On Mon, Jul 1, 2019 at 8:43 PM Andy Lutomirski wrote:
>
> In -tip, if FSGSBASE and PTI are on, the kernel crashes if SYSENTER
> happens with TF set. It also crashes under if a non-NMI paranoid
> entry happens for any other reason from kernel mode with user GSBASE
> and user CR3, e.g. due to MOV S
On Thu, Jun 27, 2019 at 11:24:41PM +0200, Thomas Gleixner wrote:
> On Wed, 26 Jun 2019, Zhenzhong Duan wrote:
>
> > This reverts commit ca5d376e17072c1b60c3fee66f3be58ef018952d.
> >
> > Commit 8990cac6e5ea ("x86/jump_label: Initialize static branching
> > early") adds jump_label_init() call in se
Hi all,
After merging the amdgpu tree, today's linux-next build (x86_64
allmodcnofig) produced this warning:
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device.c: In function 'kgd2kfd_probe':
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device.c:490:6: warning: unused
variable 'ret' [-Wunused-variable]
On Mon, Jul 01, 2019 at 10:20:27AM +0800, Zhenzhong Duan wrote:
> This reverts commit 8d693b911bb9c57009c24cb1772d205b84c7985c.
>
> Instead we use an unified parameter 'nopv' for all the hypervisor
> platforms.
>
> Signed-off-by: Zhenzhong Duan
> Reviewed-by: Juergen Gross
> Cc: Boris Ostrovsky
On Mon, Jul 01, 2019 at 12:04:13AM -0400, Joel Fernandes (Google) wrote:
> The t->rcu_read_unlock_special union's need_qs bit can be set by the
> scheduler tick (in rcu_flavor_sched_clock_irq) to indicate that help is
> needed from the rcu_read_unlock path. When this help arrives however, we
> can
In -tip, if FSGSBASE and PTI are on, the kernel crashes if SYSENTER
happens with TF set. It also crashes under if a non-NMI paranoid
entry happens for any other reason from kernel mode with user GSBASE
and user CR3, e.g. due to MOV SS shenanigans.
This series fixes the bug. It also adds another
paranoid_exit needs to restore CR3 before GSBASE. Doing it in the
opposite order crashes if the exception came from a context with
user GSBASE and user CR3 -- RESTORE_CR3 cannot resture user CR3 if
run with user GSBASE. This results in infinitely recursing
exceptions if user code does SYSENTER wi
It's only used if !CONFIG_IA32_EMULATION, so disable it in normal
configs. This will save a few bytes of text and reduce confusion.
Cc: "Bae, Chang Seok"
Signed-off-by: Andy Lutomirski
---
arch/x86/entry/entry_64.S | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/x86/entry/entry_
Make sure that we exercise both variants of the nasty
TF-in-compat-syscall regardless of what vendor's CPU is running the
tests.
Also change the intentional signal after SYSCALL to use ud2, which
is a lot more comprehensible.
This crashes the kernel due to an FSGSBASE bug right now.
This test *a
On Mon, Jul 1, 2019 at 6:46 PM Rob Herring wrote:
>
> On Mon, Jul 1, 2019 at 6:48 PM Saravana Kannan wrote:
> >
> > The driver core/bus adding dependencies by default makes sure that
> > suppliers don't sync the hardware state with software state before all the
> > consumers have their drivers lo
Add NI PXIe-RS232, PXI-RS485 and PXIe-RS485 device IDs.
Signed-off-by: jeyentam
---
include/linux/pci_ids.h | 62 -
1 file changed, 37 insertions(+), 25 deletions(-)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index 70e86148cb1e..cc1f61
On 06/28/2019 03:50 PM, Catalin Marinas wrote:
> Hi Anshuman,
Hello Catalin,
>
> On Thu, Jun 27, 2019 at 06:18:15PM +0530, Anshuman Khandual wrote:
>> pmd_present() and pmd_trans_huge() are expected to behave in the following
>> manner during various phases of a given PMD. It is derived from a
Add support for NI-Serial PXIe-RS232, PXI-RS485 and PXIe-RS485 devices.
Signed-off-by: jeyentam
---
drivers/tty/serial/8250/8250_pci.c | 879 +++--
1 file changed, 582 insertions(+), 297 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_pci.c
b/drivers/tty/serial/8
On Sun, Jun 30, 2019 at 02:37:32PM -0700, Dan Williams wrote:
> On Sun, Jun 30, 2019 at 8:23 AM Matthew Wilcox wrote:
> > I think my theory was slightly mistaken, but your fix has the effect of
> > fixing the actual problem too.
> >
> > The xas->xa_index for a PMD is going to be PMD-aligned (ie a
On Mon, Jul 1, 2019 at 6:32 PM Rob Herring wrote:
>
> On Mon, Jul 1, 2019 at 6:48 PM Saravana Kannan wrote:
> >
> > 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 devi
This patchset add support to MT2712 RTC. MT2712 RTC is a SoC based RTC
with different architecture compared to MT7622 RTC.
Ran Bi (3):
bindings: rtc: add bindings for MT2712 RTC
rtc: Add support for the MediaTek MT2712 RTC
arm64: dts: add rtc nodes for MT2712
.../devicetree/bindings/rtc/rt
Document the binding for MT2712 RTC implemented by rtc-mt2712.
Signed-off-by: Ran Bi
---
.../devicetree/bindings/rtc/rtc-mt2712.txt | 14 ++
1 file changed, 14 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/rtc-mt2712.txt
diff --git a/Documentation/d
This patch add device node for MT2712 rtc.
Signed-off-by: Ran Bi
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
index 43307bad3f0d..31166c17c39a 100644
This add support for the MediaTek MT2712 RTC. It was SoC based RTC, but
had different architecture compared with MT7622 RTC.
Signed-off-by: Ran Bi
---
drivers/rtc/Kconfig | 10 +
drivers/rtc/Makefile | 1 +
drivers/rtc/rtc-mt2712.c | 495 +++
3 fil
On 7/1/19 1:59 AM, Mel Gorman wrote:
> On Fri, Jun 28, 2019 at 11:20:42AM -0700, Mike Kravetz wrote:
>> On 4/24/19 7:35 AM, Vlastimil Babka wrote:
>>> On 4/23/19 6:39 PM, Mike Kravetz wrote:
> That being said, I do not think __GFP_RETRY_MAYFAIL is wrong here. It
> looks like there is someth
Hi, Rob,
Sorry to bother you, could you please review this patch when you are
available? Thanks.
On Mon, 2019-07-01 at 15:48 +0800, Bibby Hsieh wrote:
> cmdq driver provide a function that get the relationship
> of sub system number from device node for client.
> add specification for #subsys-cel
Hi all,
Today's linux-next merge of the mlx5-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c
between commit:
955858009708 ("net/mlx5e: Fix number of vports for ingress ACL configuration")
from Linus' tree and commit:
062f4bf4aab5 ("net/mlx5: E-Swi
Hi all,
Today's linux-next merge of the mlx5-next tree got conflicts in:
drivers/net/ethernet/mellanox/mlx5/core/eswitch.c
between commits:
02f3afd97556 ("net/mlx5: E-Switch, Correct type to u16 for vport_num and int
for vport_index")
from Linus' tree and commit:
5f5d2536be8d ("net/mlx
Hi Ben,
Benjamin Herrenschmidt 于2019年7月2日周二 上午10:44写道：
>
> Munchun, is this what your patch fixes ?
>
Yes, this is what my patch fixes.
The patchs can reference to:
[PATCH v1 OPT1] driver core: Fix use-after-free and double
free on glue directory
[PATCH v4 OPT2] driver core: Fix
Hi Ben,
On 6/18/2019 7:28 AM, Ben Hutchings wrote:
> 3.16.69-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Eric Dumazet
>
> commit f070ef2ac66716357066b683fb0baf55f8191a2e upstream.
>
> Jonathan Looney reported that a malicious peer can
1 - 100 of 816 matches
Mail list logo
