f83159f188
List of vulnerabilities is documented on: http://vuxml.freebsd.org/freebsd/8c2b2f11-0ebe-11e6-b55e-b499baebfeaf.html CVE IDs see below. PR: 206998 Submitted by: mokhi64@gmail.com (maintainer) Reviewed by: rootservice@gmail.com Approved by: mokhi64@gmail.com (maintainer) MFH: 2016Q2 Security: CVE-2016-0705 CVE-2016-0639 CVE-2015-3194 CVE-2016-0640 CVE-2016-0641 CVE-2016-3461 CVE-2016-2047 CVE-2016-0642 CVE-2016-0643 CVE-2016-0644 CVE-2016-0646 CVE-2016-0647 CVE-2016-0648 CVE-2016-0649 CVE-2016-0650 CVE-2016-0652 CVE-2016-0653 CVE-2016-0654 CVE-2016-0655 CVE-2016-0656 CVE-2016-0657 CVE-2016-0658 CVE-2016-0651 CVE-2016-0659 CVE-2016-0661 CVE-2016-0662 CVE-2016-0663 CVE-2016-0665 CVE-2016-0666 CVE-2016-0667 CVE-2016-0668
23 lines
985 B
C
23 lines
985 B
C
--- storage/myisam/mi_dynrec.c.orig 2016-03-28 18:06:12 UTC
|
|
+++ storage/myisam/mi_dynrec.c
|
|
@@ -65,18 +65,13 @@ my_bool mi_dynmap_file(MI_INFO *info, my
|
|
DBUG_RETURN(1);
|
|
}
|
|
/*
|
|
- I wonder if it is good to use MAP_NORESERVE. From the Linux man page:
|
|
- MAP_NORESERVE
|
|
- Do not reserve swap space for this mapping. When swap space is
|
|
- reserved, one has the guarantee that it is possible to modify the
|
|
- mapping. When swap space is not reserved one might get SIGSEGV
|
|
- upon a write if no physical memory is available.
|
|
+ MAP_NORESERVE is unimplemented in FreeBSD
|
|
*/
|
|
info->s->file_map= (uchar*)
|
|
my_mmap(0, (size_t) size,
|
|
info->s->mode==O_RDONLY ? PROT_READ :
|
|
PROT_READ | PROT_WRITE,
|
|
- MAP_SHARED | MAP_NORESERVE,
|
|
+ MAP_SHARED,
|
|
info->dfile, 0L);
|
|
if (info->s->file_map == (uchar*) MAP_FAILED)
|
|
{
|