linux-kernel - Re: [net-next rfc V2 6/8] macvtap: allow TUNSETIFF to create multiqueue device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <51A8B829.7040708@cogentembedded.com>
Date:	Fri, 31 May 2013 18:48:09 +0400
From:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To:	Jason Wang <jasowang@...hat.com>
CC:	davem@...emloft.net, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, mst@...hat.com
Subject: Re: [net-next rfc V2 6/8] macvtap: allow TUNSETIFF to create multiqueue
 device

Hello.

On 31-05-2013 13:53, Jason Wang wrote:

> Though the queue were in fact created by open(), we still need to add this check
> to be compatible with tuntap which can let mgmt software use a single API to
> manage queues. This patch only validates the device name and moves the TUNSETIFF
> to a helper.

> Signed-off-by: Jason Wang <jasowang@...hat.com>
> ---
>   drivers/net/macvtap.c |   51 ++++++++++++++++++++++++++++++++++++++----------
>   1 files changed, 40 insertions(+), 11 deletions(-)

> diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
> index e76484c..eac49cb 100644
> --- a/drivers/net/macvtap.c
> +++ b/drivers/net/macvtap.c
> @@ -870,6 +870,7 @@ out:
>   	return ret;
>   }
>
> +

    Seems like random whitespace change.

>   static struct macvlan_dev *macvtap_get_vlan(struct macvtap_queue *q)
>   {
>   	struct macvlan_dev *vlan;
[...]

WBR, Sergei

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/