From: Vegard Nossum <vegard.nossum@oracle.com>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Open bugs found by fuzzing as of 2016-07-30
Date: Sat, 30 Jul 2016 15:04:43 +0200 [thread overview]
Message-ID: <579CA5EB.1070707@oracle.com> (raw)
Hi,
It's been two weeks since I posted the first list of bugs found using
AFL: https://www.spinics.net/lists/linux-ext4/msg53022.html
With a bunch of ext4 patches going into 4.8 we're down from 15 to 6
with current linus/master:
1. general protection fault: 0000 [#1] KASAN
http://139.162.151.198/f/ext4/57be666646a37e9821d52bc64846a3b3b785ee7a
2. kernel BUG at fs/buffer.c:3061!
http://139.162.151.198/f/ext4/7df880da89c82579c15ca8bc786a3467ca9c47f7
3. kernel BUG at fs/ext4/inode.c:3738!
http://139.162.151.198/f/ext4/5bdefda69f39b2f2c56d9b67d5b7d9e2cc8dfd5f
(discussion: https://www.spinics.net/lists/linux-ext4/msg53032.html)
4. kernel BUG at fs/ext4/mballoc.c:3191!
http://139.162.151.198/f/ext4/34284738d67f0405325b2c43211c56020b9d0211
5. kernel BUG at fs/jbd2/commit.c:825!
http://139.162.151.198/f/ext4/3143febf7925bd1ea398bd1a775551133bd69ffd
6. WARNING: CPU: 0 PID: 58 at fs/ext4/ext4.h:2748
ext4_block_bitmap_csum_set+0x358/0x600
http://139.162.151.198/f/ext4/9628c19aff0bbaaae4149a03486305c7f6cd7523
Vegard
next reply other threads:[~2016-07-30 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 13:04 Vegard Nossum [this message]
2016-07-30 18:39 ` Open bugs found by fuzzing as of 2016-07-30 nborisov
2016-07-30 19:25 ` Vegard Nossum
2016-07-31 4:37 ` Theodore Ts'o
2016-08-03 5:43 ` Greg KH
2016-08-04 2:58 ` Theodore Ts'o
2016-08-01 4:55 ` Theodore Ts'o
2016-08-01 7:33 ` Vegard Nossum
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=579CA5EB.1070707@oracle.com \
--to=vegard.nossum@oracle.com \
--cc=linux-ext4@vger.kernel.org \
/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.