linux-kernel - Re: [Pv-drivers] [PATCH 04/12] VMCI: device driver implementaton.

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]

Message-ID: <20121030154940.GD14167@kroah.com>
Date:	Tue, 30 Oct 2012 08:49:40 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Dmitry Torokhov <dtor@...are.com>
Cc:	George Zhang <georgezhang@...are.com>, pv-drivers@...are.com,
	linux-kernel@...r.kernel.org,
	virtualization@...ts.linux-foundation.org
Subject: Re: [Pv-drivers] [PATCH 04/12] VMCI: device driver implementaton.

On Mon, Oct 29, 2012 at 09:15:22PM -0700, Dmitry Torokhov wrote:
> On Mon, Oct 29, 2012 at 07:23:47PM -0700, Greg KH wrote:
> > On Mon, Oct 29, 2012 at 06:04:15PM -0700, George Zhang wrote:
> > > +static int __init vmci_core_init(void)
> > > +{
> > > +	int result;
> > > +
> > > +	result = vmci_ctx_init();
> > > +	if (result < VMCI_SUCCESS) {
> > > +		pr_err("Failed to initialize VMCIContext (result=%d).\n",
> > > +			result);
> > 
> > If you are going to use pr_* functions, it's usually a good idea to
> > define pr_fmt in a consistant way so that it shows up the same across
> > all of your .c files.  See other drivers for examples of how to do this
> > properly.
> 
> pr_fmt() is defined in drivers/misc/vmw_vmci/vmci_common_int.h

I think that is too late in the #include file chain, shouldn't it be set
before any #include files are called?

> > > +		return -EINVAL;
> > > +	}
> > > +
> > > +	result = vmci_datagram_init();
> > > +	if (result < VMCI_SUCCESS) {
> > > +		pr_err("Failed to initialize VMCIDatagram (result=%d).\n",
> > > +			result);
> > > +		return -EINVAL;
> > > +	}
> > > +
> > > +	result = vmci_event_init();
> > > +	if (result < VMCI_SUCCESS) {
> > > +		pr_err("Failed to initialize VMCIEvent (result=%d).\n", result);
> > > +		return -EINVAL;
> > > +	}
> > 
> > You don't free and unwind things properly if things go wrong here, why
> > not?
> 
> We do, the above calls do not need to be cleaned up.

Ah, that's helpful :)

> > > +	return 0;
> > > +}
> > > +
> > > +static void __exit vmci_core_exit(void)
> > > +{
> > > +	vmci_event_exit();
> > > +}
> > > +
> > > +static int __init vmci_drv_init(void)
> > > +{
> > > +	int error;
> > > +
> > > +	error = vmci_core_init();
> > > +	if (error)
> > > +		return error;
> > > +
> > > +	if (!vmci_disable_guest) {
> > > +		error = vmci_guest_init();
> > > +		if (error) {
> > > +			pr_warn("Failed to initialize guest personality (err=%d).\n",
> > > +				error);
> > > +		} else {
> > > +			vmci_guest_personality_initialized = true;
> > > +			pr_info("Guest personality initialized and is %s\n",
> > > +				vmci_guest_code_active() ?
> > > +				"active" : "inactive");
> > > +		}
> > > +	}
> > > +
> > > +	if (!vmci_disable_host) {
> > > +		error = vmci_host_init();
> > > +		if (error) {
> > > +			pr_warn("Unable to initialize host personality (err=%d).\n",
> > > +				error);
> > > +		} else {
> > > +			vmci_host_personality_initialized = true;
> > > +			pr_info("Initialized host personality\n");
> > > +		}
> > > +	}
> > > +
> > > +	if (!vmci_guest_personality_initialized &&
> > > +	    !vmci_host_personality_initialized) {
> > > +		vmci_core_exit();
> > > +		return -ENODEV;
> > > +	}
> > > +
> > > +	pr_debug("Module is initialized\n");
> > 
> > Really?  You need this message still?
> 
> These are debug messages so do not show up in logs by default.

I know, but even if you do enable debugging, are such things really
needed?  They look like left-over tracing function calls to me.

thanks,

greg k-h
--
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/