linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to 837514f7a4ca
Date: Mon, 12 Nov 2018 02:21:10 +0800	[thread overview]
Message-ID: <20181111182110.GK2279@dhcp-12-117.nay.redhat.com> (raw)
In-Reply-To: <20181106162413.GV4135@magnolia>

On Tue, Nov 06, 2018 at 08:24:13AM -0800, Darrick J. Wong wrote:
> Hi folks,
> 
> The for-next branch of the xfs-linux repository at:
> 
> 	git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
> 
> has just been updated.
> 
> Patches often get missed, so please check if your outstanding patches
> were in this update. If they have not been in this update, please
> resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
> the next update.  As of this message, I am taking the reins back from
> Dave.
> 
> The new head of the for-next branch is commit:
> 
> 837514f7a4ca xfs: fix overflow in xfs_attr3_leaf_verify

JFYI:

I just done some basic XFS regression testing once on this kernel
(git HEAD is at 837514f7a xfs: fix overflow in xfs_attr3_leaf_verify), nothing
weird can be found. Test cases include (on x86_64 and ppc64le):
---
xfstests auto group test on XFS with 4k+reflink, 2k+reflink+rmapbt, 1k+finobt, 512b.
LTP (fs related test) on XFS with 4k+reflink and 2k+reflink+rmapbt, 64k+reflink.
pjd-fstest on XFS with 4k+reflink.
fsx 3 days stress tests.
fsstress stress test.
Lustre race test.
All mkfs.xfs options test.
Kernel build stress test.
And some other regression tests.
---

Maybe import more tests in next xfs-4.20-fixes-2 Feel free to tell me, if you
have any suggestions.

Thanks,
Zorro

> 
> New Commits:
> 
> Christophe JAILLET (1):
>       [132bf6723749] xfs: Fix error code in 'xfs_ioc_getbmap()'
> 
> Darrick J. Wong (1):
>       [bdec055bb9f2] xfs: print buffer offsets when dumping corrupt buffers
> 
> Dave Chinner (1):
>       [837514f7a4ca] xfs: fix overflow in xfs_attr3_leaf_verify
> 
> 
> Code Diffstat:
> 
>  fs/xfs/libxfs/xfs_attr_leaf.c | 11 +++++++++--
>  fs/xfs/xfs_ioctl.c            |  2 +-
>  fs/xfs/xfs_message.c          |  2 +-
>  3 files changed, 11 insertions(+), 4 deletions(-)

      reply	other threads:[~2018-11-12  4:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 16:24 [ANNOUNCE] xfs-linux: for-next updated to 837514f7a4ca Darrick J. Wong
2018-11-11 18:21 ` Zorro Lang [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=20181111182110.GK2279@dhcp-12-117.nay.redhat.com \
    --to=zlang@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).