public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: syzbot <syzbot+f96cbc69d9803e663664@syzkaller•appspotmail.com>
Cc: 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, syzkaller-bugs@googlegroups•com,
	vdavydov.dev@gmail•com
Subject: Re: linux-next boot error: WARNING in mem_cgroup_css_alloc
Date: Fri, 14 Aug 2020 09:25:02 +1000	[thread overview]
Message-ID: <20200814092502.34c48995@canb.auug.org.au> (raw)
In-Reply-To: <0000000000001c467c05acbf3196@google.com>

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

Hi,

On Thu, 13 Aug 2020 02:47:26 -0700 syzbot <syzbot+f96cbc69d9803e663664@syzkaller•appspotmail.com> wrote:
>
> syzbot found the following issue on:
> 
> HEAD commit:    e6d113ac Add linux-next specific files for 20200813
> git tree:       linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=11db9fd6900000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=2055bd0d83d5ee16
> dashboard link: https://syzkaller.appspot.com/bug?extid=f96cbc69d9803e663664
> compiler:       gcc (GCC) 10.1.0-syz 20200507
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+f96cbc69d9803e663664@syzkaller•appspotmail.com

#syz fix: mm: memcontrol: fix warning when allocating the root cgroup

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-08-13 23:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13  9:47 linux-next boot error: WARNING in mem_cgroup_css_alloc syzbot
2020-08-13 23:25 ` Stephen Rothwell [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=20200814092502.34c48995@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=cgroups@vger$(echo .)kernel.org \
    --cc=hannes@cmpxchg$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mm@kvack$(echo .)org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mhocko@kernel$(echo .)org \
    --cc=syzbot+f96cbc69d9803e663664@syzkaller$(echo .)appspotmail.com \
    --cc=syzkaller-bugs@googlegroups$(echo .)com \
    --cc=vdavydov.dev@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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