All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qian Cai <cai@lca.pw>
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>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"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: Tue, 26 May 2020 08:19:37 -0400	[thread overview]
Message-ID: <3979FAE7-0119-4F82-A933-FC175781865C@lca.pw> (raw)
In-Reply-To: <CACT4Y+ap21MXTjR3wF+3NhxEtgnKSm09tMsUnbKy2_EKEgh0kg@mail.gmail.com>



> On May 26, 2020, at 8:09 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
> 
> +linux-next and XFS maintainers
> 
> Interesting. This seems to repeat reliably and this machine is not
> known for any misbehavior and it always happens on all XFS files.
> Did XFS get something that crashes gcc's?

Are you still seeing this in today’s linux-next? There was an issue had already been sorted out.

  reply	other threads:[~2020-05-26 12:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 16:57 linux-next build error (8) syzbot
2020-03-18 20:54 ` Dmitry Vyukov
2020-03-18 21:41   ` Paul E. McKenney
2020-03-19  7:13     ` Dmitry Vyukov
2020-03-19 15:04       ` Paul E. McKenney
2020-03-20 15:38         ` Dmitry Vyukov
2020-03-20 16:26           ` Paul E. McKenney
2020-03-20 16:34             ` Randy Dunlap
2020-03-20 17:04               ` Paul E. McKenney
2020-03-20 13:08       ` Dan Carpenter
2020-03-20 15:42         ` Dmitry Vyukov
     [not found] ` <3e1a0d59-4959-6250-9f81-3d6f75687c73@I-love.SAKURA.ne.jp>
2020-05-26 12:09   ` Dmitry Vyukov
2020-05-26 12:19     ` Qian Cai [this message]
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
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=3979FAE7-0119-4F82-A933-FC175781865C@lca.pw \
    --to=cai@lca.pw \
    --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=sfr@canb.auug.org.au \
    --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 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.