Hello,
> Please show at least one bug trace when inet_lookup(&tcp_hashinfo, 0, 0, 0, 0,
> 0) fails :)
Trying this the system hangs :-( (setting panic* doesn't change more).
However, using (&tcp_hashinfo, ip_src, p_src, ip_dst, p_dst, 0) gives the
following oops:
BUG: unable to handle kernel NULL p
skb?
Any idea please?
Cheers,
- Message d'origine
> De : Evgeniy Polyakov <[EMAIL PROTECTED]>
> À : Nj A <[EMAIL PROTECTED]>
> Cc : netdev@vger.kernel.org
> Envoyé le : Jeudi, 15 Novembre 2007, 11h12mn 28s
> Objet : Re: Re : Re : Bug in using inet_lookup (
> Well, your code will oops just like before - you provide empty skb to
> the inet_iif(), which is wrong. Actually you will not even reach that
> point, since your code will exit after skb->dev check.
>
> Try simple inet_lookup(&tcp_hashinfo, src, p_src, dst, p_dst, 0).
But trying inet_lookup(&t
By setting the ID of the ingress device to the inet_lookup() to 0, the machine
reboots automatically.
Setting proc/sys/kernel/panic* to non zero values dosn't help more..
Cheers,
- Message d'origine
> De : Evgeniy Polyakov <[EMAIL PROTECTED]>
> À : Nj A &l
I suspected it could be that. However, can't see in ip_rcv the right portion
that can help.
Any further tip please?
Regards,
- Message d'origine
> De : Evgeniy Polyakov <[EMAIL PROTECTED]>
> À : Nj A <[EMAIL PROTECTED]>
> Cc : netdev@vger.kernel.org
>
Dear All,
I need to use the inet_lookup function to find the sock structure of a TCP
connection in a SYN_RECV state.
Here is what I used to do so:
/* The kernel TCP hashtable */
struct inet_hashinfo __cacheline_aligned tcp_hashinfo = {
.lhash_lock = __RW_LOCK_UNLOCKED (tcp_hashinfo.lhash_lock),
.l
