linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Dan Carpenter <error27@gmail.com>
Cc: error27@gmail.com, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: bug list: putting too much data on the stack
Date: Thu, 11 Feb 2010 11:03:54 +0100	[thread overview]
Message-ID: <E1NfVtq-0002pE-8A@pomaz-ex.szeredi.hu> (raw)
In-Reply-To: <20100211085120.GF14210@bicker> (message from Dan Carpenter on Thu, 11 Feb 2010 11:51:20 +0300)

Dan,

On Thu, 11 Feb 2010, Dan Carpenter wrote:
> fs/fuse/dev.c +888 fuse_notify_inval_entry(5) warn: 'buf' puts 1025 bytes on stack

The fix for this is already in linux-next.

Thanks,
Miklos

  reply	other threads:[~2010-02-11 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11  8:51 bug list: putting too much data on the stack Dan Carpenter
2010-02-11 10:03 ` Miklos Szeredi [this message]
2010-02-11 17:01 ` Randy Dunlap

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=E1NfVtq-0002pE-8A@pomaz-ex.szeredi.hu \
    --to=miklos@szeredi.hu \
    --cc=error27@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@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).