search for: y2038

fup2p, this is offtopic for most lists Arnd Bergmann dixit: >It's hard because we don't even know what ioctls are affected at this point, >and I was hoping to get this part merged as a stepping stone in the process >of finding out. Oh okay. >e) ioctls that pass a time value as a 'long' or '__u32' instead of > 'time_t'. Fixing them requires

On Monday 18 May 2015 12:16:48 Thorsten Glaser wrote: > Arnd Bergmann dixit: > > >In the patch series I posted recently [1], I introduce new system calls to deal > >with modified data structures, but left the question open on how these should > >be best accessed from libc. The patches introduce a new __kernel_time64_t type > > Can we please have ioctls fixed for

Hi, On Linux, glibc is using a 32bit time_t for wtmp and similar structs even on a 64bit system: https://www.thkukuk.de/blog/Y2038_glibc_utmp_64bit/ https://www.thkukuk.de/blog/Y2038_glibc_wtmp_64bit/ Since the glibc developers stated that they don't plan to solve the problem in glibc, but think that this interfaces are legacy and should be removed from glibc (like musl libc, which does not have them), I implemented with...

Arnd Bergmann dixit: >In the patch series I posted recently [1], I introduce new system calls to deal >with modified data structures, but left the question open on how these should >be best accessed from libc. The patches introduce a new __kernel_time64_t type Can we please have ioctls fixed for mixed 32/64-bit systems such as MIPS (o32/n32/n64) and x86 (i386/x32/amd64) first, before

On 05/18/2015 02:53 AM, Arnd Bergmann wrote: > In the patch series I posted recently [1], I introduce new system calls to deal > with modified data structures, but left the question open on how these should > be best accessed from libc. The patches introduce a new __kernel_time64_t type > and based on that five new data structured: struct __kernel_timespec, > struct

..._KERNEL_TIME_BITS == 64: struct __old_kernel_timespec based on 32-bit __kernel_time_t struct timespec based on 64-bit __kernel_time64_t Would this work for everyone? Any alternative suggestions? Arnd [1] http://git.kernel.org/cgit/linux/kernel/git/arnd/playground.git/log/?h=y2038-syscalls https://lwn.net/Articles/643407/ diff --git a/include/uapi/asm-generic/bitsperlong.h b/include/uapi/asm-generic/bitsperlong.h index 23e6c416b85f..ecdaf4f77f35 100644 --- a/include/uapi/asm-generic/bitsperlong.h +++ b/include/uapi/asm-generic/bitsperlong.h @@ -12,4 +12,13 @@ #define _...

I would have never imagined that I''d be bitten by the Y2038 bug someday... but it just happened and, trust me, it hurts! I have to deal with a database containing datetime fields with dates up to 2050 and more. ActiveRecord raises an exception because Ruby''s Time class implementation. Besides running Ruby on a 64-bit platform, what can be done t...

...rsion: -current Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: Regression tests Assignee: unassigned-bugs at mindrot.org Reporter: alex.kanavin at gmail.com This allows testing Y2038 with system time set to after that (i.e.2040), so that actual Y2038 issues can be exposed, and not masked by key expiry time errors. Proposed patch: https://github.com/openssh/openssh-portable/pull/425 -- You are receiving this mail because: You are watching the assignee of the bug.

Hello, Testing systems for Y2038 safety is done by setting the clock to after 2038, and then running all available test suites. This however requires that actual Y2038 issues are not masked by key expiry errors (when tests hardcode expiry dates), and this is what happens in this particular test. I've submitted a fix here: htt...

...e streams. - Fix possible divide-by-zero. - Fix issues with seeking in the win32 backend. - Fix an issue where the seek algorithm could be confused by stream data changing between reads. - Clean up compiler and scan-build warnings. - Avoid use of the deprecated ftime() function which has Y2038 problems. - Remove undefined behaviour memcpy(NULL) in op_read_native(). - Visual Studio project files updated for libogg 1.3.4 library name change. - Various build systems updates. - Various integration and testing environment improvements. This release is backward-compatible with the previou...

...es other code cleanups and changes to improve code maintainability and analyzer output. For those building for 32-bit platforms, it also enables use of the "large file" APIs - though no file processed by this program should ever be anywhere near 2GB in size, it is a prerequisite for post-y2038 support. Since this release was generated using the new GNU autoconf 2.72, this also adds a --enable-year2038 configure flag which may allow it to work with files whose timestamps are later than January 19, 2038, but this has not been tested. Alan Coopersmith (25): Remove "All rights re...

Replace __time_t with time_t in my question. I've compiled function: std::string TimeValue::toString() const { // Alas, asctime is not re-entrant on Windows... //hb: __time64_t ourTime = this->toEpochTime(); time_t ourTime = this->toEpochTime(); //hb: char* buffer = ::asctime(::_localtime64(&ourTime)); char* buffer = ::asctime(::localtime(&ourTime)); std::string

Hi, I was thinking to ask the University computing Labs here to install R and I was told they need a statement that the software (R) is Y2K compliant. Which I cannot find in CRAN. (in addition to the licensing info). Is it a big issue to put such a statement in R? or this has legal implications that R do not want as a "free" software? If possible I would like to see the statement on

...======== Get locally logged on users from utmp ------------------------------------- The Workstation Service Remote Protocol [MS-WKST] calls NetWkstaGetInfo level 102 and NetWkstaEnumUsers level 0 and 1 return the list of locally logged on users. Samba was getting the list from utmp, which is not Y2038 safe. This feature has been completely removed and Samba will always return an empty list. smb.conf changes ================ ? Parameter Name????????????????????????? Description???? Default ? --------------????????????????????????? -----------???? ------- ? smb3 unix extensions??????????????...

...======== Get locally logged on users from utmp ------------------------------------- The Workstation Service Remote Protocol [MS-WKST] calls NetWkstaGetInfo level 102 and NetWkstaEnumUsers level 0 and 1 return the list of locally logged on users. Samba was getting the list from utmp, which is not Y2038 safe. This feature has been completely removed and Samba will always return an empty list. smb.conf changes ================ ? Parameter Name????????????????????????? Description???? Default ? --------------????????????????????????? -----------???? ------- ? smb3 unix extensions??????????????...

...======== Get locally logged on users from utmp ------------------------------------- The Workstation Service Remote Protocol [MS-WKST] calls NetWkstaGetInfo level 102 and NetWkstaEnumUsers level 0 and 1 return the list of locally logged on users. Samba was getting the list from utmp, which is not Y2038 safe. This feature has been completely removed and Samba will always return an empty list. smb.conf changes ================ ? Parameter Name????????????????????????? Description???? Default ? --------------????????????????????????? -----------???? ------- ? smb3 unix extensions??????????????...

...======== Get locally logged on users from utmp ------------------------------------- The Workstation Service Remote Protocol [MS-WKST] calls NetWkstaGetInfo level 102 and NetWkstaEnumUsers level 0 and 1 return the list of locally logged on users. Samba was getting the list from utmp, which is not Y2038 safe. This feature has been completely removed and Samba will always return an empty list. smb.conf changes ================ ? Parameter Name????????????????????????? Description???? Default ? --------------????????????????????????? -----------???? ------- ? smb3 unix extensions??????????????...

...======== Get locally logged on users from utmp ------------------------------------- The Workstation Service Remote Protocol [MS-WKST] calls NetWkstaGetInfo level 102 and NetWkstaEnumUsers level 0 and 1 return the list of locally logged on users. Samba was getting the list from utmp, which is not Y2038 safe. This feature has been completely removed and Samba will always return an empty list. smb.conf changes ================ ? Parameter Name????????????????????????? Description???? Default ? --------------????????????????????????? -----------???? ------- ? smb3 unix extensions??????????????...

...======== Get locally logged on users from utmp ------------------------------------- The Workstation Service Remote Protocol [MS-WKST] calls NetWkstaGetInfo level 102 and NetWkstaEnumUsers level 0 and 1 return the list of locally logged on users. Samba was getting the list from utmp, which is not Y2038 safe. This feature has been completely removed and Samba will always return an empty list. smb.conf changes ================ ? Parameter Name????????????????????????? Description???? Default ? --------------????????????????????????? -----------???? ------- ? smb3 unix extensions??????????????...

...======== Get locally logged on users from utmp ------------------------------------- The Workstation Service Remote Protocol [MS-WKST] calls NetWkstaGetInfo level 102 and NetWkstaEnumUsers level 0 and 1 return the list of locally logged on users. Samba was getting the list from utmp, which is not Y2038 safe. This feature has been completely removed and Samba will always return an empty list. smb.conf changes ================ ? Parameter Name????????????????????????? Description???? Default ? --------------????????????????????????? -----------???? ------- ? smb3 unix extensions??????????????...