From: Tristan Ye <tristan.ye@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/2] Ocfs2/move_extents: Validate moving goal after the adjustment.
Date: Wed, 27 Apr 2011 22:06:02 -0000 [thread overview]
Message-ID: <4DF42CEF.6020704@oracle.com> (raw)
In-Reply-To: <20110611195742.GA2141@mako-laptop>
On 06/12/2011 03:57 AM, Mariusz Kozlowski wrote:
> Hi,
>
> I think this one (ea5e1675 upstream) is wrong. Validation was moved
> before 'bg' was assinged any sane value. Also 'bg' is defined with NULL
> now so it hides real problem that 'bg' is used uninitialized. So currently
> as 'bg' is NULL from the begining it will blow up with null pointer
> dereference somewhere around test in line 489:
You're definitely correct, I'm blaming myself for not making things in
order after moving the validation logic backwards a bit, thanks so much
for pointing this out.
Tristan.
>
> 489: if (range->me_goal == le64_to_cpu(bg->bg_blkno))
> 490: range->me_goal += c_to_b;
>
> Sorry for reply with no context but I'm not subscribed to ocfs2-devel.
next prev parent reply other threads:[~2011-04-27 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 19:57 [Ocfs2-devel] [PATCH 2/2] Ocfs2/move_extents: Validate moving goal after the adjustment Mariusz Kozlowski
2011-04-27 22:06 ` Tristan Ye [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-27 6:32 [Ocfs2-devel] [PATCH 1/2] Ocfs2/move_extents: Avoid doing division in extent moving Tristan Ye
2011-05-27 6:32 ` [Ocfs2-devel] [PATCH 2/2] Ocfs2/move_extents: Validate moving goal after the adjustment Tristan Ye
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=4DF42CEF.6020704@oracle.com \
--to=tristan.ye@oracle.com \
--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 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.