From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Robert LeBlanc <robert@leblancnet.us>
Cc: linux-raid@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [PATCH v2] mdopen: Prevent overrunning the devname buffer when copying devnm into it for long md names.
Date: Thu, 25 Aug 2016 13:45:23 -0400 [thread overview]
Message-ID: <wrfjfups7nf0.fsf@redhat.com> (raw)
In-Reply-To: <20160824161044.20887-1-robert@leblancnet.us> (Robert LeBlanc's message of "Wed, 24 Aug 2016 10:10:44 -0600")
Robert LeBlanc <robert@leblancnet.us> writes:
> Linux allows for 32 character device names. When using the maximum size device name and also
> storing "/dev/", devname needs to be 37 character long to store the complete device name.
> i.e. "/dev/md_abcdefghijklmnopqrstuvwxyz12\0"
>
> Signed-Off: Robert LeBlanc<robert@leblancnet.us>
> ---
> mdopen.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Looks good - I corrected your comment to fit into a proper editor width
of 80 characters, and also fixed up the SOB since it needs to say
Signed-off-by rather than signed-off.
Applied!
Jes
prev parent reply other threads:[~2016-08-25 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 16:10 [PATCH v2] mdopen: Prevent overrunning the devname buffer when copying devnm into it for long md names Robert LeBlanc
2016-08-25 7:44 ` Shaun Tancheff
2016-08-25 7:52 ` [dm-devel] " Shaun Tancheff
2016-08-25 17:45 ` 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=wrfjfups7nf0.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=robert@leblancnet.us \
/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