From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] avoid unaligned access to data
Date: Fri, 12 Mar 2004 23:59:39 +0000 [thread overview]
Message-ID: <20040312235939.GB29248@suse.de> (raw)
In-Reply-To: <20040229204531.GA25308@suse.de>
On Fri, Mar 12, Greg KH wrote:
> On Fri, Mar 05, 2004 at 11:21:36PM +0100, Olaf Hering wrote:
> > On Sun, Feb 29, Olaf Hering wrote:
> >
> > >
> > > the data access in udevinfo is usually unaligned, due to the fact that
> > > the struct is at offset strlen(sysfspath). That makes an ia64 kernel
> > > rather unhappy. Unless I miss something, this change makes it happy by
> > > making an incompatible change to the database.
> > >
> >
> > What is the plan here, Greg?
>
> Greg didn't see this patch :(
>
> Next time please cc patches to me so I make sure I don't miss them. I
> tend to get a _lot_ of email...
>
> Anyway, what is the error that happens on a ia64 box?
it complains about unaligned memory access.
udevinfo(4922): unaligned access to 0x6000000000015747, ip=0x4000000000001dd0
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&opÃk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-03-12 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 20:45 [PATCH] avoid unaligned access to data Olaf Hering
2004-03-05 22:21 ` Olaf Hering
2004-03-12 23:40 ` Greg KH
2004-03-12 23:41 ` Greg KH
2004-03-12 23:59 ` Olaf Hering [this message]
2004-03-13 0:03 ` Olaf Hering
2004-03-13 0:11 ` Greg KH
2004-03-13 9:58 ` Olaf Hering
2004-03-13 16:57 ` Johannes Erdfelt
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=20040312235939.GB29248@suse.de \
--to=olh@suse.de \
--cc=linux-hotplug@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).