linux-kernel - Re: [RFC] configfs: Allow ->make_item() and ->make

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080612223803.GB4012@localdomain>
Date:	Fri, 13 Jun 2008 00:38:03 +0200
From:	Louis Rilling <Louis.Rilling@...labs.com>
To:	Joel Becker <joel.becker@...cle.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	ocfs2-devel@....oracle.com, cluster-devel@...hat.com,
	teigland@...hat.com
Subject: Re: [RFC] configfs: Allow ->make_item() and ->make_group() to
	return detailed errors.

On Thu, Jun 12, 2008 at 02:19:55PM -0700, Joel Becker wrote:
> The configfs operations ->make_item() and ->make_group() currently
> return a new item/group.  A return of NULL signifies an error.  Because
> of this, -ENOMEM is the only return code bubbled up the stack.
> 
> Multiple folks have requested the ability to return specific error codes
> when these operations fail.  This patch adds that ability by changing the
> ->make_item/group() ops to return an int.
> 
> Also updated are the in-kernel users of configfs.
> 
> Signed-off-by: Joel Becker <joel.becker@...cle.com>

Looks good to me. Happy to see this change coming :)

Louis

-- 
Dr Louis Rilling			Kerlabs - IRISA
Skype: louis.rilling			Campus Universitaire de Beaulieu
Phone: (+33|0) 2 99 84 71 52		Avenue du General Leclerc
Fax: (+33|0) 2 99 84 71 71		35042 Rennes CEDEX - France
http://www.kerlabs.com/
--
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/