public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin] Cygwin: /proc/sys FS: don't export NFS and DFS as block devices Date: Tue, 1 Dec 2020 08:40:18 +0000 (GMT) [thread overview] Message-ID: <20201201084018.85D973857831@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=80e35a211f69f23fa57003a08d1758657364f00e commit 80e35a211f69f23fa57003a08d1758657364f00e Author: Corinna Vinschen <corinna@vinschen.de> Date: Tue Dec 1 09:37:07 2020 +0100 Cygwin: /proc/sys FS: don't export NFS and DFS as block devices Network filesystems are not block devices. Apparently this code hasn't been executed anyway, given how network filesystems are hidden behind \Device\Mup. Signed-off-by: Corinna Vinschen <corinna@vinschen.de> Diff: --- winsup/cygwin/fhandler_procsys.cc | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/winsup/cygwin/fhandler_procsys.cc b/winsup/cygwin/fhandler_procsys.cc index d2540d0a1..f8abbe7c0 100644 --- a/winsup/cygwin/fhandler_procsys.cc +++ b/winsup/cygwin/fhandler_procsys.cc @@ -175,13 +175,10 @@ fhandler_procsys::exists (struct stat *buf) badly written. */ if (NT_SUCCESS (status)) { - if (ffdi.DeviceType == FILE_DEVICE_NETWORK_FILE_SYSTEM) - file_type = virt_blk; - else if (ffdi.DeviceType == FILE_DEVICE_NAMED_PIPE) + if (ffdi.DeviceType == FILE_DEVICE_NAMED_PIPE) file_type = internal ? virt_blk : virt_pipe; else if (ffdi.DeviceType == FILE_DEVICE_DISK || ffdi.DeviceType == FILE_DEVICE_CD_ROM - || ffdi.DeviceType == FILE_DEVICE_DFS || ffdi.DeviceType == FILE_DEVICE_VIRTUAL_DISK) { /* Check for file attributes. If we get them, we peeked
reply other threads:[~2020-12-01 8:40 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201201084018.85D973857831@sourceware.org \ --to=corinna@sourceware.org \ --cc=cygwin-cvs@sourceware.org \ /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: linkBe 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).