From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: koverstreet@google.com, bcrl@kvack.org
Subject: AIO free_ioctx WARN_ON triggered by fuzz-testing.
Date: Mon, 16 Sep 2013 16:16:44 -0400 [thread overview]
Message-ID: <20130916201644.GA21963@redhat.com> (raw)
Just hit this while running trinity for a few hours.
WARN_ON(atomic_read(&ctx->reqs_available) > ctx->nr_events - 1);
WARNING: CPU: 1 PID: 20990 at fs/aio.c:451 free_ioctx+0x25d/0x260()
Modules linked in: tun fuse snd_seq_dummy bridge stp hidp rfcomm bnep scsi_transport_iscsi ipt_ULOG nfnetlink can_bcm can_raw nfc caif_socket caif af_802154 phonet af_rxrpc bluetooth rfkill can llc2 pppoe pppox ppp_generic slhc irda crc_ccitt rds af_key rose x25 atm netrom appletalk ipx p8023 psnap p8022 llc ax25 xfs snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec e1000e snd_hwdep libcrc32c snd_seq coretemp hwmon x86_pkg_temp_thermal snd_seq_device kvm_intel kvm crct10dif_pclmul crc32c_intel ghash_clmulni_intel usb_debug snd_pcm serio_raw pcspkr microcode snd_page_alloc ptp snd_timer snd shpchp pps_core soundcore
CPU: 1 PID: 20990 Comm: kworker/1:1 Not tainted 3.11.0+ #78
Hardware name: Intel Corporation Shark Bay Client platform/Flathead Creek Crb, BIOS HSWLPTU1.86C.0109.R03.1301282055 01/28/2013
Workqueue: events free_ioctx
ffffffff81a405bf ffff8801be28bcb0 ffffffff81729187 0000000000000000
ffff8801be28bce8 ffffffff8105528d ffff8802242b6ec8 ffff8802242b6f40
ffff8801aa6c9000 ffff8802242b70a8 ffff8801be28bfd8 ffff8801be28bcf8
Call Trace:
[<ffffffff81729187>] dump_stack+0x4e/0x82
[<ffffffff8105528d>] warn_slowpath_common+0x7d/0xa0
[<ffffffff8105536a>] warn_slowpath_null+0x1a/0x20
[<ffffffff81217fed>] free_ioctx+0x25d/0x260
[<ffffffff81084aa0>] ? wake_up_atomic_t+0x30/0x30
[<ffffffff81077c01>] process_one_work+0x211/0x710
[<ffffffff81077b95>] ? process_one_work+0x1a5/0x710
[<ffffffff8107821d>] worker_thread+0x11d/0x3a0
[<ffffffff81078100>] ? process_one_work+0x710/0x710
[<ffffffff8108379d>] kthread+0xed/0x100
[<ffffffff810836b0>] ? insert_kthread_work+0x80/0x80
[<ffffffff8173c05c>] ret_from_fork+0x7c/0xb0
[<ffffffff810836b0>] ? insert_kthread_work+0x80/0x80
---[ end trace cd0b6492eb84e062 ]---
reply other threads:[~2013-09-16 20:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130916201644.GA21963@redhat.com \
--to=davej@redhat.com \
--cc=bcrl@kvack.org \
--cc=koverstreet@google.com \
--cc=linux-kernel@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.