From: Jim Meyering <jim@meyering.net>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-progs: minor buffer-overrun fixes (v2)
Date: Fri, 20 Apr 2012 21:27:22 +0200 [thread overview]
Message-ID: <1334950046-24147-1-git-send-email-jim@meyering.net> (raw)
Same net result as before, but with the stray-parenthesis fix
moved to 2/4 where it belongs, rather than buried in 3/4.
Thanks to Josef for the reviews.
Also, I fixed this in 3/4:
- args.name[BTRFS_PATH_NAME_MAX-1] = 0;
+ args.name[BTRFS_SUBVOL_NAME_MAX-1] = 0;
[PATCHv2 1/4] mkfs: use strdup in place of strlen,malloc,strcpy
[PATCHv2 2/4] restore: don't corrupt stack for a zero-length
[PATCHv2 3/4] avoid several strncpy-induced buffer overruns
[PATCHv2 4/4] mkfs: avoid heap-buffer-read-underrun for zero-length
next reply other threads:[~2012-04-20 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 19:27 Jim Meyering [this message]
2012-04-20 19:27 ` [PATCHv2 1/4] mkfs: use strdup in place of strlen,malloc,strcpy sequence Jim Meyering
2012-04-20 19:27 ` [PATCHv2 2/4] restore: don't corrupt stack for a zero-length command-line argument Jim Meyering
2012-04-20 19:27 ` [PATCHv2 3/4] avoid several strncpy-induced buffer overruns Jim Meyering
2012-06-06 19:31 ` Hugo Mills
2012-06-06 19:40 ` Hugo Mills
2012-06-06 21:08 ` Jim Meyering
2012-06-11 12:05 ` [PATCHv4 " Jim Meyering
2012-04-20 19:27 ` [PATCHv2 4/4] mkfs: avoid heap-buffer-read-underrun for zero-length "size" arg Jim Meyering
2012-06-06 19:35 ` Hugo Mills
2012-06-07 14:12 ` Jim Meyering
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=1334950046-24147-1-git-send-email-jim@meyering.net \
--to=jim@meyering.net \
--cc=linux-btrfs@vger.kernel.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).