From: Randolph Chung <randolph@tausq.org>
To: jsoe0708@tiscali.be
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] unaligned accesses
Date: Thu, 9 Jan 2003 23:36:59 -0800 [thread overview]
Message-ID: <20030110073659.GC31470@tausq.org> (raw)
In-Reply-To: <3E1AA8D500000856@ocpmta8.freegates.net>
> >Blame LaMont!
> >(yes, I'm just kidding, I've just been waiting for my chance to say
> >this... :-)
> >
> Do you think that this tcpdump pb is also related to Lamont job (to be honest
> I do not remember what was it?):
LaMont recently improved the unaligned handler to be more correct and
more robust... as well as handle more cases.
> ...
> Jan 9 09:59:58 fw01 kernel: tcpdump(4638): unaligned access to 0x0011e78a
> at ip=0x0002ab83
> Jan 9 09:59:34 fw01 kernel: tcpdump(4638): unaligned access to 0x0011e78e
> at ip=0x0002ab83
> ...
yes, tcpdump (and several other network tools) are known to generate a
lot of unaligned accesses.
> hmmm buggy: not always, the triky case is when you have to access to those
> kind of data encapsulated into a structure. I do not yet find any workaround
> or how to fix this kind of pb. Any idea (gcc-3.3?)?
eh? what do you mean?
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2003-01-10 7:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 7:55 [parisc-linux] Printing problem with HP9000 712/80 and two more questions Vilmos Soti
2003-01-09 8:29 ` [parisc-linux] unaligned accesses Randolph Chung
2003-01-10 7:29 ` jsoe0708
2003-01-10 7:36 ` Randolph Chung [this message]
2003-01-10 8:24 ` jsoe0708
2003-01-10 12:52 ` Matthieu Delahaye
2003-01-10 13:45 ` jsoe0708
2003-01-10 16:29 ` Randolph Chung
2003-01-10 15:30 ` John David Anglin
2003-01-10 10:51 ` jsoe0708
2003-01-10 17:08 ` Matthew Wilcox
2003-01-10 18:47 ` jsoe0708
2003-01-10 22:13 ` Thibaut VARENE
2003-01-10 22:25 ` Thibaut VARENE
2003-01-12 15:25 ` Joel Soete
2003-01-12 16:02 ` Thibaut VARENE
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=20030110073659.GC31470@tausq.org \
--to=randolph@tausq.org \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.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