From: syzbot <syzbot+a526c269335f529d25c8-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
To: akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org,
sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org,
syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state
Date: Fri, 25 Feb 2022 23:23:23 -0800 [thread overview]
Message-ID: <000000000000c7fde605d8e6b085@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 06aeb1495c39 Add linux-next specific files for 20220225
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17a69c8e700000
kernel config: https://syzkaller.appspot.com/x/.config?x=8d8bf144f45f9b3
dashboard link: https://syzkaller.appspot.com/bug?extid=a526c269335f529d25c8
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a526c269335f529d25c8-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3590 at mm/memcontrol.c:749 __mod_memcg_lruvec_state+0x1ab/0x220
Modules linked in:
CPU: 1 PID: 3590 Comm: syz-fuzzer Not tainted 5.17.0-rc5-next-20220225-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__mod_memcg_lruvec_state+0x1ab/0x220
Code: bb 23 92 0e 48 c7 c7 e0 b6 d9 89 e8 af d9 95 07 65 c7 05 f4 c8 37 7e 00 00 00 00 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 <0f> 0b e9 a6 fe ff ff 4c 89 f6 48 c7 c7 60 63 ee 8b e8 8f d3 45 02
RSP: 0000:ffffc900039efbc0 EFLAGS: 00010202
RAX: 0000000000000206 RBX: 0000000000000200 RCX: ffffffff81aafa53
RDX: 1ffff1100218fa8d RSI: 000000000000001c RDI: ffff888010c7d468
RBP: ffff888010c7d000 R08: 0000000000000001 R09: ffffffff8ba144e7
R10: fffffbfff174289c R11: 0000000000000001 R12: 000000000000001c
R13: ffff88813fe38000 R14: ffff88813fe38000 R15: ffff88813fffa000
FS: 000000c0001d2c90(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c000e00000 CR3: 000000001cfb0000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__mod_lruvec_page_state+0x1e5/0x3e0
page_add_new_anon_rmap+0x2e5/0x930
do_huge_pmd_anonymous_page+0x102c/0x2350
__handle_mm_fault+0x2a66/0x4110
handle_mm_fault+0x1c8/0x790
do_user_addr_fault+0x489/0x11c0
exc_page_fault+0x9e/0x180
asm_exc_page_fault+0x1e/0x30
RIP: 0033:0x465e33
Code: 00 00 c5 fe 6f 06 c5 fe 6f 4e 20 c5 fe 6f 56 40 c5 fe 6f 5e 60 48 81 c6 80 00 00 00 c5 fd e7 07 c5 fd e7 4f 20 c5 fd e7 57 40 <c5> fd e7 5f 60 48 81 c7 80 00 00 00 48 81 eb 80 00 00 00 77 b5 0f
RSP: 002b:000000c0003533b8 EFLAGS: 00010202
RAX: 000000c000db4000 RBX: 0000000000423fe0 RCX: 000000c001224000
RDX: 000000c001224001 RSI: 000000c000990020 RDI: 000000c000dfffa0
RBP: 000000c000353418 R08: 000000c000db4000 R09: 0000000000000000
R10: 0000000000000020 R11: 0000000000000206 R12: 000000c000243f18
R13: 000000000000002e R14: 000000c0000001a0 R15: 0000000000000000
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+a526c269335f529d25c8@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, cgroups@vger.kernel.org,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org,
mhocko@kernel.org, roman.gushchin@linux.dev,
sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com
Subject: [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state
Date: Fri, 25 Feb 2022 23:23:23 -0800 [thread overview]
Message-ID: <000000000000c7fde605d8e6b085@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 06aeb1495c39 Add linux-next specific files for 20220225
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17a69c8e700000
kernel config: https://syzkaller.appspot.com/x/.config?x=8d8bf144f45f9b3
dashboard link: https://syzkaller.appspot.com/bug?extid=a526c269335f529d25c8
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a526c269335f529d25c8@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3590 at mm/memcontrol.c:749 __mod_memcg_lruvec_state+0x1ab/0x220
Modules linked in:
CPU: 1 PID: 3590 Comm: syz-fuzzer Not tainted 5.17.0-rc5-next-20220225-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__mod_memcg_lruvec_state+0x1ab/0x220
Code: bb 23 92 0e 48 c7 c7 e0 b6 d9 89 e8 af d9 95 07 65 c7 05 f4 c8 37 7e 00 00 00 00 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 <0f> 0b e9 a6 fe ff ff 4c 89 f6 48 c7 c7 60 63 ee 8b e8 8f d3 45 02
RSP: 0000:ffffc900039efbc0 EFLAGS: 00010202
RAX: 0000000000000206 RBX: 0000000000000200 RCX: ffffffff81aafa53
RDX: 1ffff1100218fa8d RSI: 000000000000001c RDI: ffff888010c7d468
RBP: ffff888010c7d000 R08: 0000000000000001 R09: ffffffff8ba144e7
R10: fffffbfff174289c R11: 0000000000000001 R12: 000000000000001c
R13: ffff88813fe38000 R14: ffff88813fe38000 R15: ffff88813fffa000
FS: 000000c0001d2c90(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c000e00000 CR3: 000000001cfb0000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__mod_lruvec_page_state+0x1e5/0x3e0
page_add_new_anon_rmap+0x2e5/0x930
do_huge_pmd_anonymous_page+0x102c/0x2350
__handle_mm_fault+0x2a66/0x4110
handle_mm_fault+0x1c8/0x790
do_user_addr_fault+0x489/0x11c0
exc_page_fault+0x9e/0x180
asm_exc_page_fault+0x1e/0x30
RIP: 0033:0x465e33
Code: 00 00 c5 fe 6f 06 c5 fe 6f 4e 20 c5 fe 6f 56 40 c5 fe 6f 5e 60 48 81 c6 80 00 00 00 c5 fd e7 07 c5 fd e7 4f 20 c5 fd e7 57 40 <c5> fd e7 5f 60 48 81 c7 80 00 00 00 48 81 eb 80 00 00 00 77 b5 0f
RSP: 002b:000000c0003533b8 EFLAGS: 00010202
RAX: 000000c000db4000 RBX: 0000000000423fe0 RCX: 000000c001224000
RDX: 000000c001224001 RSI: 000000c000990020 RDI: 000000c000dfffa0
RBP: 000000c000353418 R08: 000000c000db4000 R09: 0000000000000000
R10: 0000000000000020 R11: 0000000000000206 R12: 000000c000243f18
R13: 000000000000002e R14: 000000c0000001a0 R15: 0000000000000000
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2022-02-26 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 7:23 syzbot [this message]
2022-02-26 7:23 ` [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state syzbot
[not found] ` <000000000000c7fde605d8e6b085-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2022-02-28 6:09 ` Andrew Morton
2022-02-28 6:09 ` Andrew Morton
[not found] ` <20220227220943.490fb7b5f7c57d872f9523cb-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2022-02-28 11:06 ` Sebastian Andrzej Siewior
2022-02-28 11:06 ` Sebastian Andrzej Siewior
[not found] ` <YhysqzlMHWTXLR4B-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2022-02-28 11:06 ` syzbot
2022-02-28 11:06 ` 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=000000000000c7fde605d8e6b085@google.com \
--to=syzbot+a526c269335f529d25c8-pl5pbv+gp7p466ipttivnc23woclnbcfal8byrjmmd8@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org \
--cc=syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.