summaryrefslogtreecommitdiffstats
path: root/winsup
Commit message (Collapse)AuthorAgeFilesLines
* Cygwin: remove path_conv::is_fs_device()Ken Brown2019-07-221-2/+2
| | | | It is used only once.
* Cygwin: remove path_conv::is_auto_device()Ken Brown2019-07-222-2/+1
| | | | | | | It is used only once, and the name is supposed to suggest "device that is not based on the filesystem". This intended meaning is clearer if we just replace is_auto_device() by its definition at the place where it's used.
* Cygwin: fhandler_*: remove isdevice() and is_auto_device()Ken Brown2019-07-222-4/+1
| | | | | | isdevice() is used only in the definition of is_auto_device(). And the latter is used only once, in a context where isdevice() always returns true.
* Cygwin: unbreak the build with GCC 7Ken Brown2019-07-192-4/+15
| | | | | | The recent port to GCC 8 used the 'nonstring' attribute, which is unknown to GCC 7. Define and use an 'ATTRIBUTE_NONSTRING' macro instead.
* Cygwin: fix GCC 8.3 'local external declaration' errorsKen Brown2019-07-171-3/+2
| | | | Move external declarations out of function definition.
* Cygwin: fix GCC 8.3 'asm volatile' errorsKen Brown2019-07-171-2/+2
| | | | | | Remove the volatile qualifier, which is no longer allowed outside of the function body. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89585 for discussion.
* Cygwin: suppress GCC 8.3 errors with -Warray-boundsKen Brown2019-07-161-0/+2
|
* Cygwin: avoid GCC 8.3 errors with -Werror=stringop-truncationKen Brown2019-07-163-5/+5
|
* Cygwin: avoid GCC 8.3 errors with -Werror=class-memaccessKen Brown2019-07-164-6/+6
|
* Cygwin: sigpending: don't report pending signals for other threadsCorinna Vinschen2019-07-122-2/+10
| | | | | | | | The sigpending mechanism failed to check if the pending signal was a process-wide signal, or a signal for the curent thread. Fix that by adding a matching conditional to wait_sig's __SIGPENDING code. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
* Cygwin: return full sigset_t from sig_sendCorinna Vinschen2019-07-125-12/+12
| | | | | | | | | | | | | | | So far sig_send's return type is int. The problem with this is that sig_send returns a sigset_t on __SIGPENDING, and sigset_t is defined as long type. So the function only returns the lower 32 bit of sigset_t, which is fine on 32 bit, but casts away the pending RT signals on 64 bit. Fix this by changing the return type of sig_send to sigset_t, so as not to narrow down the sigset when returning from handling __SIGPENDING. Make sure to cast correctly in all invocations of sig_send. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
* Cygwin: Fix return value of sched_getaffinityMark Geisert2019-06-284-11/+31
| | | | | | Have sched_getaffinity() interface like glibc's, and provide an undocumented internal interface __sched_getaffinity_sys() like the Linux kernel's sched_getaffinity() for benefit of taskset(1).
* sched: Move Cygwin cpuset definitions into Cygwin-specific headerCorinna Vinschen2019-06-272-2/+28
| | | | | | This avoids build breakage on RTEMS. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
* Cygwin: honor the O_PATH flag when opening a FIFOKen Brown2019-06-271-1/+10
| | | | | Previously fhandler_fifo::open would treat the FIFO as a reader and would block, waiting for a writer.
* Cygwin: Build cygwin-console-helper with correct compilerMark Geisert2019-06-271-1/+1
|
* Cygwin: Use correct string conversionMark Geisert2019-06-271-2/+2
| | | | | Correct the string conversion calls so both argv elements get converted at full precision.
* Cygwin: FIFO: fix a thinko in raw_writeKen Brown2019-06-251-1/+0
| | | | Remove a line that has no effect.
* Tweak release messageKen Brown2019-06-251-1/+1
|
* Cygwin: timerfd: avoid a deadlockKen Brown2019-06-253-1/+28
| | | | | | | | | Add a function timerfd_tracker::enter_critical_section_cancelable, which is like enter_critical_section but honors a cancel event. Call this when a timer expires while the timerfd thread is in its inner loop. This avoids a deadlock if timerfd_tracker::dtor has entered its critical section and is trying to cancel the thread. See https://cygwin.com/ml/cygwin/2019-06/msg00096.html.
* Cygwin: Implement sched_[gs]etaffinity()Mark Geisert2019-06-2410-5/+366
| | | | | | | | | This patch set implements the Linux syscalls sched_getaffinity, sched_setaffinity, pthread_getaffinity_np, and pthread_setaffinity_np. Linux has a straightforward view of the cpu sets used in affinity masks. They are simply long (1024-bit) bit masks. This code emulates that view while internally dealing with Windows' distribution of available CPUs among processor groups.
* Cygwin: FIFO: minor cleanupKen Brown2019-06-232-7/+7
| | | | | | Don't use a label with the same name as a variable. Also fix indentation in fhandler.h.
* Cygwin: FIFO: slightly change the use of write_readyKen Brown2019-06-231-1/+2
| | | | | | | Make it a manual reset event. It's only used once to allow a reader to open, and there's no reason to ever reset it. Defensively set it when a client connection is recorded, even though it should be set by the writer that connected.
* Cygwin: FIFO: remove fifo_client_handler::connect_evtKen Brown2019-06-232-16/+15
| | | | | It's not needed. Instead just create and use an event in fhandler_fifo::listen_client_thread.
* Cygwin: FIFO: simplify raw_readKen Brown2019-06-231-19/+31
| | | | | | Call NtReadFile directly instead of calling fhandler_base::raw_read. In addition to being simpler, this gives us access to the return value from NtReadFile.
* Cygwin: FIFO: improve termination of the listen_client threadKen Brown2019-06-232-15/+55
| | | | | | | | | Add a method fifo_client_handler::pipe_state that queries Windows for the state of a pipe instance. Use this to help terminate the listen_client thread cleanly. If the last client handler is useless, delete it instead of declaring it invalid.
* Cygwin: FIFO: avoid deadlock when closingKen Brown2019-06-231-0/+3
| | | | | | | | fhandler_fifo::close could be called from a signal handler or another thread at a time when another function is holding the fifo_client lock. This could prevent the listen_client thread from acting on the thread termination event. Avoid a deadlock by calling fifo_client_unlock at the beginning of fhandler_fifo::close.
* Cygwin: FIFO: clean up locksKen Brown2019-06-231-8/+17
| | | | | Make sure to use the fifo_client lock when (and only when) it is needed.
* Cygwin: FIFO: add some error checkingKen Brown2019-06-232-4/+11
| | | | | Change the return type of fhandler_fifo::delete_client_handler from void to int so that we can report errors.
* Cygwin: FIFO: fix signal handling in raw_read and raw_writeKen Brown2019-06-231-31/+54
| | | | | | cygwait wasn't being called correctly. Also do some minor cleanup in raw_read and raw_write.
* Rename <xlocale.h> back to <sys/_locale.h>Corinna Vinschen2019-06-143-1/+10
| | | | | | | | | | | | | | | | | | | libX11 provides <X11/Xlocale.h>. The build of libX11 itself adds include/X11 to the compiler's include path. This results in a name collision with /usr/include/xlocale.h on case-insensitive filesystems. Commit 90e35b1eb3df renamed sys/_locale.h to xlocale.h in March 2017 under the assumption that we should provide the locale_t type in the same file as on Linux, FreeBSD, and Darwin. A few weeks later (June 2017), glibc removed the xlocale.h file in favor of bits/types/locale_t.h, which shouldn't be included directly anyway. For reference and the reasoning, see https://sourceware.org/git/?p=glibc.git;a=commit;h=f0be25b6336d Given the above, revert 90e35b1eb3df4070e68afc5e7060665214d586be and fix additional usage of xlocale.h.
* Revert "Cygwin: fork: Remember child not before success."Ken Brown2019-06-111-16/+15
| | | | | | | This reverts commit f03ea8e1c57bd5cea83f6cd47fa02870bdfeb1c5. That commit leads to fork problems if cygserver is running: https://cygwin.com/ml/cygwin-patches/2019-q2/msg00155.html
* Cygwin: map beyond EOF on 64 bit and WOW64 as wellCorinna Vinschen2019-06-051-11/+24
| | | | | | | | | | | | | | | | | | 32 bit Cygwin performs a POSIX-compatible mapping after EOF which is not supported in this form on Windows. The 64 bit Windows kernel never supported the AT_ROUND_TO_PAGE mapping flag, so we couldn't page-aligned map the space right after the file's EOF. So mapping beyond EOF was disabled in 64 bit Windows and WOW64. However, if mmap works, a matching munmap should work as well, *and* it should not accidentally unmap unrelated memory. Therefore we enable mapping beyond EOF on 64 bit as well. Since that mapping is always 64K aligned, the are between the last file page and the next 64K allocation boundary will be unallocated. There's no way around that. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
* mkdir: always check-for-existenceBen Wijen2019-06-051-1/+3
| | | | | | | | | When using NtCreateFile when creating a directory that already exists, it will correctly return 'STATUS_OBJECT_NAME_COLLISION'. However using this function to create a directory (and all its parents) a normal use would be to start with mkdir(‘/cygdrive/c’) which translates to ‘C:\’ for which it'll instead return ‘STATUS_ACCESS_DENIED’.
* cygcheck: expand common_apps listYaakov Selkowitz2019-06-041-1/+16
| | | | | | | | | An increasing number of tools are being included in Windows which have the same names as those included in Cygwin packages. Indicating which one is first in PATH can be helpful in diagnosing behavioural discrepencies between them. Also, fix the alphabetization of ssh.
* Cygwin: Allow accessing 48 bit address space in Windows 8.1 or laterCorinna Vinschen2019-06-044-5/+20
| | | | | | | | | | | | | | | | | 64 bit Windows started out with a 44 bit address space due to a restriction of the AMD64 CPUs at the time. Starting with Windows 8.1, these CPUs are not supported anymore and Windows switched to the full 48 bit address space supported by AMD64. Cygwin didn't follow suit yet so mmaps are still restricted to the lower 44 bit address space. Fix that by using a system-specific upper address for mmap allocations, 44 bit up to Windows 8, 48 bit starting with Windows 8.1. While at it, move the heap by another 8 Gigs to leave some space for a potential extension of DLL address space, and restrict the mmap lower address so the heap can grow to 32 Gigs before colliding with mmaps.
* Cygwin: fork: Remember child not before success.Michael Haubenwallner2019-06-031-15/+16
| | | | | | | | Do not remember the child before it was successfully initialized, or we would need more sophisticated cleanup on child initialization failure, like cleaning up the process table and suppressing SIGCHILD delivery with multiple threads ("waitproc") involved. Compared to that, the potential slowdown due to an extra yield () call should be negligible.
* Cygwin: fork: Always pause child after fixups.Michael Haubenwallner2019-06-031-10/+9
| | | | | | | | | | Pause the child process after performing fork fixups even if there were no dynamically loaded dlls with extra data/bss transfers to wait for. This allows the parent process to cancel the current fork call even if the child process was successfully initialized already. This is a preparation for when the parent does remember the child no earlier than after successful child initialization.
* Cygwin: dll_list: no recursive use of nt_max_path_bufMichael Haubenwallner2019-06-031-4/+9
| | | | | | Querying the ntlength and existence of the /var/run/cygfork directory in the very first Cygwin process should not use nt_max_path_buf, as that one is used by dll_list::alloc already.
* Cygwin: dll_list: stat_real_file_once with ntnameMichael Haubenwallner2019-06-032-34/+8
| | | | | | | | | | | | NtQueryVirtualMemory for MemorySectionName may return some old path even if the process was just started, for when some directory in between was renamed - maybe because the NT file cache is hot for the old path still. This was seen during gcc bootstrap, returning a MemorySectionName of ".../gcc/xgcc.exe" even if started as ".../prev-gcc/xgcc.exe", where the directory rename from "gcc" to "prev-gcc" was done the moment before. As we stat the module's real file right after loading now, there is no point in using NtQueryVirtualMemory with MemorySectionName any more, and we can use what GetModuleFileName returned instead.
* Add support for Hygon Dhyana processorJinke Fan2019-06-032-2/+4
| | | | | | | | | | | | | | | | | | | -Add vendor identification -Support in get_cpu_cache Background: Chengdu Haiguang IC Design Co., Ltd (Hygon) is a Joint Venture between AMD and Haiguang Information Technology Co.,Ltd., aims at providing high performance x86 processor for China server market. Its first generation processor codename is Dhyana, which originates from AMD technology and shares most of the architecture with AMD's family 17h, but with different CPU Vendor ID("HygonGenuine")/Family series number(Family 18h). Related Hygon kernel patch can be found on: http://lkml.kernel.org/r/5ce86123a7b9dad925ac583d88d2f921040e859b.1538583282.git.puwen@hygon.cn Signed-off-by: Jinke Fan <fanjinke@hygon.cn>
* Cygwin: FIFO: respect the O_CLOEXEC flagKen Brown2019-05-281-2/+3
| | | | | | Set the inheritance of the Windows pipe handles according to the O_CLOEXEC flag. Previously the pipe was always created and opened with OBJ_INHERIT.
* Cygwin: FIFO: Open only one handle to NPFSKen Brown2019-05-231-1/+1
| | | | | Make npfs_handle a static member function of fhandler_fifo, as in fhandler_socket_unix.
* Cygwin: FIFO: code simplifications.Ken Brown2019-05-091-11/+2
| | | | | | | | | | There's no longer a need to consider the connect_evt after fork/exec. After stopping the listen_client thread, all client handlers should be in the fc_connected or fc_invalid states, so their connect_evt members won't be used again. Also remove code in fhandler_fifo::dup that just repeats things already done in stop_listen_client.
* Cygwin: FIFO: make read_ready an auto-reset eventKen Brown2019-05-091-1/+1
| | | | | There's no point in allowing a writer to attempt to open until we've created a pipe instance.
* Cygwin: FIFO: improve the check for the listen_client threadKen Brown2019-05-092-2/+33
| | | | | | Add a method fhandler_fifo::check_listen_client_thread that checks whether the thread is running. Use it in raw_read instead of just testing the handle listen_client_thr.
* Cygwin: FIFO: set client handler flags more accuratelyKen Brown2019-05-091-1/+3
| | | | | Reflect the fact that client handlers are only used for reading and that, after connection, they are always nonblocking.
* Cygwin: FIFO: don't leave a pending listen requestKen Brown2019-05-092-53/+59
| | | | | | | | | | | | | On exit from the listen_client thread, make sure there's no pending FSCTL_PIPE_LISTEN request. Otherwise we might get a client connection after restarting the thread, and we won't have a handle for communicating with that client. Remove the retry loop in the case of STATUS_PIPE_LISTENING; that case shouldn't occur. Remove the now-unused fc_connecting value from fifo_client_connect_state.
* Cygwin: FIFO: add a HANDLE parameter to open_pipeKen Brown2019-05-092-9/+9
| | | | | | | | It's now up to the caller to pass a handle to open_pipe and, if desired, to call set_handle on return. This will be useful for a future commit, in which we will open a client connection without setting an io_handle.
* Cygwin: FIFO: re-implement duplexersKen Brown2019-05-092-34/+11
| | | | | | | | | | | | | | | | When opening a duplexer, open a client connection to the first client handler. Previously we gave the duplexer a bogus write handle, which was just a duplicate of the first client handler's handle. This meant that we had a pipe server with no clients connected, and all I/O attempts failed with STATUS_PIPE_LISTENING. Extend the last fcntl change to duplexers. Remove a now unused fifo_client_handler constructor, as well as the long unusued method fifo_client_handler::connect. Don't create the pipe in duplex mode; the server handle will only be used for reading.
* Cygwin: FIFO: add 'record_connection' methodKen Brown2019-05-092-9/+15
| | | | | Future commits will have to re-use the code for recording a client connection. For convenience, factor out this code into a new method.