4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Neal Cardwell
commit 600647d467c6d04b3954b41a6ee1795b5ae00550 upstream.
Fix BBR so that upon notification of a loss recovery undo BBR resets
long-term bandwidth sampling.
Under high reordering
Em Wed, Jan 03, 2018 at 03:33:07PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Jan 03, 2018 at 03:27:01PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Continuing investigation...
> >
> > After applying the fallback patch to allow new tools to work with older
> > kernels:
> >
> > [root@
This patch convert the stm32-cryp driver to the new crypto engine API.
Signed-off-by: Corentin Labbe
---
drivers/crypto/stm32/stm32-cryp.c | 21 -
1 file changed, 16 insertions(+), 5 deletions(-)
diff --git a/drivers/crypto/stm32/stm32-cryp.c
b/drivers/crypto/stm32/stm32-cry
4.4-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
This patch convert the stm32-hash driver to the new crypto engine API.
Signed-off-by: Corentin Labbe
---
drivers/crypto/stm32/stm32-hash.c | 18 +-
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/drivers/crypto/stm32/stm32-hash.c
b/drivers/crypto/stm32/stm32-hash.
Hello
The current crypto_engine support only ahash and ablkcipher request.
My first patch which try to add skcipher was Nacked, it will add too many
functions
and adding other algs(aead, asymetric_key) will make the situation worst.
This patchset remove all algs specific stuff and now only proce
4.4-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/
This patch convert the driver to the new crypto engine API.
Signed-off-by: Corentin Labbe
---
drivers/crypto/virtio/virtio_crypto_algs.c | 10 +++---
drivers/crypto/virtio/virtio_crypto_common.h | 3 +--
drivers/crypto/virtio/virtio_crypto_core.c | 3 ---
3 files changed, 8 insertions(
From: Markus Elfring
Date: Wed, 3 Jan 2018 21:02:17 +0100
Replace the specification of data structures by variable references
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by: Markus
4.4-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.4-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
The crypto engine could actually only enqueue hash and ablkcipher request.
This patch permit it to enqueue any type of crypto_async_request.
Signed-off-by: Corentin Labbe
---
crypto/crypto_engine.c | 230
include/crypto/engine.h | 59 +++
Signed-off-by: Corentin Labbe
---
Documentation/crypto/crypto_engine.rst | 46 ++
1 file changed, 46 insertions(+)
create mode 100644 Documentation/crypto/crypto_engine.rst
diff --git a/Documentation/crypto/crypto_engine.rst
b/Documentation/crypto/crypto_engine.
4.4-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.4-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.4-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.4-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.4-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
4.4-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.4-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-
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
Merged fixes and cleanups, rebased to 4.4.89 tree (no 5-level paging).
Signed-off-by: Hugh Dickins
Acked-by: Jiri Kosina
Signed-off-by: Greg Kroah-Hartman
---
arch/x86/entry/en
4.4-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.4-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
On 01/03, Chao Yu wrote:
> If we need an array with variable size in the end of structure, we
> can utilize flexible array feature which is supported in C99, so
> let's change sit_nat_version_bitmap[] to flexible array in struct
> f2fs_checkpoint for readability.
>
> Signed-off-by: Chao Yu
> ---
4.4-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
4.4-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.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
Synthetic filesystem mempressure testing has shown softlockups, with
hour-long page allocation stalls, and pgd_alloc() trying for order:1
with __GFP_REPEAT in one of the backtraces
4.4-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.
4.4-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.4-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.4-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.4-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.4-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;
From: Markus Elfring
Date: Wed, 3 Jan 2018 20:55:10 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/net/wireless/marvell/libertas_tf/if_usb.c | 1 -
1 file changed
From: Kieran Bingham
The Linux UVC driver has long provided adequate performance capabilities for
web-cams and low data rate video devices in Linux while resolutions were low.
Modern USB cameras are now capable of high data rates thanks to USB3 with
1080p, and even 4k capture resolutions support
From: Kieran Bingham
We currently store three separate arrays for each URB reference we hold.
Objectify the data needed to track URBs into a single uvc_urb structure,
allowing better object management and tracking of the URB.
All accesses to the data pointers through stream, are converted to us
From: Kieran Bingham
The URB completion handlers currently reference the stream context.
Now that each URB has its own context structure, convert the decode (and
one encode) functions to utilise this context for URB management.
Signed-off-by: Kieran Bingham
Reviewed-by: Laurent Pinchart
---
From: Kieran Bingham
The URB completion operation obtains the current buffer by reading
directly into the queue internal interface.
Protect this queue abstraction by providing a helper
uvc_queue_get_current_buffer() which can be used by both the decode
task, and the uvc_queue_next_buffer() funct
From: Kieran Bingham
The buffer queue interface currently operates sequentially, processing
buffers after they have fully completed.
In preparation for supporting parallel tasks operating on the buffers,
we will need to support buffers being processed on multiple CPUs.
Adapt the uvc_queue_next_
From: Kieran Bingham
Newer high definition cameras, and cameras with multiple lenses such as
the range of stereovision cameras now available have ever increasing
data rates.
The inclusion of a variable length packet header in URB packets mean
that we must memcpy the frame data out to our destina
From: Kieran Bingham
Both uvc_start_streaming(), and uvc_stop_streaming() are called from
userspace context. As such, they do not need to save the IRQ state, and
can use spin_lock_irq() and spin_unlock_irq() respectively.
Signed-off-by: Kieran Bingham
---
drivers/media/usb/uvc/uvc_queue.c | 10
4.4-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(
Beacuse of PTI, I decided to test 4.15-rc6 on most of my test machines.
And I happened to notice a radeon problem on RV250 era card with no
monitor attached. 4.15-rc1 and earlier kernels did not show these
errors, not kernels between rc1 and rc6 have been tested yet.
The messages in dmes are st
After commit fc8dffd379ca ("cpu/hotplug: Convert hotplug locking to
percpu rwsem") get_online_cpus() must be non-recursive.
Cpu hotplug is already locked for read in tg_set_cfs_bandwidth() and
static_key_slow_inc() in cfs_bandwidth_usage_inc() locks it again.
Switch to cpus_read_[un]lock() and st
On Wed, Jan 3, 2018 at 6:36 PM, Ard Biesheuvel
wrote:
> On 3 January 2018 at 16:37, Arnd Bergmann wrote:
>> On Fri, Dec 22, 2017 at 4:47 PM, Ard Biesheuvel
>> wrote:
>>
>> A minimal patch would be to disable UBSAN specifically for aes-generic.c
>> for gcc-7.2+ but not gcc-8 to avoid the potenti
For fixing cpu_hotplug_lock recursion in tg_set_cfs_bandwidth().
Signed-off-by: Konstantin Khlebnikov
---
include/linux/jump_label.h | 12
kernel/jump_label.c| 18 +-
2 files changed, 25 insertions(+), 5 deletions(-)
diff --git a/include/linux/jump_label
cpu_tss_rw was declared with the macro
DECLARE_PER_CPU_PAGE_ALIGNED
but then defined with the macro
DEFINE_PER_CPU_SHARED_ALIGNED
leading to section mismatch warnings. Prefer the macro
DEFINE_PER_CPU_PAGE_ALIGNED
Suggested-by: Thomas Gleixner
Signed-off-by: Nick Desaulniers
---
arch/x86/ke
On Sat, Dec 30, 2017 at 10:42:49PM +0100, Jann Horn wrote:
> On Sat, Dec 30, 2017 at 6:57 PM, Dan Aloni wrote:
> > From: Dan Aloni
> >
> > Hi All,
> >
> > There has been a lot of progress in recent times regarding the removal
> > of sensitive information from dmesg (pointers, etc.), so I figured
On 01/03/2018 12:21 PM, Dan Aloni wrote:
> 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
>>> +
On Mon, Jan 01, 2018 at 03:33:40PM +0100, Paul Cercueil wrote:
> This header provides clock numbers for the ingenic,tcu
> DT binding.
>
> Signed-off-by: Paul Cercueil
> ---
> include/dt-bindings/clock/ingenic,tcu.h | 23 +++
> 1 file changed, 23 insertions(+)
> create mode 1
From: Markus Elfring
Date: Wed, 3 Jan 2018 21:45:19 +0100
Omit extra messages for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/mtd/inftlmount.c | 15 ++-
1 file changed, 2 insert
03.01.2018, 21:57, "Cong Wang" :
> On Tue, Jan 2, 2018 at 3:58 PM, syzbot
> wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> 61233580f1f33c50e159c50e24d80ffd2ba2e06b
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
>> compiler: gcc (GCC) 7.1.1 2017062
On Mon, Jan 01, 2018 at 03:33:41PM +0100, Paul Cercueil wrote:
> This simple driver handles the IRQ chip of the TCU
> (Timer Counter Unit) of the JZ47xx Ingenic SoCs.
>
> Signed-off-by: Paul Cercueil
> ---
> .../bindings/interrupt-controller/ingenic,tcu.txt | 32 +
> drivers/irqchip/Kconfi
+++ Steven Rostedt [03/01/18 09:33 -0500]:
On Wed, 3 Jan 2018 02:40:47 +0100
Jessica Yu wrote:
Improve error handling when arming ftrace-based kprobes. Specifically, if
we fail to arm a ftrace-based kprobe, register_kprobe()/enable_kprobe()
should report an error instead of success. Previousl
On Mon, Jan 01, 2018 at 03:33:43PM +0100, Paul Cercueil wrote:
> This driver will use the TCU (Timer Counter Unit) present on the Ingenic
> JZ47xx SoCs to provide the kernel with a clocksource and timers.
>
> Signed-off-by: Paul Cercueil
> ---
> .../devicetree/bindings/timer/ingenic,tcu.txt
On Tue, Jan 02, 2018 at 04:25:04PM +0800, Greentime Hu wrote:
> From: Greentime Hu
>
> This patch adds nds32 L2 cache controller binding documents.
>
> Signed-off-by: Greentime Hu
> ---
> Documentation/devicetree/bindings/nds32/atl2c.txt | 29
> +
> 1 file changed, 29 in
On 1/3/2018 12:32 PM, Kieran Bingham wrote:
> From: Kieran Bingham
>
> The Linux UVC driver has long provided adequate performance capabilities for
> web-cams and low data rate video devices in Linux while resolutions were low.
>
> Modern USB cameras are now capable of high data rates thanks to
Possibly this recent patch in master fixes it:
d2950278d2 (xfrm: put policies when reusing pcpu xdst entry)
On 2018-01-03 13:57:25 +0100, Willy Tarreau wrote:
> On Tue, Jan 02, 2018 at 01:09:13PM -0800, Linus Torvalds wrote:
> > On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund wrote:
> > >
> > > I thought it'd be interesting to run a short benchmark to be able to
> > > estimate the impact of the PTI work
Hi Kishon,
Le 03/01/2018 à 10:14, Kishon Vijay Abraham I a écrit :
> Hi,
>
> On Saturday 30 December 2017 02:23 AM, Cyrille Pitchen wrote:
>> Hi Kishon,
>>
>> Le 28/12/2017 à 14:00, Kishon Vijay Abraham I a écrit :
>>> Hi Cyrille,
>>>
>>> On Monday 18 December 2017 11:46 PM, Cyrille Pitchen wrote
On Tue, Jan 02, 2018 at 10:19:42AM +0100, Rafał Miłecki wrote:
> I was wondering how platform bus handles order of strings in the
> "compatibility" property. After reading the code & testing it I
> realized it doesn't.
>
> The property should store strings ordered from the most specific to
> the m
On Tue, Jan 02, 2018 at 02:32:14PM +0530, Jagan Teki wrote:
> This adds support for the Ampire AM-800480AYTZQW-00H 7.0" WGA LCD,
> which can be supported by the simple panel driver.
>
> Signed-off-by: Jagan Teki
> ---
> .../display/panel/ampire,am-800480aytzqw-00h.txt | 7 ++
> drivers/gp
Hi Rob,
Dne sreda, 03. januar 2018 ob 21:21:54 CET je Rob Herring napisal(a):
> 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,
> Beacuse of PTI, I decided to test 4.15-rc6 on most of my test machines.
> And I happened to notice a radeon problem on RV250 era card with no
> monitor attached. 4.15-rc1 and earlier kernels did not show these
> errors, not kernels between rc1 and rc6 have been tested yet.
Sorry, I can not re
On Tue, Jan 02, 2018 at 04:17:24PM -0600, Bjorn Helgaas wrote:
> On Tue, Jan 02, 2018 at 06:53:52PM +0100, Romain Perier wrote:
> > The current PCI pool API are simple macro functions direct expanded to
> > the appropriate dma pool functions. The prototypes are almost the same
> > and semantically,
On Tue, Jan 02, 2018 at 11:18:17AM +0100, Geert Uytterhoeven wrote:
> If OF_FLATTREE=y, but OF_EARLY_FLATTREE=n:
>
> drivers/tty/serial/earlycon.o: In function `param_setup_earlycon':
> earlycon.c:(.init.text+0x3a4): undefined reference to
> `early_init_dt_scan_chosen_stdout'
>
> Fix thi
Commit 2b83ff96f51d ("led: core: Fix brightness setting when setting
delay_off=0")
replaced del_timer_sync(&led_cdev->blink_timer) with led_stop_software_blink(),
which in addition to the former also clears LED_BLINK_SW flag.
The fact that the function clears also blink_delay_on and blink_delay_o
Hi Fabio,
Thus wrote Fabio Estevam (feste...@gmail.com):
> I am not able to reproduce this problem on a imx25 pdk running 4.14.11
> or linux-next.
this is no surprise. The problem shows up only if the AWAKE bit in UART
Status Register 1 is set before we go into suspend. My understanding is
that
Hi,
Le mer. 3 janv. 2018 à 21:58, Rob Herring a écrit :
On Mon, Jan 01, 2018 at 03:33:41PM +0100, Paul Cercueil wrote:
This simple driver handles the IRQ chip of the TCU
(Timer Counter Unit) of the JZ47xx Ingenic SoCs.
Signed-off-by: Paul Cercueil
---
.../bindings/interrupt-controller
Hi Sakari,
thanks for review..
On Wed, Jan 03, 2018 at 12:11:32PM +0200, Sakari Ailus wrote:
> Hi Jacopo,
>
> Please see my comments below.
>
> On Tue, Jan 02, 2018 at 04:03:53PM +0100, Jacopo Mondi wrote:
> > ov7670 driver supports two optional properties supplied through platform
> > data, b
All right, here's the dmesg from the kernel compiled from drm-tip (in
sync with upstream at the time of the compilation earlier today), with
CONFIG_DRM_I915_DEBUG_GEM=y
I crashed it by opening 20+ xterm windows. Doesn't always do it though
(tried this before).
On Wed, Jan 03, 2018 at 11:31:31AM
On Wed, Jan 03, 2018 at 05:01:13PM +0100, Bartosz Golaszewski wrote:
> Hi Wolfram,
>
> The following changes since commit 30a7acd573899fd8b8ac39236eff6468b195ac7d:
>
> Linux 4.15-rc6 (2017-12-31 14:47:43 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/lin
Hi,
Le mer. 3 janv. 2018 à 22:08, Rob Herring a écrit :
On Mon, Jan 01, 2018 at 03:33:43PM +0100, Paul Cercueil wrote:
This driver will use the TCU (Timer Counter Unit) present on the
Ingenic
JZ47xx SoCs to provide the kernel with a clocksource and timers.
Signed-off-by: Paul Cercueil
-
On Wed, 2018-01-03 at 11:28 -0800, Mahesh Bandewar (महेश बंडेवार)
wrote:
> On Wed, Jan 3, 2018 at 12:45 AM, SF Markus Elfring
> wrote:
> > > > Omit an extra message for a memory allocation failure in this function.
> > > >
> > > > This issue was detected by using the Coccinelle software.
> > > >
On Wed, Jan 03, 2018 at 09:11:06PM +0100, Greg Kroah-Hartman wrote:
> 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
On 01/03/2018 10:52 AM, Thomas Gleixner wrote:
On Wed, 3 Jan 2018, Thomas Gleixner wrote:
On Wed, 3 Jan 2018, Lars Wendler wrote:
Am Wed, 3 Jan 2018 13:05:38 +0100 (CET)
schrieb Thomas Gleixner :
Also can you please try Linus v4.15-rc6 with PTI enabled so we can see
whether that's a backport
On Wed, Jan 3, 2018 at 10:52 AM, Thomas Gleixner wrote:
> On Wed, 3 Jan 2018, Thomas Gleixner wrote:
>
>> On Wed, 3 Jan 2018, Lars Wendler wrote:
>> > Am Wed, 3 Jan 2018 13:05:38 +0100 (CET)
>> > schrieb Thomas Gleixner :
>> > > Also can you please try Linus v4.15-rc6 with PTI enabled so we can se
Loan Offer at 3% Lowest Rate Get Now.
> On Jan 2, 2018, at 5:59 AM, Paolo Bonzini wrote:
>
> The FS and userspace GS bases are available in current->thread, while the
> kernel GS base is a percpu variable. Skip the expensive rdmsr and just
> get the values from memory.
That fsbase change is wrong: thread->fsbase is not guaranteed to
On Wed, 3 Jan 2018, Andy Lutomirski wrote:
> On Wed, Jan 3, 2018 at 10:52 AM, Thomas Gleixner wrote:
> > On Wed, 3 Jan 2018, Thomas Gleixner wrote:
> >
> >> On Wed, 3 Jan 2018, Lars Wendler wrote:
> >> > Am Wed, 3 Jan 2018 13:05:38 +0100 (CET)
> >> > schrieb Thomas Gleixner :
> >> > > Also can yo
On 01/03/2018 02:14 PM, Andy Lutomirski wrote:
> + /* Use %rsp as scratch reg. User ESP is stashed in r8 */
> + SWITCH_TO_KERNEL_CR3 scratch_reg=%rsp
> +
> + /* Switch to the kernel stack */
> movqPER_CPU_VAR(cpu_current_top_of_stack), %rsp
The stack is unreadable at
Commit-ID: d7732ba55c4b6a2da339bb12589c515830cfac2c
Gitweb: https://git.kernel.org/tip/d7732ba55c4b6a2da339bb12589c515830cfac2c
Author: Thomas Gleixner
AuthorDate: Wed, 3 Jan 2018 19:52:04 +0100
Committer: Thomas Gleixner
CommitDate: Wed, 3 Jan 2018 23:19:32 +0100
x86/pti: Switch to ke
Commit-ID: 2fd9c41aea47f4ad071accf94b94f94f2c4d31eb
Gitweb: https://git.kernel.org/tip/2fd9c41aea47f4ad071accf94b94f94f2c4d31eb
Author: Nick Desaulniers
AuthorDate: Wed, 3 Jan 2018 12:39:52 -0800
Committer: Thomas Gleixner
CommitDate: Wed, 3 Jan 2018 23:19:33 +0100
x86/process: Define
On Wed, Jan 03, 2018 at 04:48:33PM +0100, Ingo Molnar wrote:
> first please test the latest WIP.x86/pti branch which has a couple of fixes.
I'm still seeing the problem with that branch (3ffdeb1a02be, plus a couple
of local patches which shouldn't affect the resulting binary).
--Benjamin Gilbert
Hi all,
After merging the cifs tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from include/linux/seqlock.h:36:0,
from include/linux/time.h:6,
from include/linux/stat.h:19,
from include/linux/module.h:
On Wed, 3 Jan 2018, Benjamin Gilbert wrote:
> On Wed, Jan 03, 2018 at 04:48:33PM +0100, Ingo Molnar wrote:
> > first please test the latest WIP.x86/pti branch which has a couple of fixes.
>
> I'm still seeing the problem with that branch (3ffdeb1a02be, plus a couple
> of local patches which shoul
The driver apparently assumes that the device uses the same page size
as the CPU, but also assumes that this is 4096 bytes. On architectures
with a larger page size like 65536 bytes, we get a warning about an
integer overflow:
drivers/media/pci/intel/ipu3/ipu3-cio2.c: In function
'cio2_fbpt_entry
Recently, Google Project Zero discovered several classes of attack
against speculative execution. One of these, known as variant-1, allows
explicit bounds checks to be bypassed under speculation, providing an
arbitrary read gadget. Further details can be found on the GPZ blog [1]
and the Documentat
Under speculation, CPUs may mis-predict branches in bounds checks. Thus,
memory accesses under a bounds check may be speculated even if the
bounds check fails, providing a primitive for building a side channel.
The EBPF map code has a number of such bounds-checks accesses in
map_lookup_elem implem
Document the rationale and usage of the new nospec*() helpers.
Signed-off-by: Mark Rutland
Signed-off-by: Will Deacon
---
Documentation/speculation.txt | 99 +++
1 file changed, 99 insertions(+)
create mode 100644 Documentation/speculation.txt
diff --gi
This patch implements nospec_load() and nospec_ptr() for arm64,
following the recommended architectural sequence.
Signed-off-by: Mark Rutland
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/barrier.h | 61
1 file changed, 61 insertions(+)
diff --g
Under speculation, CPUs may mis-predict branches in bounds checks. Thus,
memory accesses under a bounds check may be speculated even if the
bounds check fails, providing a primitive for building a side channel.
This patch adds helpers which can be used to inhibit the use of
out-of-bounds pointers
While testing other changes, I discovered that gcc-7.2.1 produces badly
optimized code for aes_encrypt/aes_decrypt. This is especially true when
CONFIG_UBSAN_SANITIZE_ALL is enabled, where it leads to extremely
large stack usage that in turn might cause kernel stack overflows:
crypto/aes_generic.c
The uplink_rpriv variable was added at the start of the function but
only used inside of an #ifdef:
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c: In function
'mlx5e_route_lookup_ipv6':
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:1549:25: error: unused variable
'uplink_rpriv' [-Werror=unus
On Wed, Jan 3, 2018 at 5:47 PM, Ulf Hansson wrote:
> On 3 January 2018 at 10:26, Arnd Bergmann wrote:
>> The global array clashes with a newly added symbol of the same name:
>>
>> drivers/staging/ccree/cc_debugfs.o:(.data+0x0): multiple definition of
>> `debug_regs'
>> drivers/mmc/host/s3cmci.o:
I don't see this with gcc 5.4
Stephen,
Harmless to initialize flags here ... even if unneeded ... so if it
makes your life easier I don't mind initializes to 0. Let me know.
Wonder why it doesn't generate the warning on the various other places
in the fs that do the same thing?
On Wed, Jan 3, 20
On Wed, Jan 03, 2018 at 11:34:46PM +0100, Thomas Gleixner wrote:
> Can you please send me your .config and a full dmesg ?
I've attached a serial log from a local QEMU. I can rerun with a higher
loglevel if need be.
--Benjamin Gilbert
config-4.14.11.gz
Description: application/gzip
console.tx
The global array clashes with a newly added symbol of the same name:
drivers/staging/ccree/cc_debugfs.o:(.data+0x0): multiple definition of
`debug_regs'
drivers/mmc/host/s3cmci.o:(.data+0x70): first defined here
We should fix both, this one addresses the s3cmci driver by removing
the symbol from
Dear Email Owner.
I won $758.7Million Powerball Lottery in november last year, I am doing alot
of charity works worldwide, so i decided to give $950,000 USD each to 5 lucky
people worldwide, Your email was seleted from a date of internet E-mail users
which your ID came out as one of my lucky
On Wed, 3 Jan 2018, Benjamin Gilbert wrote:
> On Wed, Jan 03, 2018 at 11:34:46PM +0100, Thomas Gleixner wrote:
> > Can you please send me your .config and a full dmesg ?
>
> I've attached a serial log from a local QEMU. I can rerun with a higher
> loglevel if need be.
Thanks!
Cc'ing Andy who mi
601 - 700 of 956 matches
Mail list logo
