From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Size limitation for NcFsd drive?
Date: Fri, 29 Jul 2016 19:32:00 -0000 [thread overview]
Message-ID: <20160729143815.GE5963@calimero.vinschen.de> (raw)
In-Reply-To: <20160729141831.GA9364@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
On Jul 29 16:18, Corinna Vinschen wrote:
> In the first place it would be prudent to find out why the
> FileAllInformation info class fails on this drive. And in the second
> place it would be important to find out how to fix this. Potential
> checks:
>
> - Buffer alignment of the FILE_ALL_INFORMATION member in class
> path_conv_handle.
>
> - Buffer size of the FILE_ALL_INFORMATION member. For instance,
> does it work if the buffer is 1 byte bigger? Or perhaps if
> the buffer is NAME_MAX bigger?
- There's also a chance (albeit minor) that the FileAllInformation call
actually worked and the weird status code is just wrong. After all,
returning from this call with STATUS_BUFFER_OVERFLOW is valid, too,
so I'd check for this as well here.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-29 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 10:35 Franz Sirl
2016-07-28 16:36 ` Franz Sirl
2016-07-28 20:20 ` Corinna Vinschen
2016-07-29 14:26 ` Franz Sirl
2016-07-29 14:38 ` Corinna Vinschen
2016-07-29 16:00 ` Corinna Vinschen
2016-07-29 19:32 ` Corinna Vinschen [this message]
2016-08-02 14:26 ` Franz Sirl
2016-08-02 14:59 ` Corinna Vinschen
2016-08-04 12:36 ` Corinna Vinschen
2016-08-04 23:01 ` Franz Sirl
2016-08-05 10:53 ` Corinna Vinschen
2016-08-05 15:15 ` Franz Sirl
2016-08-05 15:21 ` Corinna Vinschen
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=20160729143815.GE5963@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).