From: syzbot <syzbot+f8c45ccc7d5d45fc5965@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dvyukov@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
songmuchun@bytedance.com, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org
Subject: Re: [syzbot] general protection fault in list_lru_add
Date: Thu, 24 Mar 2022 21:49:09 -0700 [thread overview]
Message-ID: <000000000000ecb9b105db03ae4d@google.com> (raw)
In-Reply-To: <CAMZfGtVHSWAzLN+FzOL0MyedcXc5UAaGuc4OufUwkLzWe2KWvQ@mail.gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
mm/list_lru.c:88:14: error: implicit declaration of function 'memcg_kmem_id' [-Werror=implicit-function-declaration]
Tested on:
commit: 5abc1e37 mm: list_lru: allocate list_lru_one only when..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
dashboard link: https://syzkaller.appspot.com/bug?extid=f8c45ccc7d5d45fc5965
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=12e2d063700000
next prev parent reply other threads:[~2022-03-25 4:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 22:03 [syzbot] general protection fault in list_lru_add syzbot
2022-03-23 23:11 ` Linus Torvalds
2022-03-24 2:18 ` Muchun Song
2022-03-24 3:05 ` Linus Torvalds
2022-03-24 8:44 ` Muchun Song
2022-03-24 8:50 ` Dmitry Vyukov
2022-03-24 16:12 ` Muchun Song
2022-03-24 16:18 ` Dmitry Vyukov
2022-03-24 16:38 ` Muchun Song
2022-03-24 19:44 ` syzbot
2022-03-24 19:41 ` syzbot
2022-03-24 19:45 ` Linus Torvalds
2022-03-24 19:47 ` Linus Torvalds
2022-03-25 1:43 ` Muchun Song
2022-03-25 4:49 ` syzbot [this message]
2022-03-25 5:47 ` Fabio M. De Francesco
2022-03-25 12:37 ` Fabio M. De Francesco
2022-03-25 9:51 ` Muchun Song
2022-03-25 20:29 ` Linus Torvalds
2022-03-27 5:27 ` Muchun Song
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=000000000000ecb9b105db03ae4d@google.com \
--to=syzbot+f8c45ccc7d5d45fc5965@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=songmuchun@bytedance.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.