From: Hareesh Nagarajan <hnagar2@gmail.com>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: [TRIVIAL] Error checks omitted in init_tmpfs() in mm/tiny-shmem.c
Date: Mon, 24 Oct 2005 19:16:50 -0500 [thread overview]
Message-ID: <435D7972.7020102@gmail.com> (raw)
In-Reply-To: <20051024204518.GI26160@waste.org>
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
Matt Mackall wrote:
> On Mon, Oct 24, 2005 at 03:56:47AM -0500, Hareesh Nagarajan wrote:
>> Matt Mackall wrote:
>>> On Mon, Oct 24, 2005 at 12:29:45AM -0500, Hareesh Nagarajan wrote:
>>>> The existing code in init_tmpfs() in mm/tiny-shmem.c does not handle the
>>>> cases when the calls to register_filesystem() and kern_mount() fail.
>>>> This patch adds those checks.
[ Snip ]
> A couple more comments..
>
>> Signed-off-by: Hareesh Nagarajan <hnagar2@gmail.com>
>
>> --- linux-2.6.13.4/mm/tiny-shmem.c 2005-10-10 13:54:29.000000000 -0500
>> +++ linux-2.6.13.4-edit/mm/tiny-shmem.c 2005-10-24 03:43:38.614071000 -0500
>> @@ -31,12 +31,18 @@
>>
>> static int __init init_tmpfs(void)
>> {
>> - register_filesystem(&tmpfs_fs_type);
>> + int error;
>> +
>> + error = register_filesystem(&tmpfs_fs_type);
>> + BUG_ON(error);
>
> Can we just do BUG_ON(register_filesystem() != 0)?
>
> Strictly speaking, the != 0 is redundant, but as this goes slightly
> against the grain of normal usage, it's a good indicator of intent.
It shows intent well. That goes into my book for good programming
practices. No more BUG_ON(foo) :)
>> #ifdef CONFIG_TMPFS
>> devfs_mk_dir("shm");
>> #endif
>> shm_mnt = kern_mount(&tmpfs_fs_type);
>> - return 0;
>> + BUG_ON(IS_ERR(shm_mnt));
>> +
>> + return error;
>
> We can never return non-zero here. Returning error implies we can, so
> it's confusing.
Makes sense again. Patch follows.
Signed-off-by: Hareesh Nagarajan <hnagar2@gmail.com>
[-- Attachment #2: tiny-shmmem-fix-ver3.patch --]
[-- Type: text/x-patch, Size: 462 bytes --]
--- linux-2.6.13.4/mm/tiny-shmem.c 2005-10-10 13:54:29.000000000 -0500
+++ linux-2.6.13.4-edit/mm/tiny-shmem.c 2005-10-24 19:05:28.058897000 -0500
@@ -31,11 +31,14 @@
static int __init init_tmpfs(void)
{
- register_filesystem(&tmpfs_fs_type);
+ BUG_ON(register_filesystem(&tmpfs_fs_type) != 0);
+
#ifdef CONFIG_TMPFS
devfs_mk_dir("shm");
#endif
shm_mnt = kern_mount(&tmpfs_fs_type);
+ BUG_ON(IS_ERR(shm_mnt));
+
return 0;
}
module_init(init_tmpfs)
prev parent reply other threads:[~2005-10-25 0:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 5:29 [TRIVIAL] Error checks omitted in init_tmpfs() in mm/tiny-shmem.c Hareesh Nagarajan
2005-10-24 7:09 ` Matt Mackall
2005-10-24 8:56 ` Hareesh Nagarajan
2005-10-24 20:45 ` Matt Mackall
2005-10-24 21:00 ` Muli Ben-Yehuda
2005-10-24 21:08 ` Matt Mackall
2005-10-25 0:16 ` Hareesh Nagarajan [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=435D7972.7020102@gmail.com \
--to=hnagar2@gmail.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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