public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	linux-xfs <linux-xfs@vger.kernel.org>,
	syzbot <syzbot+792dec47d693ccdc05a0@syzkaller.appspotmail.com>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: linux-next build error (8)
Date: Wed, 27 May 2020 16:25:14 +1000	[thread overview]
Message-ID: <20200527162514.404ae1da@canb.auug.org.au> (raw)
In-Reply-To: <CACT4Y+ZFsQq65jZDRKA1rQs-GM9cyFu9Cn6y=kbx21mCryBqqA@mail.gmail.com>

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

Hi Dmitry,

On Wed, 27 May 2020 07:41:15 +0200 Dmitry Vyukov <dvyukov@google.com> wrote:
>
> On Wed, May 27, 2020 at 1:33 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > What version of linux-next is this?  There was a problem last week with
> > some changes in the tip tree that caused large memory usage.  
> 
> Hi Stephen,
> 
> Detailed info about each syzbot crash is always available over the
> dashboard link:

Thanks.  As others have said, this has been taken care of - the
problematic commits were dropped from next-2020522 and the fixes
appeared in next-20200525.

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2020-05-27  6:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000000000000ae2ab305a123f146@google.com>
     [not found] ` <3e1a0d59-4959-6250-9f81-3d6f75687c73@I-love.SAKURA.ne.jp>
2020-05-26 12:09   ` linux-next build error (8) Dmitry Vyukov
2020-05-26 12:19     ` Qian Cai
2020-05-26 12:28       ` Dmitry Vyukov
2020-05-26 12:41         ` Qian Cai
2020-05-26 12:44           ` Tetsuo Handa
2020-05-26 12:50             ` Qian Cai
2020-05-26 12:59               ` Tetsuo Handa
2020-05-26 13:26           ` Dmitry Vyukov
2020-05-26 13:49             ` Qian Cai
2020-05-26 14:04               ` Dmitry Vyukov
2020-05-26 23:33     ` Stephen Rothwell
2020-05-27  5:41       ` Dmitry Vyukov
2020-05-27  6:25         ` Stephen Rothwell [this message]
2020-05-27  6:38           ` Dmitry Vyukov

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=20200527162514.404ae1da@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=darrick.wong@oracle.com \
    --cc=dvyukov@google.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=syzbot+792dec47d693ccdc05a0@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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