Re: [PATCH 0/5] Fix AT_EMPTY_PATH handling

2023-07-26 Thread Corinna Vinschen
On Jul 26 11:10, Johannes Schindelin wrote: > Hi Corinna, > > I had a look over the patches and they all make sense. I also tested the > code to make sure that the `tar xf` regression I needed to be fixed is > also addressed by this patch series. > > As I don't really know the customs of the Cygw

Re: [PATCH 0/5] Fix AT_EMPTY_PATH handling

2023-07-26 Thread Johannes Schindelin
Hi Corinna, I had a look over the patches and they all make sense. I also tested the code to make sure that the `tar xf` regression I needed to be fixed is also addressed by this patch series. As I don't really know the customs of the Cygwin project, please feel free to add any Reviewed-by:, Acke

Re: [PATCH 0/5] Fix AT_EMPTY_PATH handling

2023-07-24 Thread Corinna Vinschen
Johannes? Ping? On Jul 12 14:07, Corinna Vinschen wrote: > From: Corinna Vinschen > > The GLIBC extension AT_EMPTY_PATH allows the functions fchownat > and fstatat to operate on dirfd alone, if the given pathname is an > empty string. This also allows to operate on any file type, not > only dir

[PATCH 0/5] Fix AT_EMPTY_PATH handling

2023-07-12 Thread Corinna Vinschen
From: Corinna Vinschen The GLIBC extension AT_EMPTY_PATH allows the functions fchownat and fstatat to operate on dirfd alone, if the given pathname is an empty string. This also allows to operate on any file type, not only directories. Commit fa84aa4dd2fb4 broke this. It only allows dirfd to b