On Sun, Mar 10, 2024 at 05:44:27PM -0400, Paul R. Tagliamonte wrote:

I sent a fix to upstream vim to handle a bug where vim would attempt
to allocate size_t max (for me, 0xFFFFFFFFFFFFFFFF aka
18446744073709551615 bytes) when the filesystem responded with an
error on listxattr other than not supported.

The upstream patch can be found at 14759ded57447345ba11c11a99fd84344797862c[1] - I've exported that patch
for inclusion into sid.

Thanks! I'll likely refresh against the ~latest upstream once things in
the time_t land settle down some, so this will get pulled in then.

Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Thanks, James!

I'm deeply grateful for your work on vim, thank you so much for
maintaining it!

paultag


On Sun, Mar 10, 2024 at 8:17 PM James McCoy <jamessan@debian.org> wrote:

On Sun, Mar 10, 2024 at 05:44:27PM -0400, Paul R. Tagliamonte wrote:

I sent a fix to upstream vim to handle a bug where vim would attempt
to allocate size_t max (for me, 0xFFFFFFFFFFFFFFFF aka
18446744073709551615 bytes) when the filesystem responded with an
error on listxattr other than not supported.

The upstream patch can be found at 14759ded57447345ba11c11a99fd84344797862c[1] - I've exported that patch
for inclusion into sid.

Thanks! I'll likely refresh against the ~latest upstream once things in
the time_t land settle down some, so this will get pulled in then.

Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB

--
:wq

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)