All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Maksim Salau <maksim.salau@gmail.com>
Cc: Juergen Stuber <starblue@users.sourceforge.net>,
	legousb-devel@lists.sourceforge.net, linux-usb@vger.kernel.org,
	Alfredo Rafael Vicente Boix <alviboi@gmail.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] usb: misc: legousbtower: Fix buffers on stack
Date: Tue, 25 Apr 2017 20:04:24 +0200	[thread overview]
Message-ID: <20170425180424.GA899@kroah.com> (raw)
In-Reply-To: <20170422162437.6420-1-maksim.salau@gmail.com>

On Sat, Apr 22, 2017 at 07:24:37PM +0300, Maksim Salau wrote:
> Allocate buffers on HEAP instead of STACK for local structures
> that are to be received using usb_control_msg().
> 
> Signed-off-by: Maksim Salau <maksim.salau@gmail.com>
> Tested-by: Alfredo Rafael Vicente Boix <alviboi@gmail.com>
> Cc: stable@vger.kernel.org

This patch does not apply to usb-next, what did you make it against?

Can you rebase it and resend?

thanks,

greg k-h

  reply	other threads:[~2017-04-25 18:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAE+v5Of10hZOEC8zyhVgszWmBaFzcMjqCGdLSDJEKjWwt9F+sg@mail.gmail.com>
2017-04-22 16:24 ` [PATCH v2] usb: misc: legousbtower: Fix buffers on stack Maksim Salau
2017-04-25 18:04   ` Greg Kroah-Hartman [this message]
2017-04-25 19:28     ` Maksim Salau
2017-04-25 19:49       ` [PATCH v3] " Maksim Salau
2017-04-26  9:29         ` Greg Kroah-Hartman
2017-04-27  6:30           ` Maksim Salau
2017-05-04 12:36         ` Heikki Krogerus
2017-05-04 19:11           ` Maksim Salau
2017-04-26  9:28       ` [PATCH v2] " Greg Kroah-Hartman

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=20170425180424.GA899@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alviboi@gmail.com \
    --cc=legousb-devel@lists.sourceforge.net \
    --cc=linux-usb@vger.kernel.org \
    --cc=maksim.salau@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=starblue@users.sourceforge.net \
    /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.