From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] libata: fix HDIO_GET_32BIT ioctl
Date: Thu, 11 Feb 2016 10:10:30 -0500 [thread overview]
Message-ID: <20160211151030.GW3741@mtj.duckdns.org> (raw)
In-Reply-To: <1455196595-3466120-1-git-send-email-arnd@arndb.de>
On Thu, Feb 11, 2016 at 02:16:27PM +0100, Arnd Bergmann wrote:
> As reported by Soohoon Lee, the HDIO_GET_32BIT ioctl does not
> work correctly in compat mode with libata.
>
> I have investigated the issue further and found multiple problems
> that all appeared with the same commit that originally introduced
> HDIO_GET_32BIT handling in libata back in linux-2.6.8 and presumably
> also linux-2.4, as the code uses "copy_to_user(arg, &val, 1)" to copy
> a 'long' variable containing either 0 or 1 to user space.
Applied to libata/for-4.5-fixes.
Thanks a lot!
--
tejun
prev parent reply other threads:[~2016-02-11 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 13:16 [PATCH] libata: fix HDIO_GET_32BIT ioctl Arnd Bergmann
2016-02-11 15:10 ` Tejun Heo [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=20160211151030.GW3741@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).