Arun Sharma <[email protected]> wrote:
>
> Allow shmctl to find out if a shmid corresponds to a HUGETLB segment
>
> Signed-off-by: Arun Sharma <[email protected]>
> Acked-by: Rohit Seth <[email protected]>
>
> --- a/ipc/shm.c Tue Nov 8 20:58:38 2005
> +++ b/ipc/shm.c Wed Nov 9 10:26:37 2005
> @@ -197,7 +197,7 @@
> return -ENOMEM;
>
> shp->shm_perm.key = key;
> - shp->shm_flags = (shmflg & S_IRWXUGO);
> + shp->shm_flags = (shmflg & (S_IRWXUGO | SHM_HUGETLB));
> shp->mlock_user = NULL;
>
> shp->shm_perm.security = NULL;
I dunno. The manpage says:
The highlighted fields in the member shm_perm can be set:
struct ipc_perm {
...
ushort mode; /* lower 9 bits of access modes */
...
};
So if an application used to do:
if (perm.mode == 0666)
it will now break, because we've gone and set bit 9 on hugetlb segments.
-
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/
[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]