From: Andreas Schultz <aschultz@tpip.net>
To: pablo <pablo@netfilter.org>
Cc: laforge <laforge@gnumonks.org>,
osmocom-net-gprs <osmocom-net-gprs@lists.osmocom.org>,
netdev <netdev@vger.kernel.org>,
Lionel Gauthier <Lionel.Gauthier@eurecom.fr>
Subject: Re: [PATCH net-next 1/4] gtp: move TEID hash to per socket structure
Date: Tue, 14 Mar 2017 13:32:35 +0100 (CET) [thread overview]
Message-ID: <687079207.385041.1489494755160.JavaMail.zimbra@tpip.net> (raw)
In-Reply-To: <20170314113300.GA2992@salvia>
----- On Mar 14, 2017, at 12:33 PM, pablo pablo@netfilter.org wrote:
> On Tue, Mar 14, 2017 at 12:25:45PM +0100, Andreas Schultz wrote:
>> @@ -275,9 +280,9 @@ static int gtp1u_udp_encap_recv(struct gtp_dev *gtp, struct
>> sk_buff *skb)
>>
>> gtp1 = (struct gtp1_header *)(skb->data + sizeof(struct udphdr));
>>
>> - pctx = gtp1_pdp_find(gtp, ntohl(gtp1->tid));
>> + pctx = gtp1_pdp_find(gsk, ntohl(gtp1->tid));
>> if (!pctx) {
>> - netdev_dbg(gtp->dev, "No PDP ctx to decap skb=%p\n", skb);
>> + pr_debug("No PDP ctx to decap skb=%p\n", skb);
>> return 1;
>
> Again the pr_debug() change has resurrected.
Yes, at that point in the code, there is now ways to resolve the network device.
Therefore the netdev_dbg has to go.
> I already told you: If we are going to have more than one gtp device,
> then this doesn't make sense. I have to repeat things over and over
> again, just because you don't want to rebase your patchset for some
> reason. I don't find any other explaination for this.
Without a PDP context, there is no network device, so netdev_dbg.
> So please remove this debugging rather than rendering this completely
> useful.
ACK
> Moreover this change has nothing to this patch, so this doesn't break
> the one logical change per patch.
This patch moves the incoming teid has from the network device to the
socket. This means that gtp1_pdp_find needs to change. So this related.
For the debug change, see above why it's related.
Andreas
next prev parent reply other threads:[~2017-03-14 12:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 11:25 [PATCH net-next 0/4] gtp: support multiple APN's per GTP endpoint Andreas Schultz
2017-03-14 11:25 ` [PATCH net-next 1/4] gtp: move TEID hash to per socket structure Andreas Schultz
2017-03-14 11:33 ` Pablo Neira Ayuso
2017-03-14 12:32 ` Andreas Schultz [this message]
2017-03-14 11:25 ` [PATCH net-next 2/4] gtp: add genl cmd to enable GTP encapsulation on UDP socket Andreas Schultz
2017-03-14 11:43 ` Pablo Neira Ayuso
2017-03-14 12:28 ` Andreas Schultz
2017-03-14 13:39 ` Pablo Neira Ayuso
2017-03-14 11:25 ` [PATCH net-next 3/4] gtp: add support to select a GTP socket during PDP context creation Andreas Schultz
2017-03-14 11:25 ` [PATCH net-next 4/4] Extend Kernel GTP-U tunneling documentation Andreas Schultz
2017-03-14 11:45 ` [PATCH net-next 0/4] gtp: support multiple APN's per GTP endpoint Pablo Neira Ayuso
2017-03-14 12:42 ` Andreas Schultz
2017-03-14 13:42 ` Pablo Neira Ayuso
2017-03-14 13:52 ` Harald Welte
2017-03-14 18:32 ` 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=687079207.385041.1489494755160.JavaMail.zimbra@tpip.net \
--to=aschultz@tpip.net \
--cc=Lionel.Gauthier@eurecom.fr \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.