Re: [PATCH v2] fcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jeff Layton <jlayton@xxxxxxxxxx>
Subject: Re: [PATCH v2] fcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall
From: Vitaly Lipatov <lav@xxxxxxxxxxx>
Date: Wed, 15 Nov 2017 21:31:41 +0300
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, hch@xxxxxx, bfields@xxxxxxxxxxxx, Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20171115180345.8219-1-jlayton@kernel.org>
Organization: Etersoft
User-agent: Roundcube Webmail/1.3.3

Jeff Layton писал 15.11.17 21:03:
...

With this, we no longer need COMPAT_OFF_T_MAX either, so remove it.

COMPAT_LOFF_T_MAX

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

Follow-Ups:
- Re: [PATCH v2] fcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall
  - From: Jeff Layton

References:
- [PATCH v2] fcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall
  - From: Jeff Layton

Prev by Date: [PATCH v2] fcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall
Next by Date: Re: [patch] dax: fix PMD faults on zero-length files
Previous by thread: [PATCH v2] fcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall
Next by thread: Re: [PATCH v2] fcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux