Re: [PATCHv4 4/6] Allow setting FD_CLOEXEC flag for new sockets

> +union indirect_params {
> +  struct {
> +    int flags;
> +  } file_flags;
> +};

Have you given thought to having to perform compat translation on this?
  Today it's only copied directly from the user pointer into the union
in the task_struct.

I'd love if we could only use fixed-width fields in the interface to
avoid the compat nonsense.

- z
-
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: [PATCHv4 4/6] Allow setting FD_CLOEXEC flag for new sockets
    • From: Ulrich Drepper <[email protected]>

• References:
  • [PATCHv4 4/6] Allow setting FD_CLOEXEC flag for new sockets
    • From: Ulrich Drepper <[email protected]>

• Prev by Date: Re: [PATCH]intel-iommu-PMEN support
• Next by Date: Re: [PATCH 3/3] PNP cleanups - Version 2 - Pass struct pnp_dev to pnp_clean_resource_table for cleanup reasons
• Previous by thread: [PATCHv4 4/6] Allow setting FD_CLOEXEC flag for new sockets
• Next by thread: Re: [PATCHv4 4/6] Allow setting FD_CLOEXEC flag for new sockets
• 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]