linux-kernel - Re: [PATCH 31/32] perf, tools: Default to cpu// for events v3

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: <20121128194254.GB27608@infradead.org>
Date:	Wed, 28 Nov 2012 16:42:54 -0300
From:	Arnaldo Carvalho de Melo <acme@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Jiri Olsa <jolsa@...hat.com>, linux-kernel@...r.kernel.org,
	peterz@...radead.org, eranian@...gle.com, mingo@...nel.org,
	namhyung@...nel.org, Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 31/32] perf, tools: Default to cpu// for events v3

Em Wed, Nov 28, 2012 at 08:04:36PM +0100, Andi Kleen escreveu:
> > > +static void str_append(char **s, int *len, const char *a)
> > > +{
> > > +	int olen = *s ? strlen(*s) : 0;
> > > +	int nlen = olen + strlen(a) + 1;
> > > +	if (*len < nlen) {
> > > +		*len = *len * 2;
> > > +		if (*len < nlen)
> > > +			*len = nlen;
> > > +		*s = realloc(*s, *len);
> > > +		if (!*s)
> > > +			exit(ENOMEM);
> > 
> > Rather use BUG_ON or event better return -ENOMEM.
> 
> Neither makes sense: the callers won't handle it and it's not a bug.
> If you're out of memory in user space the only thing you can do is to 
> exit.

Nope, just propagate it back and handle at the callers, the memory
exhaustion may be temporary, just warn the user.

- Arnaldo
 
> > 
> > > +		if (olen == 0)
> > > +			**s = 0;
> > > +	}
> > > +	strcat(*s, a);
> > > +}
> > 
> > Could this one be moved to util/string.c in some generic form?
> 
> Ok.
> 
> -Andi
> 
> -- 
> ak@...ux.intel.com -- Speaking for myself only.
--
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/