From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Nikhil Kshirsagar <nkshirsa@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] mdadm --detail --scan causes SIGABRT
Date: Tue, 14 Jun 2016 13:42:21 -0400 [thread overview]
Message-ID: <wrfjvb1bfz0i.fsf@redhat.com> (raw)
In-Reply-To: <575A4018.8050500@redhat.com> (Nikhil Kshirsagar's message of "Fri, 10 Jun 2016 09:50:40 +0530")
Nikhil Kshirsagar <nkshirsa@redhat.com> writes:
> Please find attached a patch to fix BZ 1343809.
>
> Details:
> mdadm has a buffer overflow if mdinfo->sys_name needs to store a name
> larger than 20 characters.
Nikhil,
I have applied this one, adding the Signed-off-by: line as you
requested and slightly adjusted the patch description.
I would like to include some checking fixes too to avoid us overflowing
the new buffer size with even longer names.
Cheers,
Jes
prev parent reply other threads:[~2016-06-14 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 4:20 [PATCH] mdadm --detail --scan causes SIGABRT Nikhil Kshirsagar
2016-06-10 15:43 ` Nikhil Kshirsagar
2016-06-10 17:11 ` Jes Sorensen
2016-06-10 17:41 ` Nikhil Kshirsagar
2016-06-10 17:48 ` Jes Sorensen
2016-06-10 18:12 ` Nikhil Kshirsagar
2016-06-13 12:32 ` Nikhil Kshirsagar
2016-06-14 17:42 ` Jes Sorensen [this message]
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=wrfjvb1bfz0i.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=nkshirsa@redhat.com \
/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).