From: Laurent Vivier <laurent@vivier.eu>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 0/5] linux-user: manage SOCK_PACKET socket type
Date: Wed, 23 Dec 2015 14:13:21 +0100 [thread overview]
Message-ID: <567A9DF1.5000800@vivier.eu> (raw)
In-Reply-To: <20151221151449.GA29744@kos.to>
Le 21/12/2015 16:14, Riku Voipio a écrit :
> On Fri, Dec 18, 2015 at 04:13:20PM +0100, Laurent Vivier wrote:
>> Le 29/10/2015 00:12, Peter Maydell a écrit :
>>> On 28 October 2015 at 20:40, Laurent Vivier <laurent@vivier.eu> wrote:
>>>> This is obsolete, but if we want to use dhcp with some distros (like debian
>>>> ppc 8.2 jessie), we need it.
>>>>
>>>> bind() uses an interface name instead an interface index, and socket()
>>>> needs network order value to encode the protocol.
>>>>
>>>> v3: update cover letter message,
>>>> insert Reviewed-by: in PATCH 1 and PATCH 2
>>>> insert fd_trans_target_to_host_addr into target_to_host_sockaddr and
>>>> pass fd, check fd is >= 0, rename packet_target_to_host_addr to
>>>> packet_target_to_host_sockaddr
>>>>
>>>> v2: Split the patch in 4 parts to manage protocol endianness (socket()) and
>>>> interface name (bind()) in different patches.
>>>> Use TargetFdTrans array to manage the SOCK_PACKET type special case in
>>>> bind().
>>>> The two others patches are here to introduce a new function in TargetFdTrans
>>>> to translate sockaddr data structure (rename previous functions to be
>>>> clear).
>>>>
>>>> Laurent Fiver (5):
>>>
>>> This name doesn't match the names on the actual patch mails,
>>> but those are right so I guess it doesn't matter.
>>>
>>>> linux-user: SOCK_PACKET uses network endian to encode protocol in
>>>> socket()
>>>> linux-user: rename TargetFdFunc to TargetFdDataFunc, and structure
>>>> fields accordingly
>>>> linux-user: add a function hook to translate sockaddr
>>>> linux-user: manage bind with a socket of SOCK_PACKET type.
>>>> linux-user: check fd is >= 0 in
>>>> fd_trans_host_to_target_data/fd_trans_host_to_target_addr
>>>
>>> Series
>>> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>
>> Can we have this series applied ?
>
> I'll create next pull req next week, right now I'm a bit busy. If someone
> else wants to merge the series before me, you have my Acked-by.
If you want, I can do the pull request:
- I take your branch linux-user-for-upstream
from https://git.linaro.org/people/riku.voipio/qemu.git
- remove "linux-user: Fix array bounds in errno conversion"
because it is broken,
- add "linux-user: manage SOCK_PACKET socket type"
I'd like to add "linux-user, sh4: fix signal retcode address",
"linux-user: Enable sigaltstack syscall for sh4" but they have no
reviewer except me.
Laurent
prev parent reply other threads:[~2015-12-23 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 20:40 [Qemu-devel] [PATCH v3 0/5] linux-user: manage SOCK_PACKET socket type Laurent Vivier
2015-10-28 20:40 ` [Qemu-devel] [PATCH v3 1/5] linux-user: SOCK_PACKET uses network endian to encode protocol in socket() Laurent Vivier
2015-10-28 20:40 ` [Qemu-devel] [PATCH v3 2/5] linux-user: rename TargetFdFunc to TargetFdDataFunc, and structure fields accordingly Laurent Vivier
2015-10-28 20:40 ` [Qemu-devel] [PATCH v3 3/5] linux-user: add a function hook to translate sockaddr Laurent Vivier
2015-10-28 20:40 ` [Qemu-devel] [PATCH v3 4/5] linux-user: manage bind with a socket of SOCK_PACKET type Laurent Vivier
2015-10-28 20:40 ` [Qemu-devel] [PATCH v3 5/5] linux-user: check fd is >= 0 in fd_trans_host_to_target_data/fd_trans_host_to_target_addr Laurent Vivier
2015-10-28 23:12 ` [Qemu-devel] [PATCH v3 0/5] linux-user: manage SOCK_PACKET socket type Peter Maydell
2015-10-29 8:52 ` Laurent Vivier
2015-12-18 15:13 ` Laurent Vivier
2015-12-21 15:14 ` Riku Voipio
2015-12-21 16:20 ` Laurent Vivier
2015-12-23 13:13 ` Laurent Vivier [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=567A9DF1.5000800@vivier.eu \
--to=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--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).