From: Russell King <rmk@arm.linux.org.uk>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Chris Mason <chris.mason@fusionio.com>,
Mark Fasheh <mfasheh@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs
Date: Fri, 13 Sep 2013 13:15:29 +0100 [thread overview]
Message-ID: <20130913121529.GA1437@flint.arm.linux.org.uk> (raw)
In-Reply-To: <CA+5PVA6Hm6XLdJa=x9TmZnjSH160337i-CM2HGHBpQMf06Bv9w@mail.gmail.com>
On Fri, Sep 13, 2013 at 07:53:21AM -0400, Josh Boyer wrote:
> I'm not an ARM expert, so I don't know if ARM should use the
> asm-generic implementations, or just use __get_user/__put_user in all
> cases. I've CC'd rmk.
Why do we have uaccess-unaligned.h ? Normally, these kinds of things
are spawned by architectures which have problems with unaligned accesses,
ARM being one of them, but afaik we've never need this.
With the kernel-side trapping of unaligned accesses on older hardware,
we've always dealt with the normal accessor faulting.
From what I can tell in the git history, these unaligned put_user and
get_user have existed all the way back to the dawn of git use.
Can someone enlighten me why we have them?
--
Russell King
next prev parent reply other threads:[~2013-09-13 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130912153629.16487.88969@localhost.localdomain>
[not found] ` <CA+5PVA5GogJnewWvdmVo03oZRZDerE=H7BR49Xi1DZQyE_CG4Q@mail.gmail.com>
2013-09-13 6:44 ` [GIT PULL] Btrfs Geert Uytterhoeven
2013-09-13 6:44 ` Geert Uytterhoeven
2013-09-13 11:53 ` Josh Boyer
2013-09-13 12:15 ` Russell King [this message]
2013-09-13 12:15 ` Russell King
2013-09-13 12:36 ` Geert Uytterhoeven
2013-09-13 15:06 ` Josh Boyer
2013-09-13 15:06 ` Josh Boyer
2013-09-13 15:38 ` Josh Boyer
2013-09-13 15:58 ` Russell King
2013-09-13 15:58 ` Russell King
2013-09-14 9:33 ` Heiko Carstens
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=20130913121529.GA1437@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=chris.mason@fusionio.com \
--cc=geert@linux-m68k.org \
--cc=jwboyer@fedoraproject.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.de \
--cc=torvalds@linux-foundation.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).