From: jamal <hadi@cyberus.ca>
To: netdev@vger.kernel.org
Cc: "David Miller" <davem@davemloft.net>,
"Atis Elsts" <atis@mikrotik.com>,
eric.dumazet@gmail.com,
"Maciej Żenczykowski" <zenczykowski@gmail.com>
Subject: [PATCH][RFC]: ingress socket filter by mark
Date: Sun, 18 Oct 2009 08:42:38 -0400 [thread overview]
Message-ID: <1255869758.4815.40.camel@dogo.mojatatu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
Maciej forced me to dig into this ;->
at the socket level if a packet arrives with a different mark than
what we bind to, drop it. I have tested this patch and it drops a packet
with mismatching mark.
There are several approaches - and i think the patch suggestion i have
made here maybe too strict. I assume that if someone binds to a mark,
they want to not only send packets with that mark but receive
only if that mark is set.
A looser check would be something along the line accept as well if mark
is not set i.e
if (sk->sk_mark && skb->mark && sk->sk_mark != skb->mark)
Alternatively i could add one bit in the socket flags and have it so
that check is made only if app has been explicit:
if (sock_flag(sk, SOCK_CHK_SOMARK) && sk->sk_mark != skb->mark) drop
Another approach is to set sock filter from app. I dont like this
approach because it will be the least usable from app level and would be
the least simple from kernel level.
cheers,
jamal
[-- Attachment #2: filt-sock-m --]
[-- Type: text/x-patch, Size: 375 bytes --]
diff --git a/net/core/filter.c b/net/core/filter.c
index d1d779c..6fcf577 100644
--- a/net/core/filter.c
+++ b/net/core/filter.c
@@ -85,6 +85,9 @@ int sk_filter(struct sock *sk, struct sk_buff *skb)
if (err)
return err;
+ if (sk->sk_mark && sk->sk_mark != skb->mark)
+ return -EPERM;
+
rcu_read_lock_bh();
filter = rcu_dereference(sk->sk_filter);
if (filter) {
next reply other threads:[~2009-10-18 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-18 12:42 jamal [this message]
2009-10-18 17:28 ` [PATCH][RFC]: ingress socket filter by mark Eric Dumazet
2009-10-18 20:28 ` jamal
2009-10-18 23:09 ` Maciej Żenczykowski
2009-10-19 12:12 ` jamal
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=1255869758.4815.40.camel@dogo.mojatatu.com \
--to=hadi@cyberus.ca \
--cc=atis@mikrotik.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=zenczykowski@gmail.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).