From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Alex Shi <alex.shi@linux.alibaba.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
syzbot <syzbot+826543256ed3b8c37f62@syzkaller.appspotmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Cgroups <cgroups@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>, Michal Hocko <mhocko@kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: linux-next test error: BUG: using __this_cpu_read() in preemptible code in __mod_memcg_state
Date: Sat, 18 Apr 2020 18:13:58 +1000 [thread overview]
Message-ID: <20200418181358.0a761486@canb.auug.org.au> (raw)
In-Reply-To: <CACT4Y+ZsAgq0M=xUzrXTOYaaJfr_BrD8_5R5bhzr9k29jDSC+w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
Hi Dmitry,
On Sat, 18 Apr 2020 10:02:36 +0200 Dmitry Vyukov <dvyukov@google.com> wrote:
> >
> > #syz invalid
>
> This is correct, thanks!
>
> You may now see "Status: closed as invalid on 2020/04/18 07:51" at:
> https://syzkaller.appspot.com/bug?extid=826543256ed3b8c37f62
>
> It does not show up as "open" and if this will happen again syzbot
> will report it (rather than assume it's still the old bug happening).
OK, good, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-04-18 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 21:05 linux-next test error: BUG: using __this_cpu_read() in preemptible code in __mod_memcg_state syzbot
2020-03-09 9:24 ` Kirill A. Shutemov
2020-03-09 9:56 ` Alex Shi
2020-03-09 13:26 ` Alex Shi
2020-04-18 7:04 ` Dmitry Vyukov
2020-04-18 7:43 ` Stephen Rothwell
2020-04-18 7:50 ` Stephen Rothwell
2020-04-18 8:02 ` Dmitry Vyukov
2020-04-18 8:13 ` 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=20200418181358.0a761486@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@linux.alibaba.com \
--cc=cgroups@vger.kernel.org \
--cc=dvyukov@google.com \
--cc=hannes@cmpxchg.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=syzbot+826543256ed3b8c37f62@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vdavydov.dev@gmail.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).