From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+9e27a75a8c24f3fe75c1@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] memory leak in xas_nomem
Date: Mon, 30 May 2022 02:07:36 +0100 [thread overview]
Message-ID: <YpQY2HMaXEaTMNZe@casper.infradead.org> (raw)
In-Reply-To: <20220529163935.5118b4f91e2c5c3378ab326f@linux-foundation.org>
On Sun, May 29, 2022 at 04:39:35PM -0700, Andrew Morton wrote:
> On Fri, 27 May 2022 20:20:21 -0700 syzbot <syzbot+9e27a75a8c24f3fe75c1@syzkaller.appspotmail.com> wrote:
>
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit: 1e57930e9f40 Merge tag 'rcu.2022.05.19a' of git://git.kern..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=17afc423f00000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=5757003cb23a31a7
> > dashboard link: https://syzkaller.appspot.com/bug?extid=9e27a75a8c24f3fe75c1
> > compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16bc056ef00000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=116b7d9df00000
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+9e27a75a8c24f3fe75c1@syzkaller.appspotmail.com
> >
> > BUG: memory leak
>
> (hopefully cc's willy)
Thanks; I saw it, I've just been busy this weekend.
https://www.sportstats.ca/display-results.xhtml?raceid=114439&status=results&bib=3970
next prev parent reply other threads:[~2022-05-30 1:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 3:20 [syzbot] memory leak in xas_nomem syzbot
2022-05-29 23:39 ` Andrew Morton
2022-05-30 1:07 ` Matthew Wilcox [this message]
2022-06-08 19:37 ` Matthew Wilcox
2022-06-08 19:54 ` 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=YpQY2HMaXEaTMNZe@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+9e27a75a8c24f3fe75c1@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).