From: Andrew Morton <akpm@linux-foundation.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Use bigger nodestr to accomodate 32-bit node numbers
Date: Thu, 29 Aug 2013 12:26:48 -0700 [thread overview]
Message-ID: <20130829122648.c23f47e86a0a96ca771c1dc2@linux-foundation.org> (raw)
In-Reply-To: <521F3B44.9030107@suse.de>
On Thu, 29 Aug 2013 07:15:00 -0500 Goldwyn Rodrigues <rgoldwyn@suse.de> wrote:
> > We have the corresponding debugging logic at ocfs2_dismount_volume(), which
> > defines the nodestr with the old size, it seems that this change would cause
> > potential buffer overflow while restore a bigger nodestr at it.
>
> Yes, you are right. I will add the change in ocfs2_dismount_volume() as
> well. Sorry, I missed this.
>
> Andrew: Would you prefer a combined patch or a separate one?
>
It will need to be a separate patch, please.
prev parent reply other threads:[~2013-08-29 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 4:15 [Ocfs2-devel] [PATCH] Use bigger nodestr to accomodate 32-bit node numbers Goldwyn Rodrigues
2013-08-29 9:52 ` Jeff Liu
2013-08-29 12:15 ` Goldwyn Rodrigues
2013-08-29 19:26 ` Andrew Morton [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=20130829122648.c23f47e86a0a96ca771c1dc2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ocfs2-devel@oss.oracle.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).