Re: Year 2038 time set problem

Hi, 2018-02-26 16:21 GMT+01:00 : > On Mon, 26 Feb 2018 14:15:53 +0100, Piotr Figiel said: > >> According to kernel.org website 4.1 has projected EOL in May 2018. Is >> the information about kernel releases on kernel.org irrelevant/ >> shouldn't be trusted? Or my

Re: Year 2038 time set problem

Hi, 2018-02-24 16:50 GMT+01:00 Greg KH : > Also note that the 4.1 kernel is very old and obsolete and insecure, and > should NOT be used for any devices in the year 2038. According to kernel.org website 4.1 has projected EOL in May 2018. Is the information about kernel releases

Security updates of Linux kernel (was: Re: Year 2038 time set problem)

Hi, 2018-02-26 15:16 GMT+01:00 Greg KH : > On Mon, Feb 26, 2018 at 02:15:53PM +0100, Piotr Figiel wrote: >> 2018-02-24 16:50 GMT+01:00 Greg KH : >> > Also note that the 4.1 kernel is very old and obsolete and insecure, and >> > should NOT be used for any devices in

where __struct_cpy_bug is defined

Dear all I find a function of __struct_cpy_bug in linux kernel v2.4.0.But I only it's declaration.I want to know where __struct_cpy_bug is defined ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org

Re: Year 2038 time set problem

On Mon, Feb 26, 2018 at 01:19:41PM -0800, Dave Stevens wrote: > it makes me curious Greg. The little board *might* easily and lots of > other little boards *definitely will* be put into IoT gadgets for which > no updates are realistically available but whose owners will want to > use them as long