linux-kernel - [PATCH 0/2] mm: Two small fixes for recent syzbot reports

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20200408014010.80428-1-peterx@redhat.com>
Date:   Tue,  7 Apr 2020 21:40:08 -0400
From:   Peter Xu <peterx@...hat.com>
To:     linux-kernel@...r.kernel.org,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-mm@...ck.org
Cc:     Andrew Morton <akpm@...ux-foundation.org>, peterx@...hat.com
Subject: [PATCH 0/2] mm: Two small fixes for recent syzbot reports

The two patches should fix below syzbot reports:

  BUG: unable to handle kernel paging request in kernel_get_mempolicy
  https://lore.kernel.org/lkml/0000000000002b25f105a2a3434d@google.com/

  WARNING: bad unlock balance in __get_user_pages_remote
  https://lore.kernel.org/lkml/00000000000005c65d05a2b90e70@google.com/

Note that the 1st patch also applied two extra small changes comparing
to when posted on the list in that: (1) it squashed an "interupt"
spelling error that Andrew has pointed out when picked up, and (2) it
also initializes the "page" pointer to NULL.  But I'm fairly confident
it shouldn't affect the correctness of the patch.

The 2nd patch is exactly the patch posted previously.

Thanks,

Peter Xu (2):
  mm/mempolicy: Allow lookup_node() to handle fatal signal
  mm/gup: Mark lock taken only after a successful retake

 mm/gup.c       | 2 +-
 mm/mempolicy.c | 7 +++++--
 2 files changed, 6 insertions(+), 3 deletions(-)

-- 
2.24.1