From mboxrd@z Thu Jan  1 00:00:00 1970
From: Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH] export kernel call set_task_comm()
Date: Thu, 31 May 2012 17:00:54 +0100
Message-ID: <20120531160054.GG11775@ZenIV.linux.org.uk>
References: <201205311516140150468@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
To: majianpeng <majianpeng@gmail.com>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from zeniv.linux.org.uk ([195.92.253.2]:37153 "EHLO
	ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S932634Ab2EaQAz (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Thu, 31 May 2012 12:00:55 -0400
Content-Disposition: inline
In-Reply-To: <201205311516140150468@gmail.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Thu, May 31, 2012 at 03:16:18PM +0800, majianpeng wrote:
> In Commit 7d74f492e4dd0034a61458eb80f70b1d2862ed07,author said:
> "This allows drivers who call this function to be compiled modularly.
> Otherwise, a driver who is interested in this type of functionality
> has to implement their own get_task_comm() call, causing code
> duplication in the Linux source tree."
> 
> But author did not say about set_task_comm().At present,I used it but
> compiled error.To the same purpose, it should export.

Are you doing that to preexisting process?  Or just to a kernel thread
you are creating?  In the latter case, you really ought to use
kthread_create() instead of bare-metal kernel_thread()...