[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181229031416.GH5864@mit.edu>
Date: Fri, 28 Dec 2018 22:14:16 -0500
From: "Theodore Y. Ts'o" <tytso@....edu>
To: Peter Maydell <peter.maydell@...aro.org>,
Andreas Dilger <adilger@...ger.ca>,
Florian Weimer <fw@...eb.enyo.de>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
Ext4 Developers List <linux-ext4@...r.kernel.org>,
<lucho@...kov.net>, <libc-alpha@...rceware.org>,
Arnd Bergmann <arnd@...db.de>, <ericvh@...il.com>,
<hpa@...or.com>,
lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>,
QEMU Developers <qemu-devel@...gnu.org>, <rminnich@...dia.gov>,
<v9fs-developer@...ts.sourceforge.net>
Subject: Re: [Qemu-devel] d_off field in struct dirent and 32-on-64 emulation
On Sat, Dec 29, 2018 at 03:37:21AM +0100, Dominique Martinet wrote:
> > Are there going to be cases where a process or a thread will sometimes
> > want the 64-bit interface, and sometimes want the 32-bit interface?
> > Or is it always going to be one or the other? I wonder if we could
> > simply add a new flag to the process personality(2) flags.
>
> That would likely work for qemu user, but the qemu system+9p case is
> going to be more painful..
> More precisely, the 9p protocol does not plan for anything other than
> 64bit offset so if the vfs needs to hand out a 32bit offset we'll need
> to make a correspondance table between the 32bit offsets we hand off and
> the 64bit ones to use; unless some flag can be passed at lopen to tell
> the server to always hand out 32bit offsets for this directory... And if
> we do that then 9p servers will need a way to use both APIs in parallel
> for both types of directories.
How about if we add a fcntl(2) mediated flag, which is tied to a
struct file? Would that be more or less painful for 9p and qemu
system+9p?
- Ted
Powered by blists - more mailing lists