linux-kernel - Re: KASAN: null-ptr-deref Read in reclaim

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:   Tue, 12 Mar 2019 07:08:38 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     syzbot <syzbot+fa11f9da42b46cea3b4a@...kaller.appspotmail.com>,
        cgroups@...r.kernel.org, Johannes Weiner <hannes@...xchg.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux-MM <linux-mm@...ck.org>, Michal Hocko <mhocko@...nel.org>,
        Michal Hocko <mhocko@...e.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Shakeel Butt <shakeelb@...gle.com>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Vladimir Davydov <vdavydov.dev@...il.com>
Subject: Re: KASAN: null-ptr-deref Read in reclaim_high

On Tue, Mar 12, 2019 at 12:37 AM Andrew Morton
<akpm@...ux-foundation.org> wrote:
>
> On Mon, 11 Mar 2019 06:08:01 -0700 syzbot <syzbot+fa11f9da42b46cea3b4a@...kaller.appspotmail.com> wrote:
>
> > syzbot has bisected this bug to:
> >
> > commit 29a4b8e275d1f10c51c7891362877ef6cffae9e7
> > Author: Shakeel Butt <shakeelb@...gle.com>
> > Date:   Wed Jan 9 22:02:21 2019 +0000
> >
> >      memcg: schedule high reclaim for remote memcgs on high_work
> >
> > bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=155bf5db200000
> > start commit:   29a4b8e2 memcg: schedule high reclaim for remote memcgs on..
> > git tree:       linux-next
> > final crash:    https://syzkaller.appspot.com/x/report.txt?x=175bf5db200000
> > console output: https://syzkaller.appspot.com/x/log.txt?x=135bf5db200000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=611f89e5b6868db
> > dashboard link: https://syzkaller.appspot.com/bug?extid=fa11f9da42b46cea3b4a
> > userspace arch: amd64
> > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14259017400000
> > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=141630a0c00000
> >
> > Reported-by: syzbot+fa11f9da42b46cea3b4a@...kaller.appspotmail.com
> > Fixes: 29a4b8e2 ("memcg: schedule high reclaim for remote memcgs on
> > high_work")
>
> The following patch
> memcg-schedule-high-reclaim-for-remote-memcgs-on-high_work-v3.patch
> might have fixed this.  Was it applied?

Hi Andrew,

You mean if the patch was applied during the bisection?
No, it wasn't. Bisection is very specifically done on the same tree
where the bug was hit. There are already too many factors that make
the result flaky/wrong/inconclusive without changing the tree state.
Now, if syzbot would know about any pending fix for this bug, then it
would not do the bisection at all. But it have not seen any patch in
upstream/linux-next with the Reported-by tag, nor it received any syz
fix commands for this bugs. Should have been it aware of the fix? How?

Thanks