From: Nikhil Kshirsagar <nkshirsa@redhat.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] mdadm: protecting sys_name overflow
Date: Thu, 16 Jun 2016 09:26:03 +0530 [thread overview]
Message-ID: <57622353.1080202@redhat.com> (raw)
In-Reply-To: <wrfjeg7yuwho.fsf@redhat.com>
Hi Jes,
Apologies for the wrong indentation. I will re-post the patch.
Thanks,
nikhil.
On 06/16/2016 12:10 AM, Jes Sorensen wrote:
> Nikhil Kshirsagar <nkshirsa@redhat.com> writes:
>> Hello,
>>
>> Devices with names larger than 31 bytes will overflow the sys_name array.
>>
>> This patch enables mdadm to fail and log a message if a long device name
>> is going to cause a buffer overflow.
>>
>> Signed-off-by: Nikhil Kshirsagar <nkshirsa@redhat.com>
>>
>> From 705aec84c6abf5b09c4202aec7cade9824ca7f12 Mon Sep 17 00:00:00 2001
>> From: root <root@nkshirsa.pnq.csb>
>> Date: Wed, 15 Jun 2016 15:23:12 +0530
>> Subject: [PATCH] Protecting overflow of sys_name. If a long device name is
>> going to cause a buffer overflow, we fail with a log message.
>>
>> ---
>> sysfs.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/sysfs.c b/sysfs.c
>> index 8379ca8..68b8b95 100644
>> --- a/sysfs.c
>> +++ b/sysfs.c
>> @@ -283,6 +283,15 @@ struct mdinfo *sysfs_read(int fd, char *devnm, unsigned long options)
>> }
>>
>> }
>> + /* strlen computes length of string *not* including the terminating null character. */
>> +
>> + if(strlen(de->d_name) >= sizeof(dev->sys_name))
>> + {
>> + pr_err("Device name %s larger than currently supported by mdadm\n",de->d_name);
>> + free(dev);
>> + goto abort;
>> +
>> + }
> Nikhil,
>
> Please respect the coding style of mdadm. Code indents at 8 characters
> using a tab, not whitespace, and brackets should be placed correctly.
>
> Just like with kernel code.
>
> Jes
next prev parent reply other threads:[~2016-06-16 3:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 10:09 [PATCH] mdadm: protecting sys_name overflow Nikhil Kshirsagar
2016-06-15 18:40 ` Jes Sorensen
2016-06-16 3:56 ` Nikhil Kshirsagar [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-16 3:59 Nikhil Kshirsagar
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=57622353.1080202@redhat.com \
--to=nkshirsa@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=linux-raid@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).