From: Emmanuel Guiton <emmanuel@netlab.hut.fi>
To: Duncan Sands <baldrick@free.fr>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Freeing skbuff (was: Re: Sending built-by-hand packet and kernel panic.)
Date: Mon, 02 Feb 2004 19:51:47 +0200 [thread overview]
Message-ID: <401E8E33.7050305@netlab.hut.fi> (raw)
In-Reply-To: 200402021602.56242.baldrick@free.fr
Hi!
Thanks a lot for pointing out these problems. I had completely missed them.
However, my overall problem is not solved. As far as my investigations
led me, my sk_buff structure is never released after having been sent on
the wire. So I guess I need an explicit destructor function in my
sk_buff as the following is present in the definition of struct sk_buff:
void (*destructor)(struct sk_buff *); /* Destruct function
*/
Well, until now what I tried lead to even more quicker kernel panics. If
anyone has a good advice, I'd appreciate a lot.
'Thank you again,
Emmanuel
Duncan Sands wrote:
>Hi Emmanuel, I don't know anything about network programming
>but I did notice a few strange things:
>
>
>
>> /* skb is allocated 56 bytes = TCP message with no data
>>(detailed hereafter)
>> * + 2 extra bytes before the ethernet header (see hereafter)
>> */
>> skb = alloc_skb(56, GFP_ATOMIC);
>>
>>
>
>Why is this GFP_ATOMIC when you use GFP_KERNEL later on?
>
>
>
>> skb_reserve(skb, 2); /* for 16-bit alignment*/
>> /* ethernet header is 14 byte long */
>> eth = (__u8 *) skb_put(skb, 14);
>> /* ip header is 20 byte long */
>> iph = (struct iphdr *)skb_put(skb, sizeof(struct iphdr));
>> /* tcp header (no options) is 20 byte long */
>> tcph = (struct tcphdr *)skb_put(skb, sizeof(struct tcphdr));
>>
>> /* skb->dst AND skb->dev (the latter is set by the former) */
>> if (ip_route_output(&rt, ip_dst, 0, 0, 0) != 0)
>> {
>> printk("ip_route_output failed.\n");
>> return -1;
>> }
>> skb->dst = (struct rt_entry *) rt; /* A trick from ip_route_input.c */
>> skb->dev = skb->dst->dev;
>>
>> /* Socket allocation. */
>> if (sock_create(PF_INET, SOCK_RAW, IPPROTO_RAW, &sending_socket) < 0)
>> {
>> printk("Error socket creation.\n");
>> sock_release(sending_socket);
>> return -1;
>> }
>> sk = kmalloc(sizeof(struct sock), GFP_KERNEL);
>> memcpy(&(sending_socket->sk), sk, sizeof(struct sock));
>>
>>
>
>Here you are copying the (uninitialized) sk into sending_socket->sk.
>I guess you got the arguments to memcpy the wrong way round.
>
>
>
>> sock_release(sending_socket);
>>
>>
>
>Maybe this drops reference counts to various objects, in which
>case it is wrong to reference them via sk.
>
>
>
>> if (sk == NULL)
>> {
>> printk("Error: sk == NULL\n");
>> return -1;
>> }
>> /* Now, set the sock field. */
>> skb->sk = sk;
>>
>> /* TRANSPORT HEADER: TCP */
>> /* here, TCP header data is filled in tcph. */
>> skb->h.th = tcph;
>> /* NETWORK HEADER: IP */
>> /* here, IP header data is filled in iph*/
>> skb->nh.iph = iph;
>> /* LINK HEADER: ETHERNET */
>> /* here, ethernet header data is filled in iph*/
>> skb->mac.ethernet = ((u8 *)iph) - 14;
>>
>> /* Fix me:
>> * Scheduling priority put at max, choose more correct value.
>> */
>> skb->priority = 15;
>> /* To choose right pkt_type when receiving a packet.
>> * We're not receivng anything, but I set the value like the guys
>> * in pktgen.c did, there should be a reason for that.
>> */
>> skb->protocol = __constant_htons(ETH_P_IP);
>>
>> /* TIMESTAMP */
>> /* last, so it's closest to sending time. */
>> do_gettimeofday(&skb->stamp);
>>
>>printk("Going to send initialized skb! ...\n");
>>// if (NF_HOOK(PF_INET, NF_IP_LOCAL_OUT, skb, NULL, skb->dev,
>>output_maybe_reroute) < 0)
>> NF_HOOK(PF_INET, NF_IP_LOCAL_OUT, skb, NULL, skb->dev,
>>ip_finish_output) < 0
>>
>>
>
>All the best,
>
>Duncan.
>
>
next prev parent reply other threads:[~2004-02-02 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 14:46 Sending built-by-hand packet and kernel panic Emmanuel Guiton
[not found] ` <200402021602.56242.baldrick@free.fr>
2004-02-02 17:51 ` Emmanuel Guiton [this message]
2004-02-03 9:49 ` Freeing skbuff (was: Re: Sending built-by-hand packet and kernel panic.) Muli Ben-Yehuda
2004-02-06 6:58 ` Emmanuel Guiton
2004-02-04 10:27 ` Duncan Sands
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=401E8E33.7050305@netlab.hut.fi \
--to=emmanuel@netlab.hut.fi \
--cc=baldrick@free.fr \
--cc=linux-kernel@vger.kernel.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