All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Bhumit Attarde <bhumitattarde1@gmail.com>
Cc: fstests <fstests@vger.kernel.org>, Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: Things to look out for while adding FUSE support to XFSTests
Date: Tue, 8 Jun 2021 10:12:05 +0300	[thread overview]
Message-ID: <CAOQ4uxiWtx_9PnW5TDGa4CaZPY87p6mzxE4AV4CQkDCNfrom0g@mail.gmail.com> (raw)
In-Reply-To: <CABKHH71xokLUpxx4QbLh=H1rGhrOJqOwvx8ZtUOtjyLBZeGmsA@mail.gmail.com>

On Mon, Jun 7, 2021 at 9:29 PM Bhumit Attarde <bhumitattarde1@gmail.com> wrote:
>
> Hello,
>
> I’m a Google Summer of Code[1] student developer at KDE working on
> integrating XFSTests with KDE’s KIO-FUSE[2]. KIO is a KDE framework
> that provides and implements abstractions for accessing various types
> of (virtual) filesystems in a cross-platform way. KIO-FUSE is a
> project that lets you mount remote locations on your machine locally
> using FUSE. We’re anticipating that integrating XFSTESTS with KIO-FUSE
> would help us uncover previously undetected bugs in KIO-FUSE and
> KIO-slaves[3] (ioslaves) as well as the various protocols themselves.
> You can read a brief summary of the project by visiting the following
> link: Integrating XFSTests with KDE KIO-FUSE[4].
>
> As a part of the project, I’ll be adding FUSE support to XFSTests.
> While a patch[5] was submitted for this, it seems to be abandoned. I’m
> aiming to build on the mentioned patch, improve & test it after
> rectifying the errors pointed out by the reviewer. Some main changes
> that I will be making are --
> I] changing $SUBTYP to $FUSE_SUBTYP
> II] removing the added check case in `scratch_cleanup_files()`
>
> Is there anything I should keep in mind or need to look out for while
> working on this?

You should address this question to the FUSE maintainer who also
happens to be the author of path [5] (CCed).

Thanks,
Amir.

>
> Thank you.
>
> Best,
> Bhumit Attarde
>
> [1] https://summerofcode.withgoogle.com/
> [2] https://invent.kde.org/system/kio-fuse
> [3] https://api.kde.org/4.14-api/kdelibs-apidocs/kioslave/html/index.html
> [4] https://summerofcode.withgoogle.com/projects/#6429306361741312
> [5] https://patchwork.kernel.org/project/linux-fsdevel/patch/20200108192504.GA893@miu.piliscsaba.redhat.com/

  reply	other threads:[~2021-06-08  7:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 18:27 Things to look out for while adding FUSE support to XFSTests Bhumit Attarde
2021-06-08  7:12 ` Amir Goldstein [this message]
2021-06-08  7:28   ` Miklos Szeredi

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=CAOQ4uxiWtx_9PnW5TDGa4CaZPY87p6mzxE4AV4CQkDCNfrom0g@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=bhumitattarde1@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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.