From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Paul.Durrant@citrix.com,
wei.liu2@citrix.com, xen-devel@lists.xenproject.org,
konrad.wilk@oracle.com
Subject: Re: xennet_start_xmit assumptions
Date: Thu, 19 Jan 2017 13:47:33 -0500 [thread overview]
Message-ID: <20170119184733.GJ22018@oracle.com> (raw)
In-Reply-To: <20170119.113759.555556955190770932.davem@davemloft.net>
On (01/19/17 11:37), David Miller wrote:
>
> I thought we had code which made sure that at least a minimal
> link layer header was present in the SKB?
>
> Specifically I'm talking about the dev_validate_header() check.
> That is supposed to protect us from these kinds of situations.
ah, but I run my pf_packet application as root, so I have
capable(CAP_SYS_RAWIO), so I slip through the dev_validate_header()
check.
--Sowmini
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-19 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170118153132.GB9258@oracle.com>
2017-01-18 19:25 ` xennet_start_xmit assumptions Konrad Rzeszutek Wilk
[not found] ` <20170118192528.GA6847@char.us.oracle.com>
2017-01-19 9:36 ` Paul Durrant
2017-01-19 11:14 ` Sowmini Varadhan
[not found] ` <20170119111426.GA22018@oracle.com>
2017-01-19 11:31 ` Paul Durrant
2017-01-19 11:37 ` Sowmini Varadhan
2017-01-19 16:37 ` David Miller
2017-01-19 18:47 ` Sowmini Varadhan [this message]
2017-01-19 22:41 ` Sowmini Varadhan
[not found] ` <20170119224123.GB19618@oracle.com>
2017-01-20 19:30 ` David Miller
[not found] ` <20170120.143059.1390682983473502518.davem@davemloft.net>
2017-01-20 20:03 ` Sowmini Varadhan
2017-01-25 15:06 ` Paul Durrant
[not found] ` <fa531e2ed014488baa10556c724e176c@AMSPEX02CL03.citrite.net>
2017-01-25 15:45 ` Sowmini Varadhan
2017-01-18 15:31 Sowmini Varadhan
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=20170119184733.GJ22018@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=Paul.Durrant@citrix.com \
--cc=davem@davemloft.net \
--cc=konrad.wilk@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).