lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 11 Jan 2019 23:21:48 +0100
From:   Pavel Machek <>
To:     "Theodore Y. Ts'o" <>, NeilBrown <>,
        Andy Lutomirski <>,
        Andreas Dilger <>,
        Peter Zijlstra <>,
        Dmitry Safonov <>,
        "H. Peter Anvin" <>,
        Denys Vlasenko <>,
        Linus Torvalds <>,
        Borislav Petkov <>, Ingo Molnar <>,
        Brian Gerst <>,
        LKML <>,
        Thomas Gleixner <>,,
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...

(cesky, pictures)

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)

Powered by blists - more mailing lists