All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [PATCH v2 6/8] Stop buffer overflow
Date: Wed, 15 Oct 2014 08:24:26 -0700	[thread overview]
Message-ID: <543E91AA.7070703@linux.intel.com> (raw)
In-Reply-To: 20141015151941.GL1189@swordfish

[-- Attachment #1: Type: text/plain, Size: 845 bytes --]

>
>> the data is still truncated and partial.. and you keep running with it.
>
> which is not that big deal. I agree, that this is not 100% handy.
> but suppose there is a process with very long name. long enough to cause
> overrun and powertop abort(). and that process is part of a runtime and
> it must be alive, etc... and that automatically leaves only one option --
> either that process or powertop. and never together.
>

for cases where you know you can truncate correctly, making a "truncate_string_to(str, n, trailing_pattern)" helper that you
call explicitly is likely a better answer than hiding it inside a sprintf-like makro.
(and you then truncate the source string/content)

but maybe I'm just getting old and grumpy ;-)


also asprintf() for cases where you don't know how long it will be is not a bad idea


             reply	other threads:[~2014-10-15 15:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 15:24 Arjan van de Ven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-15 15:55 [Powertop] [PATCH v2 6/8] Stop buffer overflow Joe Konno
2014-10-15 15:42 Sergey Senozhatsky
2014-10-15 15:19 Sergey Senozhatsky
2014-10-15 15:01 Sergey Senozhatsky
2014-10-15 15:01 Arjan van de Ven
2014-10-15 14:46 Sergey Senozhatsky
2014-10-15 14:34 Arjan van de Ven
2014-10-15 14:21 Sergey Senozhatsky
2014-10-15 14:05 Arjan van de Ven
2014-10-15 14:03 Sergey Senozhatsky
2014-10-15 13:55 Sergey Senozhatsky
2014-10-15 12:54 Sergey Senozhatsky
2014-10-14 18:09 Joe Konno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=543E91AA.7070703@linux.intel.com \
    --to=powertop@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.