From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] vhost: Drop linux/socket.h
Date: Fri, 16 Aug 2013 12:50:12 +0300 [thread overview]
Message-ID: <20130816095012.GA21547@redhat.com> (raw)
In-Reply-To: <20130816.003159.2033932881805410431.davem@davemloft.net>
On Fri, Aug 16, 2013 at 12:31:59AM -0700, David Miller wrote:
> From: Asias He <asias@redhat.com>
> Date: Fri, 16 Aug 2013 09:27:43 +0800
>
> > On Thu, Aug 15, 2013 at 02:07:40PM -0700, David Miller wrote:
> >> From: Asias He <asias@redhat.com>
> >> Date: Thu, 15 Aug 2013 11:20:16 +0800
> >>
> >> > memcpy_fromiovec is moved to lib/iovec.c. No need to include
> >> > linux/socket.h for it.
> >> >
> >> > Signed-off-by: Asias He <asias@redhat.com>
> >>
> >> You can't do this.
> >>
> >> Because this file doesn't include the header file that
> >> provides the declaration, which is linux/uio.h
> >
> > vhost.c includes drivers/vhost/vhost.h. In drivers/vhost/vhost.h, we
> > have linux/uio.h included.
>
> Nothing in vhost.h needs linux/uio.h right? That's very poor style,
> include the header where the dependency exists which is vhost.c
It needs struct iovec, which is in include/uapi/linux/uio.h.
Do you think it's better to include uapi/linux/uio.h directly?
In that case maybe we should update linux/socket.h
to pull in uapi/linux/uio.h directly too.
Or even just forward-declare struct iovec.
I tried this last option and the only fall-out seems to be in security/
- though I didn't do an allyes config build yet. Good idea? If yes let
me know and I'll do that.
-->
socket: forward-declare struct iovec
We can simplify header dependencies by using a forward declaration
of struct iovec in socket.h - it's always used through a pointer there.
Do this and fix up users that rely on socket.h including uio.h.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
diff --git a/include/linux/socket.h b/include/linux/socket.h
index 230c04b..3ad6f52 100644
--- a/include/linux/socket.h
+++ b/include/linux/socket.h
@@ -4,7 +4,6 @@
#include <asm/socket.h> /* arch-dependent defines */
#include <linux/sockios.h> /* the SIOCxxx I/O controls */
-#include <linux/uio.h> /* iovec support */
#include <linux/types.h> /* pid_t */
#include <linux/compiler.h> /* __user */
#include <uapi/linux/socket.h>
@@ -44,6 +43,8 @@ struct linger {
* belong in an obscure libc emulation or the bin.
*/
+struct iovec;
+
struct msghdr {
void * msg_name; /* Socket name */
int msg_namelen; /* Length of name */
diff --git a/security/keys/compat.c b/security/keys/compat.c
index d65fa7f..9c2723f 100644
--- a/security/keys/compat.c
+++ b/security/keys/compat.c
@@ -13,6 +13,7 @@
#include <linux/keyctl.h>
#include <linux/compat.h>
#include <linux/slab.h>
+#include <uapi/linux/uio.h>
#include "internal.h"
/*
--
MST
prev parent reply other threads:[~2013-08-16 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 3:20 [PATCH] vhost: Drop linux/socket.h Asias He
2013-08-15 21:07 ` David Miller
2013-08-16 1:27 ` Asias He
2013-08-16 7:31 ` David Miller
2013-08-16 9:27 ` Asias He
2013-08-17 5:29 ` David Miller
2013-08-19 1:23 ` [PATCH v2] vhost: Include linux/uio.h instead of linux/socket.h Asias He
2013-08-19 7:24 ` Michael S. Tsirkin
2013-08-20 22:08 ` David Miller
2013-08-16 9:50 ` Michael S. Tsirkin [this message]
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=20130816095012.GA21547@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).