lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKFNMo=9_KAfLLttaYUuD6d9nTmht+T8En15DwxL_6-uaeSb5Q@mail.gmail.com>
Date: Tue, 23 Dec 2025 12:32:58 +0900
From: Ryusuke Konishi <konishi.ryusuke@...il.com>
To: Viacheslav Dubeyko <slava@...eyko.com>
Cc: linux-nilfs <linux-nilfs@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] nilfs2 fixes on v6.19-rc1

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ