stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: linux-xfs@vger.kernel.org, Alexander.Levin@microsoft.com,
	gregkh@linuxfoundation.org, stable@vger.kernel.org,
	amir73il@gmail.com
Subject: Re: [PATCH 0/6] xfs: stable fixes for v4.19.y - circa v4.19.60
Date: Sat, 24 Aug 2019 10:33:15 -0400	[thread overview]
Message-ID: <20190824143315.GK1581@sasha-vm> (raw)
In-Reply-To: <20190823154459.GU16384@42.do-not-panic.com>

On Fri, Aug 23, 2019 at 03:44:59PM +0000, Luis Chamberlain wrote:
>On Wed, Jul 24, 2019 at 06:34:45AM +0000, Luis Chamberlain wrote:
>> Sasha,
>>
>> you merged my last set of XFS fixes. I asked for one patch to not be
>> merged yet as one issue was not yet properly fixed. After some further
>> review I have identified commits which do fix the kernel crash reported
>> on kz#204223 [0] with generic/388, this patch set applies on top of the
>> last one I sent you.
>>
>> These commits do quite a bit of code refactoring, and the actual fix
>> lies hidden in the last commit by Darrick. Due to the amount of changes
>> trying to extract the fix is riskier than just carring the code
>> refactoring. If we're OK with the code refactor for stable, its my
>> recommendation we keep the changes to match more with upstream and
>> benefit from other fixes. The code refactoring was merged on v4.20 and
>> Darrick's fix is the only fix upstream since the code was merged.
>>
>> If others disagree with this approach please speak up.
>>
>> I've run a full set of fstests against the following sections 12 times and
>> have found no regressions against the baseline:
>>
>> xfs
>> xfs_logdev
>> xfs_nocrc_512
>> xfs_nocrc
>> xfs_realtimedev
>> xfs_reflink_1024
>> xfs_reflink_dev
>>
>> Review from others is appreciated.
>>
>> [0] https://bugzilla.kernel.org/show_bug.cgi?id=204223
>>
>> Allison Henderson (4):
>>   xfs: Move fs/xfs/xfs_attr.h to fs/xfs/libxfs/xfs_attr.h
>>   xfs: Add helper function xfs_attr_try_sf_addname
>>   xfs: Add attibute set and helper functions
>>   xfs: Add attibute remove and helper functions
>>
>> Brian Foster (1):
>>   xfs: don't trip over uninitialized buffer on extent read of corrupted
>>     inode
>>
>> Darrick J. Wong (1):
>>   xfs: always rejoin held resources during defer roll
>>
>>  fs/xfs/libxfs/xfs_attr.c       | 231 ++++++++++++++++++---------------
>>  fs/xfs/{ => libxfs}/xfs_attr.h |   2 +
>>  fs/xfs/libxfs/xfs_bmap.c       |  54 +++++---
>>  fs/xfs/libxfs/xfs_bmap.h       |   1 +
>>  fs/xfs/libxfs/xfs_defer.c      |  14 +-
>>  fs/xfs/xfs_dquot.c             |  17 +--
>>  6 files changed, 183 insertions(+), 136 deletions(-)
>>  rename fs/xfs/{ => libxfs}/xfs_attr.h (98%)
>
>*poke*

I was hoping for an ack from the xfs folks...

>BTW I'm off on vacation for a while after today.

I saw the ticket; have fun! :)

--
Thanks,
Sasha

  reply	other threads:[~2019-08-24 17:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24  6:34 [PATCH 0/6] xfs: stable fixes for v4.19.y - circa v4.19.60 Luis Chamberlain
2019-07-24  6:34 ` [PATCH 1/6] xfs: don't trip over uninitialized buffer on extent read of corrupted inode Luis Chamberlain
2019-07-24  6:34 ` [PATCH 2/6] xfs: Move fs/xfs/xfs_attr.h to fs/xfs/libxfs/xfs_attr.h Luis Chamberlain
2019-07-24  6:34 ` [PATCH 3/6] xfs: Add helper function xfs_attr_try_sf_addname Luis Chamberlain
2019-07-24  6:34 ` [PATCH 4/6] xfs: Add attibute set and helper functions Luis Chamberlain
2019-07-24  6:34 ` [PATCH 5/6] xfs: Add attibute remove " Luis Chamberlain
2019-07-24  6:34 ` [PATCH 6/6] xfs: always rejoin held resources during defer roll Luis Chamberlain
2019-08-23 15:44 ` [PATCH 0/6] xfs: stable fixes for v4.19.y - circa v4.19.60 Luis Chamberlain
2019-08-24 14:33   ` Sasha Levin [this message]
2019-08-26 18:19     ` Sasha Levin

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=20190824143315.GK1581@sasha-vm \
    --to=sashal@kernel.org \
    --cc=Alexander.Levin@microsoft.com \
    --cc=amir73il@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).