On Thu, Nov 15, 2007 at 04:57:17PM +, Nj A ([EMAIL PROTECTED]) wrote:
> > 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 simpl
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
On Thu, Nov 15, 2007 at 05:29:52PM +0100, Nj A ([EMAIL PROTECTED]) wrote:
> Hello all,
> No bugs are due to the inet_lookup call now using the following:
> if ((s_skb = alloc_skb (MAX_TCP_HEADER + 15, GFP_ATOMIC)) == NULL)
> {
> printk ("%s: Unable to allocate memory \n", __FUN
On Wed, Nov 14, 2007 at 04:47:22PM +, Nj A ([EMAIL PROTECTED]) wrote:
> 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..
Sorry, I did not understand?
You mean after yo
