From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] werc memory over flow
Date: Sat, 12 Mar 2022 13:34:31 +0100 [thread overview]
Message-ID: <E1ED69C19FDE2025CC3051F1DDD7E6C7@felloff.net> (raw)
In-Reply-To: <CC7138DE00DDE7F6259D949AFAE27A21@felloff.net>
arg, also have to not do this:
- *pb = '\0';
setsval(x, buf); /* BUG: should be able to avoid copy + free */
was already been done by the copy loop before:
while ((*pb++ = *sptr++) != 0)
;
i commited the fix now.
please report if that fixes the issue.
--
cinap
next prev parent reply other threads:[~2022-03-13 9:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 6:24 william
2022-03-11 6:33 ` ori
2022-03-11 15:18 ` ori
2022-03-12 11:23 ` cinap_lenrek
2022-03-12 11:54 ` cinap_lenrek
2022-03-12 12:34 ` cinap_lenrek [this message]
2022-03-13 7:27 ` william
2022-03-13 21:16 ` cinap_lenrek
2022-03-12 13:27 ` Steve Simon
2022-03-12 14:38 ` Steffen Nurpmeso
2022-03-11 16:49 ` Nick Owens
2022-03-11 20:13 ` cinap_lenrek
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=E1ED69C19FDE2025CC3051F1DDD7E6C7@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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 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).