stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 7/9] [3.18-stable] i2o: hide unsafe ioctl on 64-bit
Date: Fri, 5 May 2017 10:13:12 -0700	[thread overview]
Message-ID: <20170505171312.GA19034@kroah.com> (raw)
In-Reply-To: <20170505115725.1424772-8-arnd@arndb.de>

On Fri, May 05, 2017 at 01:57:23PM +0200, Arnd Bergmann wrote:
> We get a warning about a broken pointer conversion on 64-bit architectures:
> 
> drivers/message/i2o/i2o_config.c: In function 'i2o_cfg_passthru':
> drivers/message/i2o/i2o_config.c:893:19: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
>          (p->virt, (void __user *)sg[i].addr_bus,
>                    ^
> drivers/message/i2o/i2o_config.c:953:10: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
>          ((void __user *)sg[j].addr_bus, sg_list[j].virt,
>           ^
> 
> This has clearly never worked right, so we can add an #ifdef around the code.
> The driver was moved to staging in linux-4.0 and finally removed in 4.2,
> so upstream does not have a fix for it.
> 
> The driver originally got this mostly right, though probably by accident.

I fixed this in a different way, doing the cast to make things be quiet,
as was done in other places in the driver.  You were copied on that
patch when it was added to my tree, right?

And yes, this thing probably never really worked, so I don't worry about
it :)

thanks,

greg k-h

  reply	other threads:[~2017-05-05 17:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 11:57 [PATCH 0/9] [3.18-stable] fixes for all remaining known warnings Arnd Bergmann
2017-05-05 11:57 ` [PATCH 1/9] [3.18-stable] kbuild: mergeconfig: fix "jobserver unavailable" warning Arnd Bergmann
2017-05-05 17:14   ` Greg KH
2017-05-05 17:46     ` Greg KH
2017-05-05 11:57 ` [PATCH 2/9] [3.18-stable] modpost: expand pattern matching to support substring matches Arnd Bergmann
2017-05-05 11:57 ` [PATCH 3/9] [3.18-stable] modpost: don't emit section mismatch warnings for compiler optimizations Arnd Bergmann
2017-05-05 11:57 ` [PATCH 4/9] [3.18-stable] cpumask_set_cpu_local_first => cpumask_local_spread, lament Arnd Bergmann
2017-05-05 11:57 ` [PATCH 5/9] [3.18-stable] e1000e: fix call to do_div() to use u64 arg Arnd Bergmann
2017-05-05 11:57 ` [PATCH 6/9] [3.18-stable] scsi: advansys: remove #warning message Arnd Bergmann
2017-05-05 17:43   ` Greg KH
2017-05-05 17:47   ` Patch "scsi: advansys: remove #warning message" has been added to the 3.18-stable tree gregkh
2017-05-05 11:57 ` [PATCH 7/9] [3.18-stable] i2o: hide unsafe ioctl on 64-bit Arnd Bergmann
2017-05-05 17:13   ` Greg KH [this message]
2017-05-05 18:36     ` Arnd Bergmann
2017-05-05 20:07       ` Greg KH
2017-05-05 11:57 ` [PATCH 8/9] [3.18-stable] staging: unisys: correctly handle return value from queue_delayed_work() Arnd Bergmann
2017-05-05 17:44   ` Greg KH
2017-05-05 11:57 ` [PATCH 9/9] [3.18-stable] gfs2: remove IS_ERR_VALUE abuse Arnd Bergmann
2017-05-05 17:47   ` Patch "gfs2: remove IS_ERR_VALUE abuse" has been added to the 3.18-stable tree gregkh
2017-05-05 17:48 ` [PATCH 0/9] [3.18-stable] fixes for all remaining known warnings Greg KH

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=20170505171312.GA19034@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=stable@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).