From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: netdev@vger.kernel.org
Cc: Neil Horman <nhorman@tuxdriver.com>,
Vlad Yasevich <vyasevich@gmail.com>,
linux-sctp@vger.kernel.org
Subject: [PATCH net-next 1/6] sctp: allow others to use sctp_input_cb
Date: Wed, 13 Jul 2016 18:08:55 +0000 [thread overview]
Message-ID: <615beca39da498ba640c767a1b046bce67357bc7.1468432819.git.marcelo.leitner@gmail.com> (raw)
In-Reply-To: <cover.1468432819.git.marcelo.leitner@gmail.com>
We process input path in other files too and having access to it is
nice, so move it to a header where it's shared.
Signed-off-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
---
include/net/sctp/structs.h | 15 +++++++++++++++
net/sctp/input.c | 11 -----------
2 files changed, 15 insertions(+), 11 deletions(-)
diff --git a/include/net/sctp/structs.h b/include/net/sctp/structs.h
index 8626bdd3249a9283955fe81bc3255be0a18717f9..966c3a40039c12a7c525612594a51312d5de1d2a 100644
--- a/include/net/sctp/structs.h
+++ b/include/net/sctp/structs.h
@@ -59,6 +59,7 @@
#include <linux/workqueue.h> /* We need tq_struct. */
#include <linux/sctp.h> /* We need sctp* header structs. */
#include <net/sctp/auth.h> /* We need auth specific structs */
+#include <net/ip.h> /* For inet_skb_parm */
/* A convenience structure for handling sockaddr structures.
* We should wean ourselves off this.
@@ -1092,6 +1093,20 @@ static inline void sctp_outq_cork(struct sctp_outq *q)
q->cork = 1;
}
+/* SCTP skb control block.
+ * sctp_input_cb is currently used on rx and sock rx queue
+ */
+struct sctp_input_cb {
+ union {
+ struct inet_skb_parm h4;
+#if IS_ENABLED(CONFIG_IPV6)
+ struct inet6_skb_parm h6;
+#endif
+ } header;
+ struct sctp_chunk *chunk;
+};
+#define SCTP_INPUT_CB(__skb) ((struct sctp_input_cb *)&((__skb)->cb[0]))
+
/* These bind address data fields common between endpoints and associations */
struct sctp_bind_addr {
diff --git a/net/sctp/input.c b/net/sctp/input.c
index 6f8e676d285ead987b0a1337beec3b29c34e0a8e..7a327ff71f08985f6ebb963d5cdc9540b23d0666 100644
--- a/net/sctp/input.c
+++ b/net/sctp/input.c
@@ -90,17 +90,6 @@ static inline int sctp_rcv_checksum(struct net *net, struct sk_buff *skb)
return 0;
}
-struct sctp_input_cb {
- union {
- struct inet_skb_parm h4;
-#if IS_ENABLED(CONFIG_IPV6)
- struct inet6_skb_parm h6;
-#endif
- } header;
- struct sctp_chunk *chunk;
-};
-#define SCTP_INPUT_CB(__skb) ((struct sctp_input_cb *)&((__skb)->cb[0]))
-
/*
* This is the routine which IP calls when receiving an SCTP packet.
*/
--
2.7.4
next prev parent reply other threads:[~2016-07-13 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 18:08 [PATCH net-next 0/6] sctp: allow GSO frags to access the chunk too Marcelo Ricardo Leitner
2016-07-13 18:08 ` Marcelo Ricardo Leitner [this message]
2016-07-13 18:08 ` [PATCH net-next 2/6] sctp: reorder sctp_ulpevent and shrink msg_flags Marcelo Ricardo Leitner
2016-07-13 18:08 ` [PATCH net-next 3/6] sctp: allow GSO frags to access the chunk too Marcelo Ricardo Leitner
2016-07-13 18:08 ` [PATCH net-next 4/6] sctp: avoid identifying address family many times for a chunk Marcelo Ricardo Leitner
2016-07-13 18:08 ` [PATCH net-next 5/6] sctp: do not clear chunk->ecn_ce_done flag Marcelo Ricardo Leitner
2016-07-13 18:09 ` [PATCH net-next 6/6] sctp: only check for ECN if peer is using it Marcelo Ricardo Leitner
2016-07-14 1:10 ` [PATCH net-next 0/6] sctp: allow GSO frags to access the chunk too David Miller
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=615beca39da498ba640c767a1b046bce67357bc7.1468432819.git.marcelo.leitner@gmail.com \
--to=marcelo.leitner@gmail.com \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@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).