From: Laurent Vivier <laurent@vivier.eu>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: Laurent Vivier <laurent@vivier.eu>, qemu-devel@nongnu.org, agraf@suse.de
Subject: [Qemu-devel] [PATCH RFC 2/3] linux-user: support netlink protocol NETLINK_KOBJECT_UEVENT
Date: Sat, 30 Jan 2016 23:26:59 +0100 [thread overview]
Message-ID: <1454192820-5095-3-git-send-email-laurent@vivier.eu> (raw)
In-Reply-To: <1454192820-5095-1-git-send-email-laurent@vivier.eu>
This is the protocol used by udevd to manage kernel events.
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
---
linux-user/syscall.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index a1ed2f5..790ae49 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -2572,6 +2572,9 @@ static abi_long do_socket(int domain, int type, int protocol)
case NETLINK_ROUTE:
fd_trans_register(ret, &target_netlink_route_trans);
break;
+ case NETLINK_KOBJECT_UEVENT:
+ /* nothing to do: messages are strings */
+ break;
default:
close(ret);
ret = -EPFNOSUPPORT;
--
2.5.0
next prev parent reply other threads:[~2016-01-30 22:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 22:26 [Qemu-devel] [PATCH RFC 0/3] linux-user: netlink support Laurent Vivier
2016-01-30 22:26 ` [Qemu-devel] [PATCH RFC 1/3] linux-user: add rtnetlink(7) support Laurent Vivier
2016-05-13 16:40 ` Peter Maydell
2016-05-14 9:37 ` Laurent Vivier
2016-05-14 10:13 ` Peter Maydell
2016-01-30 22:26 ` Laurent Vivier [this message]
2016-05-13 16:42 ` [Qemu-devel] [PATCH RFC 2/3] linux-user: support netlink protocol NETLINK_KOBJECT_UEVENT Peter Maydell
2016-01-30 22:27 ` [Qemu-devel] [PATCH RFC 3/3] linux-user: add netlink audit Laurent Vivier
2016-05-13 16:48 ` Peter Maydell
2016-02-07 10:24 ` [Qemu-devel] [PATCH RFC 0/3] linux-user: netlink support Laurent Vivier
2016-02-07 13:10 ` Peter Maydell
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=1454192820-5095-3-git-send-email-laurent@vivier.eu \
--to=laurent@vivier.eu \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).