From: Dave Jones <davej@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: fs: remove now stale label in anon_inode_init()
Date: Wed, 26 Mar 2014 13:33:56 -0400 [thread overview]
Message-ID: <20140326173356.GA16013@redhat.com> (raw)
In-Reply-To: <20140326004510.D4C236604A2@gitolite.kernel.org>
On Wed, Mar 26, 2014 at 12:45:10AM +0000, Linux Kernel wrote:
> Gitweb: http://git.kernel.org/linus/;a=commit;h=fce7fc79c8f7188dfc5eafa1b937bcc3c5a4c2f5
> Commit: fce7fc79c8f7188dfc5eafa1b937bcc3c5a4c2f5
> Parent: d6f2589ad561aa5fa39f347eca6942668b7560a1
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> AuthorDate: Tue Mar 25 17:43:34 2014 -0700
> Committer: Linus Torvalds <torvalds@linux-foundation.org>
> CommitDate: Tue Mar 25 17:43:34 2014 -0700
>
> fs: remove now stale label in anon_inode_init()
>
> The previous commit removed the register_filesystem() call and the
> associated error handling, but left the label for the error path that no
> longer exists. Remove that too.
>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> ---
> fs/anon_inodes.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/fs/anon_inodes.c b/fs/anon_inodes.c
> index 4b4543b..42fcc46 100644
> --- a/fs/anon_inodes.c
> +++ b/fs/anon_inodes.c
> @@ -186,7 +186,6 @@ static int __init anon_inode_init(void)
>
> err_unregister_filesystem:
> unregister_filesystem(&anon_inode_fs_type);
> -err_exit:
> panic(KERN_ERR "anon_inode_init() failed (%d)\n", error);
If we're about to panic, is there any point in doing the unregister ?
Looks like that function could just be..
anon_inode_mnt = kern_mount(&anon_inode_fs_type);
if (IS_ERR(anon_inode_mnt)) {
error = PTR_ERR(anon_inode_mnt);
panic(KERN_ERR "anon_inode_init() failed (%d)\n", error);
}
return 0;
parent reply other threads:[~2014-03-26 17:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20140326004510.D4C236604A2@gitolite.kernel.org>]
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=20140326173356.GA16013@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome