From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] possible buffer overflow in devcons.c?
Date: Wed, 18 Jun 2014 14:18:50 -0400 [thread overview]
Message-ID: <ac140ab82bbe7f0c4c62afeaa9942eab@brasstown.quanstro.net> (raw)
In-Reply-To: <229B5D7C-7229-4C18-8967-3D1FC9AFD373@fb.com>
On Wed Jun 18 14:15:14 EDT 2014, pad@fb.com wrote:
> Well, hard to grep for '3' in a big codebase. They should have used UTFMAX in the first place.
>
it's not hard. i did this once. i think i did something like this
g 'char[ ]+[a-z]+\[(3|4|3\+1)\]' /sys/src
- erik
next prev parent reply other threads:[~2014-06-18 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 17:29 Yoann Padioleau
2014-06-18 17:34 ` erik quanstrom
2014-06-18 17:34 ` andrey mirtchovski
2014-06-18 17:36 ` erik quanstrom
2014-06-18 18:13 ` Yoann Padioleau
2014-06-18 18:18 ` erik quanstrom [this message]
2014-06-18 18:44 ` erik quanstrom
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=ac140ab82bbe7f0c4c62afeaa9942eab@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).