public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: rm -rf cannot delete the upmost directory level anymore on a Novell share
Date: Mon, 24 Oct 2011 10:32:00 -0000	[thread overview]
Message-ID: <20111024103136.GC14623@calimero.vinschen.de> (raw)
In-Reply-To: <4EA539E9.5080502@lauterbach.com>

On Oct 24 12:11, Franz Sirl wrote:
> Am 2011-10-21 17:35, schrieb Corinna Vinschen:
> >On Oct 21 16:58, Franz Sirl wrote:
> >>I will create a support case with Novell. To make my understanding
> >>clear, I think there are actually 2 problems here (Win32 calls for
> >>illustration, assuming the directory is already opened):
> >>
> >
> >   0. The directory has been opened with all sharing modes allowed "elsewhere".
> >
> >>1. CreateFile(FILE_READ_ATTRIBUTES | DELETE, FILE_SHARE_DELETE)
> >>should not succeed, but fail with STATUS_SHARING_VIOLATION
> >
> >I didn't see a full strace from W7.  Did you check that this doesn't
> >happen anyway?
> 
> strace attached. Succeeding here depends on the access modes of the
> open handle(s) or if the directory is not open at all.

That's why I added the step 0.  But if the file is open elsewhere,
this step should not succeed based on the access modes, but only
based on the sharing modes allowed by the other handle.

> Your changes work, I just tried the 20111023 snapshot. See the
> attached strace on Win7/64.

Thanks, it looks like expected now, given NcFsd's behaviour.  Note
that this can't be fixed on NWFS.  On NWFS, only the changes to
upstream coreutils as outlined in
http://cygwin.com/ml/cygwin/2011-10/msg00481.html will help.

> I also attached the simple testcase I'll submit to Novell. Please
> let me know if you think something is wrong with the testcase.

Looks good to me.  For completeness, maybe you should note that
delete-on-close works in this scenario, but it's desired that both
methods work, just as on NTFS, for instance.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-10-24 10:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 15:12 Franz Sirl
2011-10-19 15:46 ` Corinna Vinschen
2011-10-19 16:43   ` Franz Sirl
2011-10-20  9:21     ` Corinna Vinschen
2011-10-20  9:47       ` Corinna Vinschen
2011-10-20 14:59         ` Franz Sirl
2011-10-20 17:24           ` Corinna Vinschen
2011-10-20 11:51       ` Franz Sirl
2011-10-20 13:10         ` Corinna Vinschen
2011-10-20 13:57           ` Franz Sirl
2011-10-20 17:30             ` Corinna Vinschen
2011-10-21  9:11               ` Corinna Vinschen
2011-10-21 14:58                 ` Franz Sirl
2011-10-21 15:36                   ` Corinna Vinschen
2011-10-24 10:12                     ` Franz Sirl
2011-10-24 10:32                       ` Corinna Vinschen [this message]
2011-10-24 11:49                         ` Franz Sirl
2011-10-24 12:05                           ` Corinna Vinschen
2011-10-24 17:53                           ` Eric Blake

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=20111024103136.GC14623@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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).