From: Nj A <nj_a83@yahoo.fr>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: netdev@vger.kernel.org, kaber@trash.net, davem@davemloft.net
Subject: Re : Re : Re : Re : Bug in using inet_lookup ()
Date: Thu, 15 Nov 2007 16:57:17 +0000 (GMT) [thread overview]
Message-ID: <455140.87973.qm@web26108.mail.ukl.yahoo.com> (raw)
> 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(&tcp_hashinfo, src, p_src, dst, p_dst, 0), the machine either hangs or panics.
Is there any clean manner to come across this issue?
Cheers,
_____________________________________________________________________________
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail
next reply other threads:[~2007-11-15 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 16:57 Nj A [this message]
2007-11-15 17:30 ` Re : Re : Re : Re : Bug in using inet_lookup () Evgeniy Polyakov
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=455140.87973.qm@web26108.mail.ukl.yahoo.com \
--to=nj_a83@yahoo.fr \
--cc=davem@davemloft.net \
--cc=johnpol@2ka.mipt.ru \
--cc=kaber@trash.net \
--cc=netdev@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