All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Theodore Tso <tytso@mit.edu>
Cc: akpm@linux-foundation.org,
	Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: Don't pass stack garbage to filesystem's get_block() in map_bh->b_size
Date: Tue, 12 May 2009 15:07:26 +0100	[thread overview]
Message-ID: <20090512140726.GP8633@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20090512121959.GM21518@mit.edu>

On Tue, May 12, 2009 at 08:19:59AM -0400, Theodore Tso wrote:
> Hmm, I realized that I didn't put the name of the function that was
> misbehaving in the summary line.  So how about changing the patch
> summary to be:
> 
> fs: Fix nobh_truncate_page() to not pass stack garbage to get_block()

OK...  Merged, will push to Linus in the next pile.

  reply	other threads:[~2009-05-12 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 11:37 [PATCH] fs: Don't pass stack garbage to filesystem's get_block() in map_bh->b_size Theodore Ts'o
2009-05-12 12:19 ` Theodore Tso
2009-05-12 14:07   ` Al Viro [this message]
2009-05-12 12:22 ` Dave Kleikamp

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=20090512140726.GP8633@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=shaggy@linux.vnet.ibm.com \
    --cc=tytso@mit.edu \
    /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.