Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262013AbTHYREs (ORCPT ); Mon, 25 Aug 2003 13:04:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262028AbTHYREs (ORCPT ); Mon, 25 Aug 2003 13:04:48 -0400 Received: from havoc.gtf.org ([63.247.75.124]:44746 "EHLO havoc.gtf.org") by vger.kernel.org with ESMTP id S262013AbTHYREn (ORCPT ); Mon, 25 Aug 2003 13:04:43 -0400 Date: Mon, 25 Aug 2003 13:04:41 -0400 From: Jeff Garzik To: J?rn Engel Cc: Dan Aloni , Linux Kernel List Subject: Re: [BK PATCH] One strdup() to rule them all Message-ID: <20030825170441.GA7097@gtf.org> References: <20030825161435.GB8961@callisto.yi.org> <20030825163745.GA17608@wohnheim.fh-wedel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030825163745.GA17608@wohnheim.fh-wedel.de> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1189 Lines: 42 On Mon, Aug 25, 2003 at 06:37:45PM +0200, J?rn Engel wrote: > On Mon, 25 August 2003 19:14:35 +0300, Dan Aloni wrote: > > > > While working on the fix to network devices names and sysctl, > > I fought to urge to create yet another strdup() implementation > > This came up. > > Nice one. > > > +/** > > + * strdup - Allocate a copy of a string. > > + * @s: The string to copy. Must not be NULL. > > + * > > + * returns the address of the allocation, or NULL on > > + * error. > > + */ > > +char *strdup(const char *s) > > +{ > > + char *rv = kmalloc(strlen(s)+1, GFP_KERNEL); > > + if (rv) > > + strcpy(rv, s); > > + return rv; > > +} > > My gut feeling is always afraid when something "must not be NULL", > someone will ignore this and Bad Things (tm) happen. Is strdup ever > used such performance critical code that the extra check would hurt? > > Apart from that, well done. Rusty created this patch, a long time ago. :) Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/