[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAJfpeguO_jt=fR+kMkmbJDtbD9f-+fAafkmS+CbE0qE_Z2wFug@mail.gmail.com>
Date: Thu, 29 Aug 2024 15:21:30 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Hanna Czenczek <hreitz@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-doc@...r.kernel.org, virtualization@...ts.linux.dev,
Miklos Szeredi <mszeredi@...hat.com>, German Maglione <gmaglione@...hat.com>,
Stefan Hajnoczi <stefanha@...hat.com>, Eugenio Pérez <eperezma@...hat.com>,
Jonathan Corbet <corbet@....net>, Vivek Goyal <vgoyal@...hat.com>
Subject: Re: [PATCH 0/2] virtio-fs: Add 'file' mount option
On Thu, 29 Aug 2024 at 15:11, Hanna Czenczek <hreitz@...hat.com> wrote:
> Hm, I thought we set some things in fuse_mount and fuse_conn in there that are then queried by fuse_send_init()... Maybe the only thing fuse_send_init() needs is fm->sb->s_bdi->ra_pages for max_readahead.
Yes, that definitely needs special treatment.
> Sounds simple. Do you think semantically it’s find to block here? We’d only do it for virtio-fs, so a denial-of-service may not be of concern here.
It should be okay. AFAIK all network filesystems block mount(2) until
setup is complete.
Thanks,
Miklos
Powered by blists - more mailing lists