[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190111222148.GA3855@amd>
Date: Fri, 11 Jan 2019 23:21:48 +0100
From: Pavel Machek <pavel@....cz>
To: "Theodore Y. Ts'o" <tytso@....edu>, NeilBrown <neilb@...e.com>,
Andy Lutomirski <luto@...nel.org>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Peter Zijlstra <peterz@...radead.org>,
Dmitry Safonov <dsafonov@...tuozzo.com>,
"H. Peter Anvin" <hpa@...or.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...nel.org>,
Brian Gerst <brgerst@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
linux-tip-commits@...r.kernel.org, jsimmons@...radead.org
Subject: Re: in_compat_syscall() returns from kernel thread for X86_32.
On Wed 2018-10-24 10:32:37, Theodore Y. Ts'o wrote:
> On Wed, Oct 24, 2018 at 09:15:34AM -0400, Theodore Y. Ts'o wrote:
> > At least for ext4, the primary problem is that we want to use a 64-bit
> > telldir/seekdir cookie if all 64-bits will make it to user space, and
> > a 32-bit telldir cookie if only 32 bits will make it userspace. This
> > impacts NFS as well because if there are people who are still using
> > NFSv2, which has 32-bit directory offsets, we need to constrain the
> > telldir/seekdir cookies we give to NFS to be a 32 has as opposed to a
> > 64-bit hash.
>
> Are there anyone still using NFSv2, BTW? One way of making the
> problem *much* easier to sovle would be to drop NFSv2 support. :-)
NFSv2 is now in "unexcpected" places such as U-Boot bootloader. I'm
pretty sure someone still uses it...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists