From: Nick Piggin <npiggin@gmail.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: NFS dio aio bug
Date: Fri, 14 Jan 2011 12:29:18 +1100 [thread overview]
Message-ID: <AANLkTinjkvVySCA93F+p66KrTuqMfMF064ggNSg0yauX@mail.gmail.com> (raw)
Hi Trond,
I'm getting use after frees in aio code in NFS
[ 2703.396766] Call Trace:
[ 2703.396858] [<ffffffff8100b057>] ? native_sched_clock+0x27/0x80
[ 2703.396959] [<ffffffff8108509e>] ? put_lock_stats+0xe/0x40
[ 2703.397058] [<ffffffff81088348>] ? lock_release_holdtime+0xa8/0x140
[ 2703.397159] [<ffffffff8108a2a5>] lock_acquire+0x95/0x1b0
[ 2703.397260] [<ffffffff811627db>] ? aio_put_req+0x2b/0x60
[ 2703.397361] [<ffffffff81039701>] ? get_parent_ip+0x11/0x50
[ 2703.397464] [<ffffffff81612a31>] _raw_spin_lock_irq+0x41/0x80
[ 2703.397564] [<ffffffff811627db>] ? aio_put_req+0x2b/0x60
[ 2703.397662] [<ffffffff811627db>] aio_put_req+0x2b/0x60
[ 2703.397761] [<ffffffff811647fe>] do_io_submit+0x2be/0x7c0
[ 2703.397895] [<ffffffff81164d0b>] sys_io_submit+0xb/0x10
[ 2703.397995] [<ffffffff8100307b>] system_call_fastpath+0x16/0x1b
Adding some tracing, it is due to nfs completing the request then
returning something other than -EIOCBQUEUED, so aio.c
also completes the request.
Thanks,
Nick
next reply other threads:[~2011-01-14 1:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 1:29 Nick Piggin [this message]
2011-01-14 16:08 ` NFS dio aio bug Chuck Lever
[not found] ` <4E70BD9B-DB23-42EC-B28D-998E16FEC189-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2011-01-14 21:48 ` Nick Piggin
[not found] ` <AANLkTikE8CT=6XQn550Cw6V0B7GWezpeUrhctFN8vSE7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-01-18 22:01 ` Chuck Lever
[not found] ` <D4A3D0CB-DA82-4E2E-BCAD-B03108AA4284-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2011-01-19 2:56 ` Wengang Wang
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=AANLkTinjkvVySCA93F+p66KrTuqMfMF064ggNSg0yauX@mail.gmail.com \
--to=npiggin@gmail.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).