From: Mika Liljeberg <Mika.Liljeberg@welho.com>
To: kuznet@ms2.inr.ac.ru
Cc: Mika.Liljeberg@nokia.com, davem@redhat.com,
linux-kernel@vger.kernel.org, sarolaht@cs.helsinki.fi,
rmk@arm.linux.ORG.UK
Subject: Re: ARM: Re: TCP LAST-ACK state broken in 2.4.17-pre2 [NEW DATA]
Date: Tue, 18 Dec 2001 22:52:31 +0200 [thread overview]
Message-ID: <3C1FAC8F.699E1287@welho.com> (raw)
In-Reply-To: <200112182029.XAA11287@ms2.inr.ac.ru>
kuznet@ms2.inr.ac.ru wrote:
> > It's ARM in little endian mode.
>
> I think it is answer to the question.
>
> No doubts it still has broken misaligned access.
Oops, I think there was a misunderstanding. The linux machine is Intel.
The other one is a non-Linux ARM.
> > Now that you mention it, tcp_parse_options() in input.c seems to expect
> > that the timestamps are word aligned,
>
> Nope. It does not expect any alignment, but it is really supposed
> to penalise misbehaving cases.
Ahh, I see. There's a kernel exception handler that is supposed to fix
misaligned access? Hacky.
Cheers,
MikaL
next prev parent reply other threads:[~2001-12-18 20:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 9:33 TCP LAST-ACK state broken in 2.4.17-pre2 [NEW DATA] Mika.Liljeberg
2001-12-18 18:37 ` kuznet
2001-12-18 20:21 ` Mika Liljeberg
2001-12-18 20:28 ` David S. Miller
2001-12-18 20:29 ` ARM: " kuznet
2001-12-18 20:52 ` Mika Liljeberg [this message]
2001-12-18 21:08 ` David S. Miller
2001-12-18 21:03 ` Russell King
2001-12-18 21:11 ` David S. Miller
2001-12-18 21:14 ` Russell King
2001-12-18 21:15 ` David S. Miller
2001-12-18 21:27 ` Mika Liljeberg
2001-12-18 21:24 ` Rik van Riel
2001-12-18 21:28 ` Russell King
2001-12-18 21:33 ` David S. Miller
2001-12-20 7:31 ` Stevie O
2001-12-20 7:40 ` David S. Miller
2001-12-20 7:51 ` Stevie O
2001-12-20 8:58 ` Russell King
2001-12-20 9:01 ` Russell King
2001-12-20 10:22 ` David Weinehall
2002-01-02 19:52 ` Mike Touloumtzis
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 9:10 ARM: " Mika.Liljeberg
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=3C1FAC8F.699E1287@welho.com \
--to=mika.liljeberg@welho.com \
--cc=Mika.Liljeberg@nokia.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.ORG.UK \
--cc=sarolaht@cs.helsinki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.