From: Eric Sandeen <sandeen@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: fix unaligned access in xfs_btree_visit_blocks
Date: Mon, 22 May 2017 14:40:26 -0500 [thread overview]
Message-ID: <3a07e882-3ae8-c12c-fac6-9e31a6a96041@redhat.com> (raw)
In-Reply-To: <20170522190710.GB17100@infradead.org>
On 5/22/17 2:07 PM, Christoph Hellwig wrote:
> On Mon, May 22, 2017 at 10:48:14AM -0500, Eric Sandeen wrote:
>> This was throwing unaligned access warnings on sparc64:
>>
>> Kernel unaligned access at TPC[1043c088] xfs_btree_visit_blocks+0x88/0xe0 [xfs]
>>
>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>> ---
>>
>> diff --git a/fs/xfs/libxfs/xfs_btree.c b/fs/xfs/libxfs/xfs_btree.c
>> index 5392674..84089f8 100644
>> --- a/fs/xfs/libxfs/xfs_btree.c
>> +++ b/fs/xfs/libxfs/xfs_btree.c
>> @@ -4395,7 +4395,7 @@ struct xfs_btree_split_args {
>> xfs_btree_readahead_ptr(cur, ptr, 1);
>>
>> /* save for the next iteration of the loop */
>> - lptr = *ptr;
>> + lptr = get_unaligned(ptr);
>
> Hm.. We don't really do this for the return value of of xfs_btree_ptr_addr
> anywhere else. So if it really returns something not suitably enough
> aligned we're in much deeper trouble.
Yeah, I took a quick look, probably too quick. But I think the problem
here is that it's a structure copy, which is unusual compared to most of
the other callers:
union xfs_btree_ptr lptr;
lptr = *ptr;
and is probably what's generating the warning, right? I guess a better
comment and/or commit log would be in order.
I haven't looked at every other caller but several end up calling
xfs_btree_copy_ptrs which does a memcpy.
Hm, ok, maybe we should just be using that helper...
xfs_btree_copy_ptrs(cur, &lptr, ptr, 1);
?
-Eric
next prev parent reply other threads:[~2017-05-22 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 15:48 [PATCH] xfs: fix unaligned access in xfs_btree_visit_blocks Eric Sandeen
2017-05-22 16:02 ` Eric Sandeen
2017-05-22 19:07 ` Christoph Hellwig
2017-05-22 19:40 ` Eric Sandeen [this message]
2017-05-22 20:06 ` [PATCH V2] " Eric Sandeen
2017-05-22 20:43 ` Darrick J. Wong
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=3a07e882-3ae8-c12c-fac6-9e31a6a96041@redhat.com \
--to=sandeen@redhat.com \
--cc=hch@infradead.org \
--cc=linux-xfs@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).