All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Mazur <mmazur@kernel.pl>
To: reiserfs-list@namesys.com
Subject: Invalid use of asm/unaligned.h
Date: Wed, 11 Aug 2004 21:48:42 +0200	[thread overview]
Message-ID: <200408112148.42125.mmazur@kernel.pl> (raw)

I'm the linux-libc-headers* maintainer and after the release of version 
reiserfsprogs 3.6.18 I was informed that they don't build correctly against 
llh. A couple of months ago a patch was added to reiserfsprogs that fixed 
access to unaligned memory on ia64. Fact of the matter is that 
asm/unaligned.h is *not* a userland header (and as such was removed from llh) 
and you can call good luck the fact that it's userland friendly on ia64. On 
most archs that it's needed on (those that do not support unaligned memory 
access) the header will either not work cause it requires some kernel 
internal stuff, or will not work cause it's plain marked as kernel only 
(ifdefed __KERNEL__ as on arch-ppc).

Now the nice thing to do would be to switch to some more userland friendly way 
of accessing unaligned memory, since using kernel headers for such things is 
not a good idea. I don't have too much options for making those headers 
userland friendly and adding them to llh, since I can't call any external 
functions (like memcpy) from llh and I don't believe adding lots of asm code 
by coding my own functions for that is a good idea (neither have I the 
expertise nor the resources to do it correctly).
So - what will it be? :)

Oh, and please do cc me with any replies since I'm not subscribed to this 
list.

* http://ep09.pld-linux.org/~mmazur/linux-libc-headers


-- 
In the year eighty five ten
God is gonna shake his mighty head
He'll either say,
"I'm pleased where man has been"
Or tear it down, and start again

             reply	other threads:[~2004-08-11 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 19:48 Mariusz Mazur [this message]
2004-08-11 20:55 ` Invalid use of asm/unaligned.h Jeff Mahoney
2004-08-11 22:27   ` Mariusz Mazur

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=200408112148.42125.mmazur@kernel.pl \
    --to=mmazur@kernel.pl \
    --cc=reiserfs-list@namesys.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.