public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Yoshinao Muramatsu <ysno@ac.auone-net.jp>
Cc: cygwin-patches@cygwin.com
Subject: Re: [PATCH 0/3] fix unlink/rename failure in hyper-v container(regenerate)
Date: Mon, 20 Mar 2023 13:12:15 +0100	[thread overview]
Message-ID: <ZBhNn6nItmyk2Ylk@calimero.vinschen.de> (raw)
In-Reply-To: <20230320115102.1692-1-ysno@ac.auone-net.jp>

Hi Yoshinao,

I just pushed a patch to fs_info::update to take the filesystem
flags introduced starting with Windows 7 into account:

https://sourceware.org/cgit/newlib-cygwin/commit/?id=fcccdc4021ff

AFAICS, this patch should already fix the problem.

It's not the last state, though, because a few more tweak are necessary:

- The filesystem shows up as "cifs" rather than "ntfs" in mount.
- Creating case sensitive directories won't work.
- an upper/lowercase problem in user extended attributes.
- unlinking files-in-use is broken yet.

I intend to fix those in a followup patch.

The next cygwin test release 3.5.0-0.249.g59241913330c will contain the
above patch.  Before we go ahead and apply your patch, can you test if
this already works as desired?  I'd like to get this working and then we
add your workaround, in case we encounter this problem in another
scenario, too.


Thanks,
Corinna



On Mar 20 20:50, Yoshinao Muramatsu wrote:
> From: Yoshinao <ysno@ac.auone-net.jp>
> 
> use real name and add `Signed-Off-By:' field, as suggested by Corinna.
> code is untouched.
> 
> Yoshinao Muramatsu (3):
>   fix unlink in container
>   fix rename in container
>   log disabling posix semantics
> 
>  winsup/cygwin/syscalls.cc | 23 +++++++++++++++++++++--
>  1 file changed, 21 insertions(+), 2 deletions(-)
> 
> -- 
> 2.37.3.windows.1

      parent reply	other threads:[~2023-03-20 12:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 14:43 [PATCH 0/3] fix unlink/rename failure in hyper-v container YO4
2023-03-17 14:43 ` [PATCH 1/3] fix unlink in container YO4
2023-03-17 14:43 ` [PATCH 2/3] fix rename " YO4
2023-03-17 14:43 ` [PATCH 3/3] log disabling posix semantics YO4
2023-03-17 19:15 ` [PATCH 0/3] fix unlink/rename failure in hyper-v container Corinna Vinschen
2023-03-18  5:29   ` Yoshinao Muramatsu
2023-03-18 10:01     ` Corinna Vinschen
2023-03-20 13:06       ` Yoshinao Muramatsu
2023-03-20 14:51         ` Corinna Vinschen
2023-03-20 14:54           ` Corinna Vinschen
2023-03-20 20:37           ` Corinna Vinschen
2023-03-21 15:32             ` Yoshinao Muramatsu
2023-03-21 17:58               ` Corinna Vinschen
2023-03-23 16:40                 ` Yoshinao Muramatsu
2023-03-24 11:54                   ` Corinna Vinschen
2023-03-24 13:20                     ` Jon Turney
2023-03-24 13:22                       ` Corinna Vinschen
2023-03-24 14:20                         ` Jon Turney
2023-03-24 13:48                     ` Yoshinao Muramatsu
2023-03-20 11:50   ` [PATCH 0/3] fix unlink/rename failure in hyper-v container(regenerate) Yoshinao Muramatsu
2023-03-20 11:51     ` [PATCH 1/3] fix unlink in container Yoshinao Muramatsu
2023-03-20 11:51     ` [PATCH 2/3] fix rename " Yoshinao Muramatsu
2023-03-20 11:51     ` [PATCH 3/3] log disabling posix semantics Yoshinao Muramatsu
2023-03-20 12:12     ` Corinna Vinschen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZBhNn6nItmyk2Ylk@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-patches@cygwin.com \
    --cc=ysno@ac.auone-net.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).