mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ravishankar N <ravishankar@redhat.com>
To: Miklos Szeredi <mszeredi@redhat.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	fuse-devel <fuse-devel@lists.sourceforge.net>
Subject: Re: commit 0b5da8d: fuse: add support for SEEK_HOLE and SEEK_DATA in lseek
Date: Thu, 17 Nov 2016 07:04:26 +0530	[thread overview]
Message-ID: <2756c158-de24-01ac-8a52-4a9a332ff5e8@redhat.com> (raw)
In-Reply-To: <87d1hvmbjh.fsf@thinkpad.rath.org>

Hi Nikolaus,

On 11/17/2016 01:39 AM, Nikolaus Rath wrote:
> Hi Ravishankar,
>
> In commit 0b5da8d you added support for a new FUSE_LSEEK
> operation. However, as far as I can tell the corresponding userspace
> code never landed in libfuse.
>
> Do you have a corresponding patch for libfuse?
No, unfortunately. I only used gluster to test what I wrote.
>
> Looking at the commit message, I assume this functionality was added
> specifically for glusterfs which presumably does not use libfuse.

You're right, gluster has its own code [1].
> But
> even in that case it would be nice if you could Cc
> fuse-devel@lists.sourceforge.net
The discussion[2] actually did start on fuse-devel.
> so that someone else can add support
That would be great.
> for this. This is important because AFAIR the libfuse documentation is
> the only thing that comes close to an official documentation of the FUSE
> API.
>

Best regards,
Ravi


[1] 
https://github.com/gluster/glusterfs/blob/master/xlators/mount/fuse/src/fuse-bridge.c
[2] https://sourceforge.net/p/fuse/mailman/message/34227449/
> Best,
> -Nikolaus
>

      reply	other threads:[~2016-11-17  1:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 20:09 Nikolaus Rath
2016-11-17  1:34 ` Ravishankar N [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=2756c158-de24-01ac-8a52-4a9a332ff5e8@redhat.com \
    --to=ravishankar@redhat.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mszeredi@redhat.com \
    /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

all inboxes | Powered by JetHome®