lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 5 Mar 2007 11:58:29 -0800
From:	Joel Becker <Joel.Becker@...cle.com>
To:	Akinobu Mita <akinobu.mita@...il.com>,
	linux-kernel@...r.kernel.org, Mark Fasheh <mark.fasheh@...cle.com>,
	Kurt Hackel <kurt.hackel@...cle.com>
Subject: Re: [PATCH] ocfs2: fix module_init error handling

On Sun, Mar 04, 2007 at 10:34:43PM +0900, Akinobu Mita wrote:
> From: Akinobu Mita <akinobu.mita@...il.com>
> Subject: [PATCH] ocfs2: fix module_init error handling
> 
> Fix error handling in module_init and make module_init() return
> correct error code.

	What are you fixing specifically?  This looks like you are
reorganizing the exit path.  While stylistic differences can exist on
the choice of function exit, claiming there is a "fix" means there is an
actual bug.  Please clarify the bug so we can evaluate your change.

> -leave:
> -	if (status < 0) {
> -		ocfs2_free_mem_caches();
> -		exit_ocfs2_uptodate_cache();
> -		exit_ocfs2_extent_maps();
> -	}
> +	status = register_filesystem(&ocfs2_fs_type);
> +	if (status)
> +		goto err_filesystem;
>  
>  	mlog_exit(status);

	Also, this change suppresses some paths to mlog_exit(), which
impacts people tracing.
	If there is an actual bug you are fixing, please tell us.  We'll
work with you to correct it.

Joel

-- 

Life's Little Instruction Book #451

	"Don't be afraid to say, 'I'm sorry.'"

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@...cle.com
Phone: (650) 506-8127
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ