linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: syzbot <syzbot+ef4ecf7b6bdc4157bfa4@syzkaller.appspotmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	cgroups@vger.kernel.org, Johannes Weiner <hannes@cmpxchg.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Michal Hocko <mhocko@kernel.org>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Muchun Song <songmuchun@bytedance.com>,
	syzkaller-bugs@googlegroups.com, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [syzbot] [cgroups?] [mm?] WARNING in folio_memcg
Date: Mon, 19 Aug 2024 16:05:41 +0800	[thread overview]
Message-ID: <B2518F6C-7652-4AE5-AE57-39380E79932D@linux.dev> (raw)
In-Reply-To: <0000000000006f7e4d0620042b96@google.com>



> On Aug 19, 2024, at 15:22, syzbot <syzbot+ef4ecf7b6bdc4157bfa4@syzkaller.appspotmail.com> wrote:
> 
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    367b5c3d53e5 Add linux-next specific files for 20240816
> git tree:       linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=11be396b980000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=61ba6f3b22ee5467
> dashboard link: https://syzkaller.appspot.com/bug?extid=ef4ecf7b6bdc4157bfa4
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=147469f5980000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=153c5ad5980000
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/0b1b4e3cad3c/disk-367b5c3d.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/5bb090f7813c/vmlinux-367b5c3d.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/6674cb0709b1/bzImage-367b5c3d.xz
> 
> The issue was bisected to:
> 
> commit ebadc95608dc3ee87ad4e5dc4f2c665c709bb899
> Author: Muchun Song <songmuchun@bytedance.com>
> Date:   Wed Aug 14 09:34:15 2024 +0000
> 
>    mm: kmem: add lockdep assertion to obj_cgroup_memcg
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=170875f5980000
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=148875f5980000
> console output: https://syzkaller.appspot.com/x/log.txt?x=108875f5980000
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+ef4ecf7b6bdc4157bfa4@syzkaller.appspotmail.com

Thanks for your report. I've fixed this in patch [1].

[1] https://lore.kernel.org/linux-mm/20240819080415.44964-1-songmuchun@bytedance.com/T/#u



      reply	other threads:[~2024-08-19  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  7:22 [syzbot] [cgroups?] [mm?] WARNING in folio_memcg syzbot
2024-08-19  8:05 ` Muchun Song [this message]

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=B2518F6C-7652-4AE5-AE57-39380E79932D@linux.dev \
    --to=muchun.song@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=songmuchun@bytedance.com \
    --cc=syzbot+ef4ecf7b6bdc4157bfa4@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vbabka@suse.cz \
    /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).