On Wed, 3 Jan 2018 19:18:52 +0530
Gaurav Kohli wrote:
> There can be a race, if receive_buf call comes before
> tty initialization completes in n_tty_open and tty->disc_data
> may be NULL.
This makes no sense. If the race exists then the check you do isn't good
enough because the ldsic dsta is
On Wed 03 Jan 08:26 PST 2018, Srinivas Kandagatla wrote:
> Thanks for your review comments.
>
> On 02/01/18 05:48, Bjorn Andersson wrote:
> > On Thu 14 Dec 09:33 PST 2017, srinivas.kandaga...@linaro.org wrote:
[..]
> > > +int q6asm_unmap_memory_regions(unsigned int dir, struct audio_client *ac)
>
On 12/26/2017 09:43 PM, Tom Lendacky wrote:
>AMD processors are not subject to the types of attacks that the kernel page
>table isolation
feature protects against.
There is no doubt this is a serious flaw. This thread reminded me - about a
year ago we
discovered a software code that bricked an
On 01/03, Srinivas Kandagatla wrote:
> Thanks for your review comments,
>
> On 03/01/18 17:20, Stephen Boyd wrote:
> >>+
> >>+ return ret;
> >>+}
> >>+
> >>+static int msm_snd_apq8096_probe(struct platform_device *pdev)
> >>+{
> >>+ int ret;
> >>+ struct snd_soc_card *card;
> >>+
> >>+ car
On Thu, Dec 28, 2017 at 03:40:37PM +0100, Ulf Hansson wrote:
> From: Lina Iyer
>
> Update DT bindings to represent hierarchical CPU and CPU domain idle states
> for PSCI. Also update the PSCI examples to clearly show how flattened and
> hierarchical idle states can be represented in DT.
>
> Sign
On Wed, Jan 03, 2018 at 12:58:02AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 72bca2084a21edda74b802bc076083d5951f67b4
> 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 Thu, Dec 28, 2017 at 05:33:35PM +0100, Mylène Josserand wrote:
> Add the support of regulator to use it as VCC source.
>
> Signed-off-by: Mylène Josserand
> ---
> .../bindings/input/touchscreen/edt-ft5x06.txt | 1 +
> drivers/input/touchscreen/edt-ft5x06.c | 33
> ++
On Wed 03 Jan 08:27 PST 2018, Srinivas Kandagatla wrote:
>
>
> On 03/01/18 00:28, Bjorn Andersson wrote:
> > On Thu 14 Dec 09:34 PST 2017, srinivas.kandaga...@linaro.org wrote:
> >
> > > +++ b/Documentation/devicetree/bindings/sound/qcom,apq8096.txt
> >
> > Wouldn't it be possible to describe
On 01/03/2018 01:25 PM, Randy Dunlap wrote:
On 01/03/2018 08:50 AM, Pierre-Louis Bossart wrote:
From: Vinod Koul
Helps in finding if endings
That partial sentence is confusing. I couldn't decode it without
reading the entire patch. That shouldn't be necessary.
How about:
Help in finding
* Rafael J. Wysocki [171229 23:52]:
> On Fri, Dec 29, 2017 at 6:57 PM, Tony Lindgren wrote:
> > * Jeffy Chen [171226 02:11]:
> >> We are going to handle PCIe WAKE# pin for PCI devices in the pci core,
> >> so add definitions of the optional PCIe WAKE# pin for PCI devices.
> >>
> >> Also add an d
* Rafael J. Wysocki [171230 00:34]:
> On Sat, Dec 30, 2017 at 12:50 AM, Rafael J. Wysocki wrote:
> > On Fri, Dec 29, 2017 at 6:57 PM, Tony Lindgren wrote:
> >> * Jeffy Chen [171226 02:11]:
> >>> We are going to handle PCIe WAKE# pin for PCI devices in the pci core,
> >>> so add definitions of t
On Wed, 3 Jan 2018, Paolo Bonzini wrote:
> On 03/01/2018 11:36, Thomas Gleixner wrote:
> > On Wed, 3 Jan 2018, Guillaume Tucker wrote:
> >> On 03/01/18 09:48, Thomas Gleixner wrote:
> Well, it turns out this is not exactly a conflict as there's a
> subtle difference between the qemu devic
* Rafael J. Wysocki [171230 00:24]:
> On Sat, Dec 30, 2017 at 12:39 AM, Rafael J. Wysocki wrote:
> > No, you need a wakeirq properly for the child *device* and that
> > property will be consumed by the PCI layer.
>
> Or, if you use the convention mentioned in another message in this
> thread, yo
Add a simple description of struct nvmem_config and its fields.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infradead.org
Cc: linux-rockc.
Looks like commas were accidentally used where semicolons were
supposed to be. Fix that.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infra
There's "dev" variable for this already. Use it.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infradead.org
Cc: linux-rockc...@lists.infrad
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
There's "dev" variable for this already. Use it.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infradead.org
Cc: linux-rockc...@lists.infrad
On Thu, Dec 28, 2017 at 10:29:52PM +0100, Mathieu Malaterre wrote:
> From: PrasannaKumar Muralidharan
>
> This patch brings support for the JZ4780 efuse. Currently it only expose
> a read only access to the entire 8K bits efuse memory.
>
> Tested-by: Mathieu Malaterre
> Signed-off-by: PrasannaK
There already a "dev" variable for that. Use it.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infradead.org
Cc: linux-rockc...@lists.infrad
There's already "dev" variable for that. Use it.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infradead.org
Cc: linux-rockc...@lists.infrad
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
Simplify code a bit by using of_device_get_match_data() instead of
of_match_device().
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infradea
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
Being able to build this driver when COMPILE_TEST is selected is still
useful even when MESON_SM is not selected, since selecting this
driver as a module and doing "make modules" will result in successful
build and would detect trivial coding errors. For an example of type
of errors that could be p
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
On 12/30, Yunlong Song wrote:
> In some case, the node blocks has wrong blkaddr whose segment type is
> NODE, e.g., recover inode has missing xattr flag and the blkaddr is in
> the xattr range. Since fsck.f2fs does not check the recovery nodes, this
> will cause __f2fs_replace_block change the curs
On Thu, Dec 28, 2017 at 10:29:53PM +0100, Mathieu Malaterre wrote:
> MIPS Creator CI20 comes with JZ4780 SoC. Provides access to the efuse block
> using jz4780 efuse driver.
>
> Signed-off-by: Mathieu Malaterre
> ---
> arch/mips/configs/ci20_defconfig | 2 ++
Your subject indicates this is a dts
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
On Wed 03 Jan 08:27 PST 2018, Srinivas Kandagatla wrote:
> Thanks for the review comments.
>
>
> On 03/01/18 00:16, Bjorn Andersson wrote:
> > On Thu 14 Dec 09:34 PST 2017, srinivas.kandaga...@linaro.org wrote:
> >
> > > From: Srinivas Kandagatla
> > >
> > > uThis patch adds support to DB820c
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
Introduce devm_nvmem_register()/devm_nvmem_unregister() to make
.remove() unnecessary in trivial drivers.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-med
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
On Wed 03 Jan 08:27 PST 2018, Srinivas Kandagatla wrote:
> Thanks for the comments,
>
> On 03/01/18 00:22, Bjorn Andersson wrote:
> > On Thu 14 Dec 09:34 PST 2017, srinivas.kandaga...@linaro.org wrote:
> >
> > > From: Srinivas Kandagatla
[..]
> > > + lpass_q6_smmu: arm,smmu-lpass_q6@160
Add code to allow avoid having nvmem core append a numeric suffix to
the end of the name by passing config->id of -1.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
C
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.in
Srinivas, all:
This patchset contains various small changes that I recently made to
NVMEM, more specifically:
- Patches 1 and 3 are two changes I am hoping are acceptable upstream
- Patches 4 to 15 are a follow up to patch 2
- Patches 16 to 22 are just trivial fixups and I am more than happy
Hi,
* Rafael J. Wysocki [171228 17:33]:
> So we are fine except for the race and we need the wakeirq field in wakeup
> sources to automatically arm the wakeup IRQs during suspend.
>
> If I'm not mistaken, we only need something like the patch below (untested).
Yeah for your patch below works ju
From: Markus Elfring
Date: Wed, 3 Jan 2018 21:06:54 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation
in __if_usb_submit_rx_urb()
Improve a size determination in two functions
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
kaiser_add_user_map() took no notice when kaiser_pagetable_walk() failed.
And avoid its might_sleep() when atomic (though atomic at present unused).
Signed-off-by: Hugh Dickins
A
This is the start of the stable review cycle for the 4.4.110 release.
There are 37 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Fri Jan 5 19:50:38 UTC 2018.
Anything receiv
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
There's a 0x1000 in various places, which looks better with a name.
Signed-off-by: Hugh Dickins
Acked-by: Jiri Kosina
Signed-off-by: Greg Kroah-Hartman
---
arch/x86/entry/entr
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Mainly deleting a surfeit of blank lines, and reflowing header comment.
Signed-off-by: Hugh Dickins
Acked-by: Jiri Kosina
Signed-off-by: Greg Kroah-Hartman
---
arch/x86/includ
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Richard Fellner
This patch introduces our implementation of KAISER (Kernel Address Isolation to
have Side-channels Efficiently Removed), a kernel isolation technique to close
hardware side chan
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Why was 4 chosen for kernel PCID and 6 for user PCID?
No good reason in a backport where PCIDs are only used for Kaiser.
If we continue with those, then we shall need to add Andy
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
Merged performance improvements to Kaiser, using distinct kernel
and user Process Context Identifiers to minimize the TLB flushing.
Signed-off-by: Hugh Dickins
Acked-by: Jiri Kosi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
We fail to see what CONFIG_KAISER_REAL_SWITCH is for: it seems to be
left over from early development, and now just obscures tricky parts
of the code. Delete it before adding PCID
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
Concentrate it in arch/x86/mm/kaiser.c and use the upstream string "nopti".
Signed-off-by: Borislav Petkov
Signed-off-by: Greg Kroah-Hartman
---
Documentation/kernel-paramet
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
AMD (and possibly other vendors) are not affected by the leak
KAISER is protecting against.
Keep the "nopti" for traditional reasons and add pti=
like upstream.
Signed-off-by:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Kaiser only needs to map one page of the stack; and
kernel/fork.c did not build on powerpc (no __PAGE_KERNEL).
It's all cleaner if linux/kaiser.h provides kaiser_map_thread_stack()
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Include linux/kaiser.h instead of asm/kaiser.h to build ldt.c without
CONFIG_KAISER. kaiser_add_mapping() does already return an error code,
so fix the FIXME.
Signed-off-by: Hugh
This patch convert the driver to the new crypto engine API.
Signed-off-by: Corentin Labbe
---
drivers/crypto/omap-aes.c | 17 +
drivers/crypto/omap-aes.h | 3 +++
drivers/crypto/omap-des.c | 20
3 files changed, 32 insertions(+), 8 deletions(-)
diff --git a
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
I have not observed a might_sleep() warning from setup_fixmap_gdt()'s
use of kaiser_add_mapping() in our tree (why not?), but like upstream
we have not provided a way for that to p
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Avoid perf crashes: place debug_store in the user-mapped per-cpu area
instead of allocating, and use page allocator plus kaiser_add_mapping()
to keep the BTS and PEBS buffers user-
This is the start of the stable review cycle for the 4.9.75 release.
There are 39 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Fri Jan 5 19:50:44 UTC 2018.
Anything receive
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Use tab not space so they line up properly, kaslr.o also.
Signed-off-by: Hugh Dickins
Signed-off-by: Greg Kroah-Hartman
---
arch/x86/mm/Makefile |4 ++--
1 file changed, 2
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Mostly this commit is just unshouting X86_CR3_PCID_KERN_VAR and
X86_CR3_PCID_USER_VAR: we usually name variables in lower-case.
But why does x86_cr3_pcid_noflush need to be __alig
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Neel Natu points out that paranoid_entry() was wrong to assume that
an entry that did not need swapgs would not need SWITCH_KERNEL_CR3:
paranoid_entry (used for debug breakpoint, i
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
When removing the bogus comment from kaiser_remove_mapping(),
I really ought to have checked the extent of its bogosity: as
Neel points out, there is nothing to stop unmap_pud_rang
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Now that we're playing the ALTERNATIVE game, use that more efficient
method: instead of user-mapping an extra page, and reading an extra
cacheline each time for x86_cr3_pcid_noflus
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Yes, unmap_pud_range_nofree()'s declaration ought to be in a
header file really, but I'm not sure we want to use it anyway:
so for now just declare it inside kaiser_remove_mapping(
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
I have not observed a might_sleep() warning from setup_fixmap_gdt()'s
use of kaiser_add_mapping() in our tree (why not?), but like upstream
we have not provided a way for that to p
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
We fail to see what CONFIG_KAISER_REAL_SWITCH is for: it seems to be
left over from early development, and now just obscures tricky parts
of the code. Delete it before adding PCID
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
pjt has observed that nmi's second (nmi_from_kernel) call to do_nmi()
adjusted the %rdi regs arg, rightly when CONFIG_KAISER, but wrongly
when not CONFIG_KAISER.
Although the mini
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
native_pgd_clear() uses native_set_pgd(), so native_set_pgd() must
avoid setting the _PAGE_NX bit on an otherwise pgd_none() entry:
usually that just generated a warning on exit, b
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
Make sure dmesg reports when KPTI is enabled.
Signed-off-by: Kees Cook
Signed-off-by: Greg Kroah-Hartman
---
arch/x86/mm/kaiser.c |7 ++-
1 file changed, 6 insertions(+), 1
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
Now that the required bits have been addressed, reenable
PARAVIRT.
Signed-off-by: Borislav Petkov
Signed-off-by: Greg Kroah-Hartman
---
security/Kconfig |2 +-
1 file ch
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Let kaiser_flush_tlb_on_return_to_user() do the X86_FEATURE_PCID
check, instead of each caller doing it inline first: nobody needs
to optimize for the noPCID case, it's clearer thi
On Wed, 3 Jan 2018 14:22:37 -0500
Albert Cahalan wrote:
> We got into the current situation for performance reasons, avoiding the costly
> reload of CR3 that a hardware task switch would cause. It seems we'll be
> loading CR3 now anyway, so it might be time to reconsider hardware
> task switches.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
This renames CONFIG_KAISER to CONFIG_PAGE_TABLE_ISOLATION.
Signed-off-by: Kees Cook
Signed-off-by: Greg Kroah-Hartman
---
arch/x86/boot/compressed/misc.h |2 +-
arch/x
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Kosina
Kaiser cannot be used on paravirtualized MMUs (namely reading and writing CR3).
This does not work with KAISER as the CR3 switch from and to user space PGD
would require to map the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
... before the first use of kaiser_enabled as otherwise funky
things happen:
about to get started...
(XEN) d0v0 Unhandled page fault fault/trap [#14, ec=]
(XEN) Paget
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit a035795499ca1c2bd1928808d1a156eda1420383 upstream
native_flush_tlb_single() will be changed with the upcoming
PAGE_TABLE_ISOLATION feature. This requires to have more co
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Include linux/kaiser.h instead of asm/kaiser.h to build ldt.c without
CONFIG_KAISER. kaiser_add_mapping() does already return an error code,
so fix the FIXME.
Signed-off-by: Hugh
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Neal Cardwell
commit 2f6c498e4f15d27852c04ed46d804a39137ba364 upstream.
Fix BBR so that upon notification of a loss recovery undo BBR resets
the full pipe detection (STARTUP exit) state machine
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
It is absurd that KAISER should depend on SMP, but apparently nobody
has tried a UP build before: which breaks on implicit declaration of
function 'per_cpu_offset' in arch/x86/mm/k
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Kaiser only needs to map one page of the stack; and
kernel/fork.c did not build on powerpc (no __PAGE_KERNEL).
It's all cleaner if linux/kaiser.h provides kaiser_map_thread_stack()
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Richard Fellner
This patch introduces our implementation of KAISER (Kernel Address Isolation to
have Side-channels Efficiently Removed), a kernel isolation technique to close
hardware side chan
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
Merged fixes and cleanups, rebased to 4.9.51 tree (no 5-level paging).
Signed-off-by: Hugh Dickins
Signed-off-by: Greg Kroah-Hartman
---
arch/x86/entry/entry_64.S|
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
I found asm/tlbflush.h too twisty, and think it safer not to avoid
__native_flush_tlb_global_irq_disabled() in the kaiser_enabled case,
but instead let it handle kaiser_enabled alo
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
AMD (and possibly other vendors) are not affected by the leak
KAISER is protecting against.
Keep the "nopti" for traditional reasons and add pti=
like upstream.
Signed-off-by:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
Concentrate it in arch/x86/mm/kaiser.c and use the upstream string "nopti".
Signed-off-by: Borislav Petkov
Signed-off-by: Greg Kroah-Hartman
---
Documentation/kernel-paramet
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Added "nokaiser" boot option: an early param like "noinvpcid".
Most places now check int kaiser_enabled (#defined 0 when not
CONFIG_KAISER) instead of #ifdef CONFIG_KAISER; but ent
On Wed 03 Jan 05:15 PST 2018, Loic PALLARDY wrote:
> > -Original Message-
> > From: linux-remoteproc-ow...@vger.kernel.org [mailto:linux-remoteproc-
> > ow...@vger.kernel.org] On Behalf Of Loic PALLARDY
> > Sent: Wednesday, January 03, 2018 11:27 AM
> > To: Bjorn Andersson ; Ohad Ben-Cohen
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
An error from kaiser_add_mapping() here is not at all likely, but
Eric Biggers rightly points out that __free_ldt_struct() relies on
new_ldt->size being initialized: move that up.
Hi Stephane and Andi,
Could you please review the script?
If it's OK for you, could you please Ack/Review this?
Thanks,
Kan
>
> From: Kan Liang
>
> There could be different types of memory in the system. E.g normal
> System Memory, Persistent Memory. To understand how the workload maps
> to
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Why was 4 chosen for kernel PCID and 6 for user PCID?
No good reason in a backport where PCIDs are only used for Kaiser.
If we continue with those, then we shall need to add Andy
On Sat, Dec 30, 2017 at 11:40:06AM -0800, Randy Dunlap wrote:
> On 12/30/2017 09:58 AM, Dan Aloni wrote:
> > From: Dan Aloni
> >
> > Signed-off-by: Dan Aloni
> > ---
> > Documentation/admin-guide/dmesg-encryption.rst | 77
> > ++
> > 1 file changed, 77 insertions(+)
> >
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
We have many machines (Westmere, Sandybridge, Ivybridge) supporting
PCID but not INVPCID: on these load_new_mm_cr3() simply crashed.
Flushing user context inside load_new_mm_cr3()
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
The kaiser update made an interesting choice, never to free any shadow
page tables. Contention on global spinlock was worrying, particularly
with it held across page table scans w
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Merged performance improvements to Kaiser, using distinct kernel
and user Process Context Identifiers to minimize the TLB flushing.
[This work actually all from Dave Hansen 2017-0
On Sat, Dec 30, 2017 at 10:01:58PM +0100, Jernej Skrabec wrote:
> This commit adds all necessary compatibles and descriptions needed to
> implement A83T HDMI pipeline.
>
> Mixer is already properly described, so only compatible is added.
>
> However, A83T TCON1, which is connected to HDMI, doesn'
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
While trying to get our gold link to work, four cleanups:
matched the gdt_page declaration to its definition;
in fiddling unsuccessfully with PERCPU_INPUT(), lined up backslashes;
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
There's a 0x1000 in various places, which looks better with a name.
Signed-off-by: Hugh Dickins
Signed-off-by: Greg Kroah-Hartman
---
arch/x86/entry/entry_64.S |4 ++--
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
kaiser_add_user_map() took no notice when kaiser_pagetable_walk() failed.
And avoid its might_sleep() when atomic (though atomic at present unused).
Signed-off-by: Hugh Dickins
S
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Mainly deleting a surfeit of blank lines, and reflowing header comment.
Signed-off-by: Hugh Dickins
Signed-off-by: Greg Kroah-Hartman
---
arch/x86/include/asm/kaiser.h | 32 +
501 - 600 of 956 matches
Mail list logo
