From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+fa11f9da42b46cea3b4a@syzkaller.appspotmail.com>,
cgroups@vger.kernel.org, Johannes Weiner <hannes@cmpxchg.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>, Michal Hocko <mhocko@kernel.org>,
Michal Hocko <mhocko@suse.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Shakeel Butt <shakeelb@google.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: KASAN: null-ptr-deref Read in reclaim_high
Date: Mon, 11 Mar 2019 23:25:41 -0700 [thread overview]
Message-ID: <20190311232541.db8571d2e3e0ca636785f31f@linux-foundation.org> (raw)
In-Reply-To: <CACT4Y+byKQSOCte3JS9XOnyr+aVSEFtBvLxG2-HUrZX3-82Hcg@mail.gmail.com>
On Tue, 12 Mar 2019 07:08:38 +0100 Dmitry Vyukov <dvyukov@google.com> wrote:
> On Tue, Mar 12, 2019 at 12:37 AM Andrew Morton
> <akpm@linux-foundation.org> wrote:
> >
> > On Mon, 11 Mar 2019 06:08:01 -0700 syzbot <syzbot+fa11f9da42b46cea3b4a@syzkaller.appspotmail.com> wrote:
> >
> > > syzbot has bisected this bug to:
> > >
> > > commit 29a4b8e275d1f10c51c7891362877ef6cffae9e7
> > > Author: Shakeel Butt <shakeelb@google.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@syzkaller.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?
memcg-schedule-high-reclaim-for-remote-memcgs-on-high_work-v3.patch was
added to linux-next on Jan 10. I take it that this bug was hit when
testing the entire linux-next tree, so we can assume that
memcg-schedule-high-reclaim-for-remote-memcgs-on-high_work-v3.patch
does not fix it, correct?
In which case, over to Shakeel!
next prev parent reply other threads:[~2019-03-12 6:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 13:08 syzbot
2019-03-11 23:37 ` Andrew Morton
2019-03-12 6:08 ` Dmitry Vyukov
2019-03-12 6:25 ` Andrew Morton [this message]
2019-03-12 6:43 ` Eric Biggers
2019-03-12 8:21 ` Dmitry Vyukov
2019-03-12 22:31 ` Eric Biggers
2019-03-13 8:12 ` Dmitry Vyukov
2019-03-12 8:33 ` Dmitry Vyukov
2019-03-12 13:45 ` Shakeel Butt
2019-03-12 14:44 ` Dmitry Vyukov
2019-03-12 22:50 ` Eric Biggers
2019-03-13 8:24 ` Dmitry Vyukov
2019-03-13 18:16 ` Eric Biggers
2019-03-19 13:52 ` Dmitry Vyukov
-- strict thread matches above, loose matches on Subject: below --
2019-01-10 17:03 syzbot
2019-01-10 17:03 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190311232541.db8571d2e3e0ca636785f31f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=dvyukov@google.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=sfr@canb.auug.org.au \
--cc=shakeelb@google.com \
--cc=syzbot+fa11f9da42b46cea3b4a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vdavydov.dev@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox