From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Ossama Othman <ossama.othman@gmail.com>
Cc: mptcp@lists.linux.dev, Ossama Othman <ossama.othman@intel.com>
Subject: Re: [PATCH mptcp-next] mptcp: fix conflict with <netinet/in.h>
Date: Thu, 19 May 2022 17:05:08 -0700 (PDT) [thread overview]
Message-ID: <f4baa4-81e6-21df-80a5-13eb15317559@linux.intel.com> (raw)
In-Reply-To: <20220519153929.214331-1-ossama.othman@intel.com>
On Thu, 19 May 2022, Ossama Othman wrote:
> Including <linux/mptcp.h> before the C library <netinet/in.h> header
> causes symbol redefinition errors at compile-time due to duplicate
> declarations and definitions in the <linux/in.h> header included by
> <linux/mptcp.h>.
>
> Explicitly include <netinet/in.h> before <linux/in.h> in
> <linux/mptcp.h> when __KERNEL__ is not defined so that the C library
> compatibility logic in <linux/libc-compat.h> is enabled when including
> <linux/mptcp.h> in user space code.
>
> Signed-off-by: Ossama Othman <ossama.othman@intel.com>
Looks good to me, I think this makes things easier for userspace.
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
> ---
> include/uapi/linux/mptcp.h | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/include/uapi/linux/mptcp.h b/include/uapi/linux/mptcp.h
> index 921963589904..dfe19bf13f4c 100644
> --- a/include/uapi/linux/mptcp.h
> +++ b/include/uapi/linux/mptcp.h
> @@ -2,16 +2,17 @@
> #ifndef _UAPI_MPTCP_H
> #define _UAPI_MPTCP_H
>
> +#ifndef __KERNEL__
> +#include <netinet/in.h> /* for sockaddr_in and sockaddr_in6 */
> +#include <sys/socket.h> /* for struct sockaddr */
> +#endif
> +
> #include <linux/const.h>
> #include <linux/types.h>
> #include <linux/in.h> /* for sockaddr_in */
> #include <linux/in6.h> /* for sockaddr_in6 */
> #include <linux/socket.h> /* for sockaddr_storage and sa_family */
>
> -#ifndef __KERNEL__
> -#include <sys/socket.h> /* for struct sockaddr */
> -#endif
> -
> #define MPTCP_SUBFLOW_FLAG_MCAP_REM _BITUL(0)
> #define MPTCP_SUBFLOW_FLAG_MCAP_LOC _BITUL(1)
> #define MPTCP_SUBFLOW_FLAG_JOIN_REM _BITUL(2)
> --
> 2.34.1
>
>
>
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-05-20 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 15:39 [PATCH mptcp-next] mptcp: fix conflict with <netinet/in.h> Ossama Othman
2022-05-19 17:17 ` mptcp: fix conflict with <netinet/in.h>: Tests Results MPTCP CI
2022-05-20 0:05 ` Mat Martineau [this message]
2022-05-20 15:20 ` [PATCH mptcp-next] mptcp: fix conflict with <netinet/in.h> Matthieu Baerts
2022-05-21 0:18 ` Mat Martineau
2022-05-21 7:27 ` Matthieu Baerts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f4baa4-81e6-21df-80a5-13eb15317559@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=mptcp@lists.linux.dev \
--cc=ossama.othman@gmail.com \
--cc=ossama.othman@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.