linux-kernel - Re: [PATCH] fcntl: don't cap l_start and l_end values for F

lists.openwall.net		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 linux-hardening linux-cve-announce 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]

Message-ID: <f3c22b98e9c5da1b873829d5271462c6@etersoft.ru>
Date:   Wed, 15 Nov 2017 16:36:43 +0300
From:   Vitaly Lipatov <lav@...rsoft.ru>
To:     Jeff Layton <jlayton@...nel.org>
Cc:     linux-fsdevel@...r.kernel.org, hch@....de, bfields@...ldses.org,
        Alexander Viro <viro@...iv.linux.org.uk>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fcntl: don't cap l_start and l_end values for F_GETLK64
 in compat syscall

Jeff Layton писал 15.11.17 16:17:
> From: Jeff Layton <jlayton@...hat.com>
> 
> Currently, we're capping the values too low in the F_GETLK64 case. The
> fields in that structure are 64-bit values, so we shouldn't need to any
> sort of fixup there.
> 
> Make sure we check that assumption at build time in the future however
> by ensuring that the sizes we're copying will fit.
Nice fix.
The only question I do not know answer is what is purpose of 
COMPAT_LOFF_T_MAX macro?

-- 
С уважением,
Виталий Липатов,
Etersoft