From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org,
viro@parcelfarce.linux.theplanet.co.uk, ak@suse.de
Subject: Re: [PATCH] zero out i_blocks in get_pipe_inode
Date: Tue, 11 Nov 2003 15:36:14 -0800 [thread overview]
Message-ID: <51260000.1068593774@flay> (raw)
In-Reply-To: <20031111144842.137e396e.akpm@osdl.org>
>> + inode->i_blocks = 0;
>
> alloc_inode() already did that.
Sigh ... yes, you're right - sorry.
get_pipe_inode -> new_inode -> alloc_inode. definitely covered.
I shall crawl back under my regularly scheduled stone ;-)
M.
prev parent reply other threads:[~2003-11-11 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 23:04 [PATCH] zero out i_blocks in get_pipe_inode Martin J. Bligh
2003-11-11 22:48 ` Andrew Morton
2003-11-11 22:50 ` Andi Kleen
2003-11-11 23:36 ` Martin J. Bligh [this message]
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=51260000.1068593774@flay \
--to=mbligh@aracnet.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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