public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Sheng Yong <shengyong1@huawei.com>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org
Subject: Re: [PATCH] xfs: remote attribute overwrite causes transaction overrun
Date: Wed, 29 Apr 2015 17:43:16 +1000	[thread overview]
Message-ID: <20150429074316.GV15810@dastard> (raw)
In-Reply-To: <1430272525-60351-2-git-send-email-shengyong1@huawei.com>

On Wed, Apr 29, 2015 at 01:55:25AM +0000, Sheng Yong wrote:
> commit 8275cdd0e7ac550dcce2b3ef6d2fb3b808c1ae59 upstream.
> 
> Commit e461fcb ("xfs: remote attribute lookups require the value
> length") passes the remote attribute length in the xfs_da_args
> structure on lookup so that CRC calculations and validity checking
> can be performed correctly by related code. This, unfortunately has
> the side effect of changing the args->valuelen parameter in cases
> where it shouldn't.
> 
> That is, when we replace a remote attribute, the incoming
> replacement stores the value and length in args->value and
> args->valuelen, but then the lookup which finds the existing remote
> attribute overwrites args->valuelen with the length of the remote
> attribute being replaced. Hence when we go to create the new
> attribute, we create it of the size of the existing remote
> attribute, not the size it is supposed to be. When the new attribute
> is much smaller than the old attribute, this results in a
> transaction overrun and an ASSERT() failure on a debug kernel:
> 
> XFS: Assertion failed: tp->t_blk_res_used <= tp->t_blk_res, file: fs/xfs/xfs_trans.c, line: 331
> 
> Fix this by keeping the remote attribute value length separate to
> the attribute value length in the xfs_da_args structure. The enables
> us to pass the length of the remote attribute to be removed without
> overwriting the new attribute's length.
> 
> Also, ensure that when we save remote block contexts for a later
> rename we zero the original state variables so that we don't confuse
> the state of the attribute to be removes with the state of the new
> attribute that we just added. [Spotted by Brain Foster.]
> 
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> Reviewed-by: Brian Foster <bfoster@redhat.com>
> Signed-off-by: Dave Chinner <david@fromorbit.com>
> [shengyong: backport to 3.10
>  - Addresse: CVE-2015-0274
>  - adjust context
>  - fs/xfs/xfs_attr_list.c comes from fs/xfs/xfs_attr.c and
>    fs/xfs/xfs_attr_leaf.c in linux 3.12]
> Signed-off-by: Sheng Yong <shengyong1@huawei.com>

You are backporting to 3.10?

Check when Commit e461fcb ("xfs: remote attribute lookups require
the value length") was introduced:

$ git describe --contains e461fcb
for-linus-v3.11-rc1~53
$

Seems to me like the problem the CVE describes didn't exist in 3.10...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2015-04-29  7:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29  1:55 [RFC PATCH] xfs: remote attribute overwrite causes transaction overrun Sheng Yong
2015-04-29  1:55 ` [PATCH] " Sheng Yong
2015-04-29  7:43   ` Dave Chinner [this message]
2015-04-29  9:05     ` Sheng Yong
2015-05-02 18:36       ` Greg KH
2015-05-04  1:45         ` Sheng Yong
2015-05-04  3:34           ` Dave Chinner

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=20150429074316.GV15810@dastard \
    --to=david@fromorbit.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=shengyong1@huawei.com \
    --cc=stable@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