From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 194695] size overflow detected in function ext4_mb_new_group_pa
Date: Tue, 28 Feb 2017 05:28:49 +0000 [thread overview]
Message-ID: <bug-194695-13602-VPhlwpHvHu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194695-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194695
Theodore Tso (tytso@mit.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
--- Comment #2 from Theodore Tso (tytso@mit.edu) ---
I don't think we use the pa_lstart value for group preallocations --- a logical
number doesn't really have meaning for group pa's. That being said, the
preallocation code is really quite a mess, and it makes it hard to follow. We
should really look at cleaning it up....
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2017-02-28 5:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 13:11 [Bug 194695] New: size overflow detected in function ext4_mb_new_group_pa bugzilla-daemon
2017-02-27 20:55 ` [Bug 194695] " bugzilla-daemon
2017-02-28 5:28 ` bugzilla-daemon [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=bug-194695-13602-VPhlwpHvHu@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.