From: David Miller <davem@davemloft.net>
To: yevgenyp@mellanox.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net 0/5] net/mlx4: Fixes to mlx4_core driver.
Date: Fri, 07 Sep 2012 12:58:54 -0400 (EDT) [thread overview]
Message-ID: <20120907.125854.2234018619889706404.davem@davemloft.net> (raw)
In-Reply-To: <1346921452-2035-1-git-send-email-yevgenyp@mellanox.com>
From: Yevgeny Petrilin <yevgenyp@mellanox.com>
Date: Thu, 6 Sep 2012 11:50:47 +0300
> Add security check / enforcement for flow steering rules set for VMs:
> Since VFs may be mapped to VMs which aren't trusted entities, flow
> steering rules attached through the wrapper on behalf of VFs must be
> checked to make sure that their L2 specification relate to MAC address
> assigned to that VF, and add L2 specification if its missing.
>
> Fixing bad handling of command failures, can lead to crash.
>
> Fixing wrong promiscuous mode entries management.
All applied, thanks.
prev parent reply other threads:[~2012-09-07 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 8:50 [PATCH net 0/5] net/mlx4: Fixes to mlx4_core driver Yevgeny Petrilin
2012-09-06 8:50 ` [PATCH net 1/5] net/mlx4_core: Put Firmware flow steering structures in common header files Yevgeny Petrilin
2012-09-06 8:50 ` [PATCH net 2/5] net/mlx4_core: Add security check / enforcement for flow steering rules set for VMs Yevgeny Petrilin
2012-09-06 8:50 ` [PATCH net 3/5] net/mlx4_core: Looking for promiscuous entries on the correct port Yevgeny Petrilin
2012-09-06 8:50 ` [PATCH net 4/5] net/mlx4_core: Fixing error flow in case of QUERY_FW failure Yevgeny Petrilin
2012-09-06 8:50 ` [PATCH net 5/5] net/mlx4_core: Return the error value in case of command initialization failure Yevgeny Petrilin
2012-09-07 16:58 ` David Miller [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=20120907.125854.2234018619889706404.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yevgenyp@mellanox.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 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).