Re: [PATCH for v4.14] mm/userfaultfd: do not access vma->vm_mm after calling handle_userfault()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH for v4.14] mm/userfaultfd: do not access vma->vm_mm after calling handle_userfault()
From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 25 Nov 2020 12:58:13 +0100
Cc: stable@xxxxxxxxxxxxxxx, Andrea Arcangeli <aarcange@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Alexander Egorenkov <egorenar@xxxxxxxxxxxxx>, Heiko Carstens <hca@xxxxxxxxxxxxx>
In-reply-to: <20201123165258.80810-1-gerald.schaefer@linux.ibm.com>

On Mon, Nov 23, 2020 at 05:52:58PM +0100, Gerald Schaefer wrote:
> commit bfe8cc1db02ab243c62780f17fc57f65bde0afe1 upstream.
> 
> Alexander reported a syzkaller / KASAN finding on s390, see below for
> complete output.

<snip>

Both backports now queued up, thanks.

greg k-h

References:
- FAILED: patch "[PATCH] mm/userfaultfd: do not access vma->vm_mm after calling" failed to apply to 4.14-stable tree
  - From: gregkh
- [PATCH for v4.14] mm/userfaultfd: do not access vma->vm_mm after calling handle_userfault()
  - From: Gerald Schaefer

Prev by Date: Re: perf: Apply e9a6882f267a to v4.9 stable (fix for null-pointer dereference)
Next by Date: Re: [PATCH 5/5] memory: renesas-rpc-if: Fix a reference leak in rpcif_probe()
Previous by thread: [PATCH for v4.14] mm/userfaultfd: do not access vma->vm_mm after calling handle_userfault()
Next by thread: stable-rc/queue/4.14 build: 201 builds: 0 failed, 201 passed, 66 warnings (v4.14.208-53-g6539b73c949c)
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Kernel Development Newbies] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite Hiking] [Linux Kernel] [Linux SCSI]

Powered by Linux