From: Jens Axboe <jens.axboe@oracle.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sys_splice crashes in 2.6.19rc1 during autotest
Date: Thu, 5 Oct 2006 17:58:46 +0200 [thread overview]
Message-ID: <20061005155844.GC5170@kernel.dk> (raw)
In-Reply-To: <200610051725.53183.ak@suse.de>
On Thu, Oct 05 2006, Andi Kleen wrote:
>
> I was running autotest on 2.6.19rc1+x86_64 patchkit and I ended up with a BUG()
> below sys_splice while running some IO test there.
>
> This was a debugging kernel with PREEMPTION and various other
> debugging options enabled.
>
> The system ran out of disk space during the test so that
> might have been related and I ended up with a "fio" process
> in D. Also the system was confused afterwards with rm
> oopsing etc.
>
> File system was reiserfs.
Can you pass me the fio job file you used?
--
Jens Axboe
next prev parent reply other threads:[~2006-10-05 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 15:25 sys_splice crashes in 2.6.19rc1 during autotest Andi Kleen
2006-10-05 15:58 ` Jens Axboe [this message]
2006-10-05 16:08 ` Andi Kleen
2006-10-06 6:43 ` Jens Axboe
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=20061005155844.GC5170@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=ak@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox