diff options
author | Michael S. Tsirkin <mst@redhat.com> | 2014-12-14 19:52:51 +0300 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2014-12-18 11:11:09 +0300 |
commit | 505e428374bc17a2c0bd388c2e8d892e9cd8eef2 (patch) | |
tree | d2ba58ba96fc9bc9c4e7e421d9e0058ccfb22f25 /net/nfc | |
parent | c8742f85125dcfb27a2daa389283fffebffebb00 (diff) | |
download | linux-505e428374bc17a2c0bd388c2e8d892e9cd8eef2.tar.xz |
powerpc/uaccess: Allow get_user() with bitwise types
At the moment, if p and x are both of the same bitwise type
(eg. __le32), get_user(x, p) produces a sparse warning.
This is because *p is loaded into a long then cast back to typeof(*p).
When typeof(*p) is a bitwise type (which is uncommon), such a cast needs
__force, otherwise sparse produces a warning.
For non-bitwise types __force should have no effect, and should not hide
any legitimate errors.
Note that we are casting to typeof(*p) not typeof(x). Even with the
cast, if x and *p are of different types we should get the warning, so I
think we are not loosing the ability to detect any actual errors.
virtio would like to use bitwise types with get_user() so fix these
spurious warnings by adding __force.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
[mpe: Fill in changelog with more details]
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'net/nfc')
0 files changed, 0 insertions, 0 deletions