* [ANNOUNCE] xfs-linux: for-next updated to f259584cb40c
@ 2025-06-27 12:55 Carlos Maiolino
2025-06-27 12:58 ` Christoph Hellwig
0 siblings, 1 reply; 4+ messages in thread
From: Carlos Maiolino @ 2025-06-27 12:55 UTC (permalink / raw)
To: linux-xfs
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.
The new head of the for-next branch is commit:
f259584cb40c Merge branch 'xfs-6.17-merge' into for-next
21 new commits:
Carlos Maiolino (1):
[f259584cb40c] Merge branch 'xfs-6.17-merge' into for-next
Dave Chinner (7):
[09234a632be4] xfs: xfs_ifree_cluster vs xfs_iflush_shutdown_abort deadlock
[db6a2274162d] xfs: catch stale AGF/AGF metadata
[d62016b1a2df] xfs: avoid dquot buffer pin deadlock
[fc48627b9c22] xfs: add tracepoints for stale pinned inode state debug
[d2fe5c4c8d25] xfs: rearrange code in xfs_buf_item.c
[816c330b605c] xfs: factor out stale buffer item completion
[7b5f775be14a] xfs: fix unmount hang with unflushable inodes stuck in the AIL
Steven Rostedt (13):
[c0ed3d33cea1] xfs: remove unused trace event xfs_attr_remove_iter_return
[4b1b26f4fded] xfs: remove unused event xlog_iclog_want_sync
[159e1d454d6d] xfs: remove unused event xfs_ioctl_clone
[1905a13e44d9] xfs: remove unused xfs_reflink_compare_extents events
[3a81e9a6d78d] xfs: remove unused trace event xfs_attr_rmtval_set
[3f9b08fedc35] xfs: remove unused xfs_attr events
[9e6d839093cb] xfs: remove unused event xfs_attr_node_removename
[6f4d1600b0ba] xfs: remove unused event xfs_alloc_near_error
[7352e1419858] xfs: remove unused event xfs_alloc_near_nominleft
[4b7169eb63ab] xfs: remove unused event xfs_pagecache_inval
[5a3b36801c7d] xfs: remove usused xfs_end_io_direct events
[8f648ef996bf] xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure
[9075fe1225ad] xfs: change xfs_xattr_class from a TRACE_EVENT() to DECLARE_EVENT_CLASS()
Code Diffstat:
fs/xfs/libxfs/xfs_alloc.c | 41 +++++--
fs/xfs/libxfs/xfs_ialloc.c | 31 ++++-
fs/xfs/scrub/trace.h | 2 +-
fs/xfs/xfs_buf.c | 38 ------
fs/xfs/xfs_buf.h | 1 -
fs/xfs/xfs_buf_item.c | 295 +++++++++++++++++++++++++++------------------
fs/xfs/xfs_buf_item.h | 3 +-
fs/xfs/xfs_dquot.c | 4 +-
fs/xfs/xfs_icache.c | 8 ++
fs/xfs/xfs_inode.c | 2 +-
fs/xfs/xfs_inode_item.c | 5 +-
fs/xfs/xfs_log_cil.c | 4 +-
fs/xfs/xfs_qm.c | 86 +++----------
fs/xfs/xfs_trace.h | 78 ++----------
fs/xfs/xfs_trans.c | 4 +-
15 files changed, 290 insertions(+), 312 deletions(-)
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ANNOUNCE] xfs-linux: for-next updated to f259584cb40c
2025-06-27 12:55 [ANNOUNCE] xfs-linux: for-next updated to f259584cb40c Carlos Maiolino
@ 2025-06-27 12:58 ` Christoph Hellwig
2025-06-27 13:13 ` Carlos Maiolino
0 siblings, 1 reply; 4+ messages in thread
From: Christoph Hellwig @ 2025-06-27 12:58 UTC (permalink / raw)
To: Carlos Maiolino; +Cc: linux-xfs
Btw, I assumed you'd send my fixes from three weeks ago to Linus for
6.16. Do you plan to wait for 6.17 or did you just not get around
sending a pull request? At least for the zone allocator shutdown
check that would be annoying as it causes hangs during testing.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ANNOUNCE] xfs-linux: for-next updated to f259584cb40c
2025-06-27 12:58 ` Christoph Hellwig
@ 2025-06-27 13:13 ` Carlos Maiolino
2025-06-27 13:21 ` Christoph Hellwig
0 siblings, 1 reply; 4+ messages in thread
From: Carlos Maiolino @ 2025-06-27 13:13 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: linux-xfs
On Fri, Jun 27, 2025 at 05:58:08AM -0700, Christoph Hellwig wrote:
> Btw, I assumed you'd send my fixes from three weeks ago to Linus for
> 6.16. Do you plan to wait for 6.17 or did you just not get around
> sending a pull request? At least for the zone allocator shutdown
> check that would be annoying as it causes hangs during testing.
>
You meant the ones we already have in for-next? Or did I miss something
else?
I'll send them for 6.16, I was just really busy past couple weeks to
actually prepare a Pull request.
I'm planning to send everything we have now in for-next to Linus on next
week. I can send a pull tomorrow with things already staged for a few
days (i.e. without the patches from today) if you need it urgently, but
I'd rather wait to send it to -rc5 if that's ok with you.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ANNOUNCE] xfs-linux: for-next updated to f259584cb40c
2025-06-27 13:13 ` Carlos Maiolino
@ 2025-06-27 13:21 ` Christoph Hellwig
0 siblings, 0 replies; 4+ messages in thread
From: Christoph Hellwig @ 2025-06-27 13:21 UTC (permalink / raw)
To: Carlos Maiolino; +Cc: Christoph Hellwig, linux-xfs
On Fri, Jun 27, 2025 at 03:13:55PM +0200, Carlos Maiolino wrote:
> On Fri, Jun 27, 2025 at 05:58:08AM -0700, Christoph Hellwig wrote:
> > Btw, I assumed you'd send my fixes from three weeks ago to Linus for
> > 6.16. Do you plan to wait for 6.17 or did you just not get around
> > sending a pull request? At least for the zone allocator shutdown
> > check that would be annoying as it causes hangs during testing.
> >
>
> You meant the ones we already have in for-next?
Yes.
> I'll send them for 6.16,
Awesome, I kjust wanted to double check.
> I'm planning to send everything we have now in for-next to Linus on next
> week. I can send a pull tomorrow with things already staged for a few
> days (i.e. without the patches from today) if you need it urgently, but
> I'd rather wait to send it to -rc5 if that's ok with you.
In general I'd like to see them out rather sooner than later, but
if it's easier for your it can wait.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2025-06-27 13:21 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-27 12:55 [ANNOUNCE] xfs-linux: for-next updated to f259584cb40c Carlos Maiolino
2025-06-27 12:58 ` Christoph Hellwig
2025-06-27 13:13 ` Carlos Maiolino
2025-06-27 13:21 ` Christoph Hellwig
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).