[PATCH 0/2] use symbolic constants in generic lseek code

The generic lseek code in fs/read_write.c uses hardcoded values for
SEEK_{SET,CUR,END}.

Patch 1 fixes the case statements to use the symbolic constants in
include/linux/fs.h, and should not be at all controversial.

Patch 2 adds a SEEK_MAX and uses it to validate user arguments.  This makes
the code a little cleaner and also enables future extensions (such as
SEEK_DATA and SEEK_HOLE).  If anyone has a problem with this, please speak up.

-- Chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH 0/2] use symbolic constants in generic lseek code
  - From: David Howells <[email protected]>
- [PATCH 2/2] use use SEEK_MAX to validate user lseek arguments
  - From: "Chris Snook" <[email protected]>
- [PATCH 1/2] use symbolic constants in generic lseek code
  - From: "Chris Snook" <[email protected]>

Prev by Date: Re: [PATCH 0/7] containers (V7): Generic Process Containers
Next by Date: Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
Previous by thread: [PATCH] UML utrace support, step 1
Next by thread: [PATCH 1/2] use symbolic constants in generic lseek code
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]