From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Hennerich, Michael" <Michael.Hennerich@analog.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix unaligned exception in /drivers/net/wireless/orinoco.c
Date: Mon, 05 Feb 2007 00:08:38 -0500 [thread overview]
Message-ID: <1170652118.4191.36.camel@dv.roinet.com> (raw)
In-Reply-To: <20070202202039.GA9382@tuxdriver.com>
On Fri, 2007-02-02 at 15:20 -0500, John W. Linville wrote:
> On Thu, Jan 18, 2007 at 09:57:18AM -0000, Hennerich, Michael wrote:
> >
> > This short patch prevents an unaligned exception to occur. (GCC 4.1)
> > tmp is defined as char pointer while it is later accessed as short.
Signed-off-by: Pavel Roskin <proski@gnu.org>
> This patch seems fine, such as it is. But, it seems like it might
> also be appropriate to change hermes_read_ltv and/or hermes_read_words
> to not take void * parameters? This patch would still be needed,
> but it might be more obvious to future coders?
I agree. If we use any optimization that requires alignment of the
buffer for aligned access, it needs to be clearly specified and
(ideally) enforced.
I've tried to make a patch, but it seems to be a bigger effort than I
expected. It turns out that hermes_clear_words() is not doing what it
should (although it would only affect some buggy firmwares), and it's
clear that I just cannot replace a couple of arguments and hope for the
best. I need to dust off my 802.11b cards and re-test everything.
I've started orinoco branch locally, and I hope I'll be able to clean
the driver from all that bitrot soon.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2007-02-05 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 9:57 [PATCH] fix unaligned exception in /drivers/net/wireless/orinoco.c Hennerich, Michael
2007-02-02 20:20 ` John W. Linville
2007-02-05 5:08 ` Pavel Roskin [this message]
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=1170652118.4191.36.camel@dv.roinet.com \
--to=proski@gnu.org \
--cc=Michael.Hennerich@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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.