Return-path: Received: from mail.kernel.org ([198.145.29.99]:41906 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751057AbeFAIEI (ORCPT ); Fri, 1 Jun 2018 04:04:08 -0400 Date: Fri, 1 Jun 2018 10:03:46 +0200 From: Greg Kroah-Hartman To: Mark Greer Cc: Johan Hovold , Arend van Spriel , Carlos Manuel Santos , Samuel Ortiz , Stephen Hemminger , linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org Subject: Re: [PATCH v4] NFC: pn533: don't send USB data off of the stack Message-ID: <20180601080346.GC12809@kroah.com> (sfid-20180601_100414_423390_7294A91A) References: <20180520131946.GA7325@kroah.com> <20180521083825.GO30172@localhost> <20180531103848.GB31952@kroah.com> <20180601040632.GA14834@animalcreek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20180601040632.GA14834@animalcreek.com> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, May 31, 2018 at 09:06:32PM -0700, Mark Greer wrote: > On Thu, May 31, 2018 at 12:38:48PM +0200, Greg Kroah-Hartman wrote: > > On Mon, May 21, 2018 at 10:38:25AM +0200, Johan Hovold wrote: > > > On Sun, May 20, 2018 at 03:19:46PM +0200, Greg Kroah-Hartman wrote: > > > > It's amazing that this driver ever worked, but now that x86 doesn't > > > > allow USB data to be sent off of the stack, it really does not work at > > > > all. Fix this up by properly allocating the data for the small > > > > "commands" that get sent to the device off of the stack. > > > > > > > > We do this for one command by having a whole urb just for ack messages, > > > > as they can be submitted in interrupt context, so we can not use > > > > usb_bulk_msg(). But the poweron command can sleep (and does), so use > > > > usb_bulk_msg() for that transfer. > > > > > > > > Reported-by: Carlos Manuel Santos > > > > Cc: Samuel Ortiz > > > > Cc: Stephen Hemminger > > > > Cc: stable > > > > Signed-off-by: Greg Kroah-Hartman > > > > --- > > > > v4: don't use urb transfer buffer flags as the memory is tied to the urb > > > > (thanks to Johan) Now we have a new static urb, and we use > > > > usb_bulk_msg() for the other message. > > > > v3: actually use the correct buffer (thanks to Arend van Spriel) > > > > use kmemdup (thanks to Johannes Berg and Julia Lawall) > > > > v2: set the urb flags correctly > > > > > > Your changes look correct now so feel free to add: > > > > > > Reviewed-by: Johan Hovold > > > > Thanks for the review. > > > > > It seems we could end up returning an errno from probe with active urbs > > > (if pn533_finalize_setup() fails) in which case the ack buffer would > > > leak. But freeing the urbs while active would then be the bigger > > > problem, and that wasn't introduced by this patch. > > > > Yeah, this whole thing is a mess and I really don't want to do much more > > to the driver without having the hardware to test with it. So I'll just > > leave it as-is for now :) > > Hi Greg. > > I have a pn533 USB stick, a trf7970-based board, and some nfc tags so I > can help you test as long as you don't mind multi-day turn-around times. > Alternatively, I can set something up and give you remote access, if you > prefer that. > > Let me know. multi-day turn arounds are fine. But given that this driver has been broken for a very long time with no one noticing, I doubt that there are many, if any, real users out there to make it worth working on at the moment to fix up minor code quality issues :( thanks, greg k-h