From: Leah Rumancik <leah.rumancik@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, linux-xfs@vger.kernel.org,
chandan.babu@oracle.com, fred@cloudflare.com,
Dave Chinner <dchinner@redhat.com>,
Christoph Hellwig <hch@lst.de>,
"Darrick J . Wong" <djwong@kernel.org>
Subject: Re: [PATCH 6.1 01/24] xfs: write page faults in iomap are not buffered writes
Date: Mon, 6 May 2024 10:52:16 -0700 [thread overview]
Message-ID: <CACzhbgSNe5amnMPEz8AYu3Z=qZRyKLFDvOtA_9wFGW9Bh-jg+g@mail.gmail.com> (raw)
In-Reply-To: <CAOQ4uxhcFSPhnAfDxm-GQ8i-NmDonzLAq5npMh84EZxxr=qhjQ@mail.gmail.com>
Ah my bad, I'll make sure to explicitly mention its been ACK'd by
linux-xfs in the future.
Will send out a MAINTAINERS file patch as well.
Thanks,
Leah
On Sat, May 4, 2024 at 11:17 AM Amir Goldstein <amir73il@gmail.com> wrote:
>
> On Sat, May 4, 2024 at 12:16 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, May 01, 2024 at 11:40:49AM -0700, Leah Rumancik wrote:
> > > From: Dave Chinner <dchinner@redhat.com>
> > >
> > > [ Upstream commit 118e021b4b66f758f8e8f21dc0e5e0a4c721e69e ]
> >
> > Is this series "ok" to take? I've lost track of who we should be taking
> > xfs stable patches from these days...
> >
>
> Yes, because it was posted to xfs list and acked by Darrick:
> https://lore.kernel.org/linux-xfs/20240426231407.GQ360919@frogsfrogsfrogs/
>
> I guess the cover letter that is missing from this series would have
> mentioned that.
>
> Anyway, how can you keep track, that is a good question.
>
> There are some tell signs that you could rely on in the future:
> 1. All the stable xfs patch series in the recent era, as this one, have been
> Acked-by: Darrick J. Wong <djwong@kernel.org>
> 2. The majority of stable xfs patches in the recent era,
> have been posted and Signed-off-by the xfs maintainer that is
> listed in MAINTAINER in the respective LTS kernel:
>
> $ git diff stable/linux-5.10.y -- MAINTAINERS |grep -w XFS -A 2
> XFS FILESYSTEM
> -M: Amir Goldstein <amir73il@gmail.com>
> -M: Darrick J. Wong <djwong@kernel.org>
> amir@amir-ThinkPad-T480:~/src/linux$ git diff stable/linux-5.15.y --
> MAINTAINERS |grep -w XFS -A 2
> XFS FILESYSTEM
> -C: irc://irc.oftc.net/xfs
> -M: Leah Rumancik <leah.rumancik@gmail.com>
> amir@amir-ThinkPad-T480:~/src/linux$ git diff stable/linux-6.1.y --
> MAINTAINERS |grep -w XFS -A 2
> XFS FILESYSTEM
> -C: irc://irc.oftc.net/xfs
> -M: Darrick J. Wong <djwong@kernel.org>
> amir@amir-ThinkPad-T480:~/src/linux$ git diff stable/linux-6.6.y --
> MAINTAINERS |grep -w XFS -A 2
> XFS FILESYSTEM
> -M: Catherine Hoang <catherine.hoang@oracle.com>
> M: Chandan Babu R <chandan.babu@oracle.com>
>
> Leah,
>
> I guess a patch to MAINTAINERS for 6.1.y is in order...
>
> Thanks,
> Amir.
next prev parent reply other threads:[~2024-05-06 17:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 18:40 [PATCH 6.1 01/24] xfs: write page faults in iomap are not buffered writes Leah Rumancik
2024-05-01 18:40 ` [PATCH 6.1 02/24] xfs: punching delalloc extents on write failure is racy Leah Rumancik
2024-05-01 18:40 ` [PATCH 6.1 03/24] xfs: use byte ranges for write cleanup ranges Leah Rumancik
2024-05-01 18:40 ` [PATCH 6.1 04/24] xfs,iomap: move delalloc punching to iomap Leah Rumancik
2024-05-01 18:40 ` [PATCH 6.1 05/24] iomap: buffered write failure should not truncate the page cache Leah Rumancik
2024-05-01 18:40 ` [PATCH 6.1 06/24] xfs: xfs_bmap_punch_delalloc_range() should take a byte range Leah Rumancik
2024-05-01 18:40 ` [PATCH 6.1 07/24] iomap: write iomap validity checks Leah Rumancik
2024-05-01 18:40 ` [PATCH 6.1 08/24] xfs: use iomap_valid method to detect stale cached iomaps Leah Rumancik
2024-05-01 18:40 ` [PATCH 6.1 09/24] xfs: drop write error injection is unfixable, remove it Leah Rumancik
2024-05-01 18:40 ` [PATCH 6.1 10/24] xfs: fix off-by-one-block in xfs_discard_folio() Leah Rumancik
2024-05-01 18:40 ` [PATCH 6.1 11/24] xfs: fix incorrect error-out in xfs_remove Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 12/24] xfs: fix sb write verify for lazysbcount Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 13/24] xfs: fix incorrect i_nlink caused by inode racing Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 14/24] xfs: invalidate block device page cache during unmount Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 15/24] xfs: attach dquots to inode before reading data/cow fork mappings Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 16/24] xfs: wait iclog complete before tearing down AIL Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 17/24] xfs: fix super block buf log item UAF during force shutdown Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 18/24] xfs: hoist refcount record merge predicates Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 19/24] xfs: estimate post-merge refcounts correctly Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 20/24] xfs: invalidate xfs_bufs when allocating cow extents Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 21/24] xfs: allow inode inactivation during a ro mount log recovery Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 22/24] xfs: fix log recovery when unknown rocompat bits are set Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 23/24] xfs: get root inode correctly at bulkstat Leah Rumancik
2024-05-01 18:41 ` [PATCH 6.1 24/24] xfs: short circuit xfs_growfs_data_private() if delta is zero Leah Rumancik
2024-05-04 9:16 ` [PATCH 6.1 01/24] xfs: write page faults in iomap are not buffered writes Greg KH
2024-05-04 18:17 ` Amir Goldstein
2024-05-06 17:52 ` Leah Rumancik [this message]
2024-05-22 14:11 ` Greg KH
2024-05-22 21:55 ` Leah Rumancik
2024-05-23 7:08 ` Greg KH
2024-05-23 11:06 ` Greg KH
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='CACzhbgSNe5amnMPEz8AYu3Z=qZRyKLFDvOtA_9wFGW9Bh-jg+g@mail.gmail.com' \
--to=leah.rumancik@gmail.com \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=fred@cloudflare.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.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 read-only IMAP folder(s) and NNTP newsgroup(s).