From: Nikolaus Rath <Nikolaus@rath.org>
To: fuse-devel <fuse-devel@lists.sourceforge.net>,
Miklos Szeredi <mszeredi@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Sahitya Tummala <stummala@codeaurora.org>,
David Sheets <david.sheets@docker.com>,
Tahsin Erdogan <tahsin@google.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: Reading from fuse pipe fails with EBADFD
Date: Tue, 04 Dec 2018 09:03:16 +0000 [thread overview]
Message-ID: <875zw97jfv.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <8736rmb728.fsf@vostro.rath.org> (Nikolaus Rath's message of "Tue, 27 Nov 2018 20:26:39 +0000")
Hi,
Really no one any suggestion for debugging this?
(Adding some more people who recently worked on fs/fuse)
Best,
-Nikolaus
On Nov 27 2018, Nikolaus Rath <Nikolaus@rath.org> wrote:
> Hi,
>
> When testing FUSE under heavy load, I am occasionally getting EBADFD
> errors when reading from the fuse pipe.
>
> Does anyone have an idea what might cause this, and how to debug it
> further?
>
> Unfortunately I can't tell if this happens upon read() or upon
> splice(). I've extended the code now, so the next time it happens I will
> be able to tell.
>
> I am testing with kernel 4.15 from Ubuntu Bionic.
>
> So far this has happened twice in about 3 hours of testing. For the
> testing, I am repeatedly running the same 3 workloads, without
> remounting. Each workload takes ~ 15-30 seconds.
>
> Best,
> -Nikolaus
>
> --
> GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
>
> »Time flies like an arrow, fruit flies like a Banana.«
--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next prev parent reply other threads:[~2018-12-04 9:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 20:26 Reading from fuse pipe fails with EBADFD Nikolaus Rath
2018-12-04 9:03 ` Nikolaus Rath [this message]
2018-12-04 9:10 ` Miklos Szeredi
2018-12-04 19:02 ` [fuse-devel] " Nikolaus Rath
2018-12-10 9:19 ` Miklos Szeredi
2018-12-26 22:30 ` Nikolaus Rath
2018-12-31 10:56 ` Nikolaus Rath
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=875zw97jfv.fsf@thinkpad.rath.org \
--to=nikolaus@rath.org \
--cc=david.sheets@docker.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=stummala@codeaurora.org \
--cc=tahsin@google.com \
--cc=viro@zeniv.linux.org.uk \
/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.