All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: target-devel@vger.kernel.org
Subject: Re: Bug report: KFIFO kfifo_init() may introduce buffer overflow
Date: Thu, 29 Aug 2019 17:21:33 +0000	[thread overview]
Message-ID: <201908291021.DF893CEE5B@keescook> (raw)
In-Reply-To: <20190722114700.GE3089@kadam>

On Tue, Aug 06, 2019 at 06:27:13PM +0800, laokz wrote:
> On Fri, Aug 2, 2019 at 09:30 +0200,Greg KH wrote:
> > On Mon, Jul 22, 2019 at 09:26:23PM +0800, laokz wrote:
> > > Hello Dan,
> > > 
> > > On Mon, Jul 22, 2019 at 14:50 +0300,Dan Carpenter wrote:
> > > > > It looks like you're right.  Probably the fix is to:
> > > > > 1) Change INITIAL_SRP_LIMIT to 8192
> > > > 
> > > > I meant 1024 not 8192.
> > > 
> > > Nice to see that. It really helped for me. Thank you very much.
> > 
> > Did anything ever happen with this?  Was a patch submitted to resolve
> > this issue?
> Sorry for the late reply. I didn't submit any patch, for as newbie I wasn't
> quite sure about the severity of this issue. The developers may do their
> choice.

It's worth fixing regardless. :) Did a patch get sent for this?

-- 
Kees Cook

  parent reply	other threads:[~2019-08-29 17:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 11:47 Bug report: KFIFO kfifo_init() may introduce buffer overflow Dan Carpenter
2019-07-22 11:50 ` Dan Carpenter
2019-08-02  7:30 ` Greg KH
2019-08-29 17:21 ` Kees Cook [this message]
2019-08-29 18:48 ` Linus Torvalds
2019-08-29 19:32 ` Linus Torvalds
2019-08-29 19:40 ` Stefani Seibold
2019-08-29 19:42 ` Kees Cook
2019-08-29 21:51 ` Will Deacon
2019-09-01 17:38 ` Linus Torvalds

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=201908291021.DF893CEE5B@keescook \
    --to=keescook@chromium.org \
    --cc=target-devel@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 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.