All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Petko Manolov <petkan@nucleusys.com>
Cc: "Ben Hutchings" <ben@decadent.org.uk>,
	netdev@vger.kernel.org, linux-usb@vger.kernel.org,
	"Lisandro Damián Nicanor Pérez Meyer" <lisandro@debian.org>
Subject: Re: [PATCH net 1/4] pegasus: Use heap buffers for all register access
Date: Mon, 6 Feb 2017 09:28:22 +0100	[thread overview]
Message-ID: <20170206082822.GA23451@kroah.com> (raw)
In-Reply-To: <20170206081444.smcgjkmdepxoosb6@p310>

On Mon, Feb 06, 2017 at 10:14:44AM +0200, Petko Manolov wrote:
> On 17-02-05 01:30:39, Greg KH wrote:
> > On Sat, Feb 04, 2017 at 04:56:03PM +0000, Ben Hutchings wrote:
> > > Allocating USB buffers on the stack is not portable, and no longer
> > > works on x86_64 (with VMAP_STACK enabled as per default).
> > 
> > It's never worked on other platforms, so these should go to the stable 
> > releases please.
> 
> As far as i know both drivers works fine on other platforms, though I only 
> tested it on arm and mipsel. ;)

It all depends on the arm and mips platforms, the ones that can not DMA
from stack memory are the ones that would always fail here (since the
2.2 kernel days).

> Random thought: isn't it better to add the alloc/free code in usb_control_msg() 
> and avoid code duplication all over the driver space?

A very long time ago we considered it, but realized that the majority of
drivers already had the memory dynamically allocated, so we just went
with this.  Perhaps we could revisit that if it turns out we were wrong,
and would simplify things.

thanks,

greg k-h

  reply	other threads:[~2017-02-06  8:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-04 16:54 [PATCH net 0/4] Fix on-stack USB buffers Ben Hutchings
2017-02-04 16:56 ` [PATCH net 1/4] pegasus: Use heap buffers for all register access Ben Hutchings
2017-02-05  0:30   ` Greg KH
2017-02-06  8:14     ` Petko Manolov
2017-02-06  8:28       ` Greg KH [this message]
2017-02-06 12:51         ` Petko Manolov
2017-02-06 13:21           ` Johan Hovold
2017-02-06 13:32             ` Johan Hovold
2017-02-06 13:46               ` Johan Hovold
2017-02-07 10:24                 ` Petko Manolov
2017-02-07 10:45                   ` Greg KH
     [not found]                     ` <20170207104506.GB32583-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-02-07 12:50                       ` Petko Manolov
2017-02-06 13:30           ` David Laight
2017-02-07 18:32           ` Steve Calfee
2017-02-08  7:57             ` Petko Manolov
2017-02-04 16:56 ` [PATCH net 2/4] rtl8150: " Ben Hutchings
2017-02-06  8:10   ` Petko Manolov
     [not found]   ` <20170204165631.GW3442-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
2017-02-06 16:09     ` David Laight
2017-02-06 16:25       ` Ben Hutchings
2017-02-07 10:34         ` Petko Manolov
2017-02-07 10:51           ` Greg KH
2017-02-07 11:56             ` David Laight
     [not found]               ` <063D6719AE5E284EB5DD2968C1650D6DB027DB75-VkEWCZq2GCInGFn1LkZF6NBPR1lH4CV8@public.gmane.org>
2017-02-07 12:42                 ` 'Greg KH'
2017-02-07 12:53             ` Petko Manolov
2017-02-07 13:01               ` Greg KH
2017-02-07 13:20                 ` Petko Manolov
2017-02-07 14:14                   ` David Laight
2017-02-07 14:52                     ` Petko Manolov
     [not found] ` <20170204165451.GU3442-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
2017-02-04 16:56   ` [PATCH net 3/4] catc: Combine failure cleanup code in catc_probe() Ben Hutchings
2017-02-04 16:57 ` [PATCH net 4/4] catc: Use heap buffer for memory size test Ben Hutchings
2017-02-07 15:07 ` [PATCH net 0/4] Fix on-stack USB buffers David Miller

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=20170206082822.GA23451@kroah.com \
    --to=greg@kroah.com \
    --cc=ben@decadent.org.uk \
    --cc=linux-usb@vger.kernel.org \
    --cc=lisandro@debian.org \
    --cc=netdev@vger.kernel.org \
    --cc=petkan@nucleusys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.