Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Andrey Kuzmin <andrey.v.kuzmin@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Shared files with thread=1: func=xfer, err=Bad file descriptor
Date: Tue, 01 Apr 2014 12:59:35 -0600	[thread overview]
Message-ID: <533B0C97.8080007@kernel.dk> (raw)
In-Reply-To: <CANvN+eknc=9Ncooprk6AUqOTvkju_JpYivy7EL5xRXka2qv+6g@mail.gmail.com>

On 04/01/2014 12:56 PM, Andrey Kuzmin wrote:
> Seems to have fixed it: EBADF does not show up anymore even in a 120s run.

Great, it has been committed. The issue was that fio would mistakenly 
not assign shadow_fd on that one alloc, hence it would think it was fd 0 
and close it. And when open(2) then (validly) started handing out 
untracked fd 0, then all hell broke lose.

-- 
Jens Axboe



      reply	other threads:[~2014-04-01 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01  1:08 Shared files with thread=1: func=xfer, err=Bad file descriptor Andrey Kuzmin
2014-04-01 14:31 ` Jens Axboe
2014-04-01 15:56   ` Andrey Kuzmin
2014-04-01 18:24     ` Jens Axboe
2014-04-01 18:56       ` Andrey Kuzmin
2014-04-01 18:59         ` Jens Axboe [this message]

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=533B0C97.8080007@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=andrey.v.kuzmin@gmail.com \
    --cc=fio@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