From: Kevin Winchester <kjwinchester@gmail.com>
To: Andrew Morgan <morgan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
apw@shadowen.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, kamalesh@linux.vnet.ibm.com
Subject: Re: 2.6.24-rc2-mm1 -- strange apparent network failures
Date: Sat, 17 Nov 2007 21:17:12 -0400 [thread overview]
Message-ID: <473F9298.7060401@gmail.com> (raw)
In-Reply-To: <473F8C46.4070308@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kevin Winchester wrote:
> Looking at the code being bypassed:
>
> if (pE.cap[i] || pP.cap[i] || pP.cap[i])
>
> looks somewhat weird as it is testing the same condition twice. Should
> it have been:
>
> if (pE.cap[i] || pP.cap[i] || pI.cap[i])
>
> ?
>
> I'm about to test that change instead of bypassing the loop, so I'll let
> you know the results.
>
No, this still results in a dead network connection, although it is
probably a correct change. I suppose giving the loop even more reasons
to return -ERANGE wasn't going to be helpful.
- --
Kevin Winchester
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHP5KXKPGFQbiQ3tQRAilbAJ9h3qtO9sb9+ctVU0pxzCBjysy06QCdE1Wd
M5V3+0BWyn04p0UeUq/KSlw=
=663t
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-11-18 1:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071113175906.497a1a6a.akpm@linux-foundation.org>
2007-11-15 10:02 ` 2.6.24-rc2-mm1 -- strange apparent network failures Andy Whitcroft
2007-11-16 0:28 ` Kevin Winchester
2007-11-16 0:44 ` Andrew Morton
2007-11-17 5:16 ` Andrew Morgan
2007-11-17 12:48 ` Kevin Winchester
2007-11-17 23:52 ` Andrew Morgan
2007-11-18 0:50 ` Kevin Winchester
2007-11-18 1:17 ` Kevin Winchester [this message]
2007-11-18 1:57 ` Andrew Morgan
2007-11-18 1:23 ` Kevin Winchester
2007-11-17 13:57 ` Andy Whitcroft
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=473F9298.7060401@gmail.com \
--to=kjwinchester@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).