Re: [PATCH] Protection for exploiting null dereference using mmap

On Tue, Jun 05, 2007 at 05:00:51PM -0400, James Morris wrote:
> This should be an unsigned long.
> 
> I wonder if the default should be for this value to be zero (i.e. preserve 
> existing behavior).  It could break binaries, albeit potentially insecure 

Agreed - DOSemu type apps and lrmi need to map at zero for vm86
-
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] Protection for exploiting null dereference using mmap
  - From: Eric Paris <[email protected]>
- Re: [PATCH] Protection for exploiting null dereference using mmap
  - From: Eric Paris <[email protected]>

References:
- [PATCH] Protection for exploiting null dereference using mmap
  - From: Eric Paris <[email protected]>
- Re: [PATCH] Protection for exploiting null dereference using mmap
  - From: James Morris <[email protected]>

Prev by Date: Re: [PATCH] lguest-fix-divide-error-implement-sched_clock
Next by Date: Re: [PATCH 03/22] 2.6.22-rc3 perfmon2 : new system calls support
Previous by thread: Re: [PATCH] Protection for exploiting null dereference using mmap
Next by thread: Re: [PATCH] Protection for exploiting null dereference using mmap
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]