linux-kernel - Re: [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-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 8 Apr 2020 17:47:32 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Peter Xu <peterx@...hat.com>
Cc:     linux-kernel@...r.kernel.org,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-mm@...ck.org
Subject: Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports

On Tue,  7 Apr 2020 21:40:08 -0400 Peter Xu <peterx@...hat.com> wrote:

> 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/

(Is there an email address for the syzbot operators?)

sysbot does test linux-next, yet these patches sat in linux-next for a
month without a peep, but all hell broke loose when they hit Linus's
tree.  How could this have happened?

Possibly I've been carrying a later patch which fixed all this up, but
I'm not seeing anything like that.  Nothing at all against mm/gup.c.