From: syzbot <syzbot+d154ec99402c6f628887@syzkaller.appspotmail.com>
To: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
yuchao0@huawei.com
Subject: Re: kernel BUG at fs/f2fs/node.c:LINE!
Date: Mon, 23 Apr 2018 23:42:02 -0700 [thread overview]
Message-ID: <000000000000ae37a6056a9273f6@google.com> (raw)
In-Reply-To: <20180424062000.GA57884@jaegeuk-macbookpro.roam.corp.google.com>
Hello,
syzbot tried to test the proposed patch but build/boot failed:
failed to create VM pool: failed to create GCE image: failed to get create
image operation operation-1524552040215-56a926ecc71d9-3edfeb8b-8abca81c:
googleapi: Error 403: Rate Limit Exceeded, rateLimitExceeded
Tested on
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/dev commit
b549e322861b99f1862fb5f08dfb5e5753a38635 (Sat Apr 21 06:44:59 2018 +0000)
f2fs: check cap_resource only for data blocks
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
Patch: https://syzkaller.appspot.com/x/patch.diff?id=5565179303559168
Kernel config:
https://syzkaller.appspot.com/x/.config?id=1808800213120130118
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+d154ec99402c6f628887@syzkaller.appspotmail.com>
To: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
yuchao0@huawei.com
Subject: Re: kernel BUG at fs/f2fs/node.c:LINE!
Date: Mon, 23 Apr 2018 23:42:02 -0700 [thread overview]
Message-ID: <000000000000ae37a6056a9273f6@google.com> (raw)
In-Reply-To: <20180424062000.GA57884@jaegeuk-macbookpro.roam.corp.google.com>
Hello,
syzbot tried to test the proposed patch but build/boot failed:
failed to create VM pool: failed to create GCE image: failed to get create
image operation operation-1524552040215-56a926ecc71d9-3edfeb8b-8abca81c:
googleapi: Error 403: Rate Limit Exceeded, rateLimitExceeded
Tested on
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/dev commit
b549e322861b99f1862fb5f08dfb5e5753a38635 (Sat Apr 21 06:44:59 2018 +0000)
f2fs: check cap_resource only for data blocks
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
Patch: https://syzkaller.appspot.com/x/patch.diff?id=5565179303559168
Kernel config:
https://syzkaller.appspot.com/x/.config?id=1808800213120130118
next prev parent reply other threads:[~2018-04-24 6:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 13:02 kernel BUG at fs/f2fs/node.c:LINE! syzbot
2018-04-21 13:02 ` syzbot
2018-04-24 6:01 ` Jaegeuk Kim
2018-04-24 6:04 ` syzbot
2018-04-24 6:20 ` Jaegeuk Kim
2018-04-24 6:42 ` syzbot [this message]
2018-04-24 6:42 ` syzbot
2018-04-24 14:28 ` Dmitry Vyukov via Linux-f2fs-devel
2018-04-24 14:28 ` Dmitry Vyukov
2018-04-24 14:42 ` syzbot
2018-04-24 16:27 ` Jaegeuk Kim
2018-04-24 16:27 ` Jaegeuk Kim
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=000000000000ae37a6056a9273f6@google.com \
--to=syzbot+d154ec99402c6f628887@syzkaller.appspotmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yuchao0@huawei.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.