Hi Viacheslav,

I'm submitting three nilfs2 fixes as a patch series (rather than a
pull request as previously mentioned), so please queue them in your
tree.

Two of the three involve kernel-doc issues in uapi header files. These
are suitable for the next cycle.

The remaining one, which I'm sure you've seen, fixes an issue recently
reported by syzbot involving the FITRIM ioctl, and is a slightly
higher priority.

If possible, I'd like you to submit this as a bugfix patch without
waiting for the next release cycle, but if you're limiting your pull
requests to merge windows, feel free to submit it together with ones
for v6.20-rc1 at your convenience.


Thanks,
Ryusuke Konishi


Edward Adam Davis (1):
  nilfs2: Fix potential block overflow that cause system hang

Randy Dunlap (1):
  nilfs2: convert nilfs_super_block to kernel-doc

Ryusuke Konishi (1):
  nilfs2: fix missing struct keywords in nilfs2_api.h kernel-doc

 fs/nilfs2/sufile.c                 |   4 +
 include/uapi/linux/nilfs2_api.h    |   4 +-
 include/uapi/linux/nilfs2_ondisk.h | 163 +++++++++++++++++------------
 3 files changed, 103 insertions(+), 68 deletions(-)

-- 
2.43.0

Hi Ryusuke,

On Sat, 2025-12-20 at 03:04 +0900, Ryusuke Konishi wrote:
> Hi Viacheslav,
> 
> I'm submitting three nilfs2 fixes as a patch series (rather than a
> pull request as previously mentioned), so please queue them in your
> tree.
> 
> Two of the three involve kernel-doc issues in uapi header files.
> These
> are suitable for the next cycle.
> 
> The remaining one, which I'm sure you've seen, fixes an issue
> recently
> reported by syzbot involving the FITRIM ioctl, and is a slightly
> higher priority.
> 
> If possible, I'd like you to submit this as a bugfix patch without
> waiting for the next release cycle, but if you're limiting your pull
> requests to merge windows, feel free to submit it together with ones
> for v6.20-rc1 at your convenience.
> 

I've applied patches on the tree. Sorry, end of the year as usually
"unexpectedly" busy. :) I think that Christmas and New Year time is not
the best time to send pull request. Also, I am finishing of creating
the tickets for xfstests issues. So, I hope I could start to analyze
the issues soon. And, probably, we could have more fixes for the next
merge window.

Thanks,
Slava.

On Tue, Dec 23, 2025 at 9:16 AM Viacheslav Dubeyko wrote:
>
> Hi Ryusuke,
>
> On Sat, 2025-12-20 at 03:04 +0900, Ryusuke Konishi wrote:
> > Hi Viacheslav,
> >
> > I'm submitting three nilfs2 fixes as a patch series (rather than a
> > pull request as previously mentioned), so please queue them in your
> > tree.
> >
> > Two of the three involve kernel-doc issues in uapi header files.
> > These
> > are suitable for the next cycle.
> >
> > The remaining one, which I'm sure you've seen, fixes an issue
> > recently
> > reported by syzbot involving the FITRIM ioctl, and is a slightly
> > higher priority.
> >
> > If possible, I'd like you to submit this as a bugfix patch without
> > waiting for the next release cycle, but if you're limiting your pull
> > requests to merge windows, feel free to submit it together with ones
> > for v6.20-rc1 at your convenience.
> >
>
> I've applied patches on the tree. Sorry, end of the year as usually
> "unexpectedly" busy. :) I think that Christmas and New Year time is not
> the best time to send pull request. Also, I am finishing of creating
> the tickets for xfstests issues. So, I hope I could start to analyze
> the issues soon. And, probably, we could have more fixes for the next
> merge window.
>
> Thanks,
> Slava.

Yes, that's fine.
It's the end of the year, so please proceed at your convenience.
If nothing else happens, I'd like to address some of the necessary
improvements to the NILFS utilities build and focus on  issues around
rename operations.

Thanks,
Ryusuke Konishi