From: Jeff Moyer <jmoyer@redhat.com>
To: Sage Weil <sage@newdream.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Null pointer deref in do_aio_submit
Date: Fri, 10 Feb 2012 13:06:32 -0500 [thread overview]
Message-ID: <x49zkcqo95j.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1202100921580.1530@cobra.newdream.net> (Sage Weil's message of "Fri, 10 Feb 2012 09:27:51 -0800 (PST)")
Sage Weil <sage@newdream.net> writes:
> I hit the following under a reasonable simple aio workload:
>
> - reasonably heavy load
> - lots of threads doing buffered io to random files
> - one thread submitting O_DIRECT aio to a single file (journal), all
> sequential (wrapping), 100MB
> - probably somewhere between 1 and 50 aios outstanding at any point in
> time.
>
> The kernel was v3.2 mainline, plus unrelated btrfs and ceph patches.
>
> Is this a known issue? Any other information that would be helpful?
I don't know for sure, but could you test with the following commit?
69e4747ee9727d660b88d7e1efe0f4afcb35db1b
Also, I'll note that it looks like you are doing O_SYNC + O_DIRECT AIO.
I'm curious to know what apps use that particular combination. Is this
just a test case, or do you have an app which does this in production?
Cheers,
Jeff
next prev parent reply other threads:[~2012-02-10 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 17:27 Null pointer deref in do_aio_submit Sage Weil
2012-02-10 18:06 ` Jeff Moyer [this message]
2012-02-10 20:42 ` Sage Weil
2012-02-10 20:53 ` Jeff Moyer
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=x49zkcqo95j.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sage@newdream.net \
/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