March 2018 - kernelnewbies@kernelnewbies.org - Kernelnewbies Mailing Lists

Submitted patch, what to do next
by Alex Arvelaez March 8, 2018

March 8, 2018

Hello, I sent a small patch to the LKML. I sent it to one of the mantainers (as per get_mantainers.pl) and I CC-ed linux-kernel(a)vger.kernel.org. I'm not entirely sure I did everything properly and I was wondering how long does it usually take to get any feedback? It's been a couple weeks since I sent it. Any advice is appreciated, thanks! Regards, Alex

6 5

Re: Year 2038 time set problem
by Alex Arvelaez March 5, 2018

March 5, 2018

On Mar 4, 2018 9:21 PM, Ruben Safir <ruben(a)mrbrklyn.com> wrote: > > On 03/04/2018 05:24 PM, valdis.kletnieks(a)vt.edu wrote: > > If you can't afford the disruption of service a reboot causes, you *really* > > need to be deploying HA or load-balancer solutions. > > > > Because if you can't afford a reboot's worth of 15-20 minutes of downtime, you > > *really* can't afford the 6-8 hours you're probably going to be down if a chip > > soldered onto the motherboard/backplane fries. > > > > (All of $DAYJOB's important systems are behind HA or load-balancers, as well as > > HA-capable storage. Let's just say that some vendors make it easier than > > others to set up 8+2 RAID6 across 10 separate shelves of storage, and designing > > mutli-petabyte solutions without single points of failure is harder than it looks :) > > > > > These questions always lead into these philosophical discussions as to > how I should run my boxes and theoretical flights of opinionated rubbish > that I am not interested in. I got the answer to the question I needed > and it is very sobering. > > I am not setting up a high availability cluster in my house, thank you. If you don't need high availability, what's the problem with the occasional reboot? > The linux kernel is integrated into dozens of devices which never see > the light of day for kernel upgrades from PPOE routers, IOT devices, > cellphones, VOIP boxes, electrocardiograms, menu displays for McDonalds, > signal boxes on train systems, etc etc etc. > > What has been described is a huge security problem and your solution is > a non-starter and doesn't help the broader discussion Device makers don't love updating their devices, I don't see how you could fix that sadly. What's your solution? Regards, Alex

6 11

Re: Year 2038 time set problem
by Alex Arvelaez March 5, 2018

March 5, 2018

On Mar 5, 2018 6:30 AM, Bernd Petrovitsch <bernd(a)petrovitsch.priv.at> wrote: > > On Mon, 2018-03-05 at 02:35 +0000, Alex Arvelaez wrote: > [...] > > Device makers don't love updating their devices, I don't see how you > > could fix that sadly. What's your solution? > > It's much worse for varying reasons. > > And why should "we" (whoever that is) fix the problems of others? I wasn't saying the kernel community should take on this problem. I was saying the kernel community can't possibly fix this problem. > The upstream can't do anything directly if the downstream simply > refuses to update (if there are fixes to real threats) and/or reboot > (if it's the kernel). We agree on all points. :) Regards, Alex

2 1

Re: Build error with O= option
by Alex Arvelaez March 5, 2018

March 5, 2018

On Mar 5, 2018 7:04 AM, Gioh Kim <gurugio(a)gmail.com> wrote: > > Hi, > > I am trying to use O=<dir> option when building kernel. > It failed with missing .config file error. > I checked out the message and found out it tried to read .config in > the output directory. > > It's strange because there is no command to copy .config to the output > directory. > I tested v4.14 and v4.15, and both failed. Depending on your distro they may provide you with their config file. You can create a default configuration by doing: make defconfig O=$dir cd $dir make Where $dir is wherever you want the output to be. Regards, Alex

2 1

Re: Year 2038 time set problem
by Alex Arvelaez March 5, 2018

March 5, 2018

On Mar 4, 2018 3:21 PM, Ruben Safir <ruben(a)mrbrklyn.com> wrote: > > On 03/04/2018 01:31 PM, valdis.kletnieks(a)vt.edu wrote: > > Note that saying "The CPU isn't vulnerable to Meltdown/Spectre, therefor > > the 4.1 kernel is OK" is *incredibly* wrong. > > > > For the record, since 4.1 came out, there's been at *least* a dozen security > > issues in the Linux kernel that have been a *lot* scarier for security > > professionals than the Meltdown/Spectre issue. That only got any news coverage > > because it was an actual hardware design flaw that was believed to be difficult > > to easily fix with software changes... > > By this standard, it is necessary to update the kernel and reboot nearly > every week. Is that right? You can kexec into the newer kernel to avoid rebooting if you absolutely must but yeah the best practice is to keep your system up to date and that requires some disruption of service. There's also kernel live patching which would allow you to patch the kernel without rebooting but I don't know how well supported that option is. > -- > So many immigrant groups have swept through our town > that Brooklyn, like Atlantis, reaches mythological > proportions in the mind of the world - RI Safir 1998 > http://www.mrbrklyn.com > > DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 > http://www.nylxs.com - Leadership Development in Free Software > http://www2.mrbrklyn.com/resources - Unpublished Archive > http://www.coinhangout.com - coins! > http://www.brooklyn-living.com > > Being so tracked is for FARM ANIMALS and and extermination camps, > but incompatible with living as a free human being. -RI Safir 2013 > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies(a)kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies Regards, Alex

4 11

Build error with O= option
by Gioh Kim March 5, 2018

March 5, 2018

Hi, I am trying to use O=<dir> option when building kernel. It failed with missing .config file error. I checked out the message and found out it tried to read .config in the output directory. It's strange because there is no command to copy .config to the output directory. I tested v4.14 and v4.15, and both failed. I googled that error message and found one thread in the stackoverflow: https://stackoverflow.com/questions/28603372/kernel-compilation-not-finding… Is it two years old but not fixed yet? Or did I use O= option wrong? FYI, following is my error message. gohkim@ws00837:~/work/linux-torvalds$ make O=./output V=1 make -C /home/gohkim/work/linux-torvalds/output KBUILD_SRC=/home/gohkim/work/linux-torvalds \ -f /home/gohkim/work/linux-torvalds/Makefile make[1]: Entering directory '/home/gohkim/work/linux-torvalds/output' make -f ../scripts/Makefile.build obj=arch/x86/entry/syscalls all make -f ../scripts/Makefile.build obj=scripts/basic (cat /dev/null; ) > scripts/basic/modules.order rm -f .tmp_quiet_recordmcount make -f ../scripts/Makefile.build obj=arch/x86/tools relocs make -f ../Makefile silentoldconfig make -f ../scripts/Makefile.build obj=scripts/basic (cat /dev/null; ) > scripts/basic/modules.order rm -f .tmp_quiet_recordmcount ln -fsn .. source /bin/bash ../scripts/mkmakefile \ .. . 4 15 GEN ./Makefile make -f ../scripts/Makefile.build obj=scripts/kconfig silentoldconfig mkdir -p include/config include/generated test -e include/generated/autoksyms.h || \ touch include/generated/autoksyms.h scripts/kconfig/conf --silentoldconfig Kconfig *** *** Configuration file ".config" not found! *** *** Please run some configurator (e.g. "make oldconfig" or *** "make menuconfig" or "make xconfig"). *** ../scripts/kconfig/Makefile:38: recipe for target 'silentoldconfig' failed make[3]: *** [silentoldconfig] Error 1 ../Makefile:524: recipe for target 'silentoldconfig' failed make[2]: *** [silentoldconfig] Error 2 /home/gohkim/work/linux-torvalds/Makefile:604: recipe for target 'include/config/auto.conf' failed make[1]: *** [include/config/auto.conf] Error 2 make[1]: Leaving directory '/home/gohkim/work/linux-torvalds/output' Makefile:146: recipe for target 'sub-make' failed make: *** [sub-make] Error 2 -- Best regards, Gioh Kim

1 0

Re: Year 2038 time set problem
by Alex Arvelaez March 5, 2018

March 5, 2018

On Mar 4, 2018 10:15 PM, Ruben Safir <ruben(a)mrbrklyn.com> wrote: > > On 03/04/2018 09:35 PM, Alex Arvelaez wrote: > > If you don't need high availability, what's the problem with the occasional reboot? > > I have a life, and its a chore to reboot the 3 boxes after every easy: set up a cronjob to do it for you. > upgrade. It runs my phones, my TV, my house security, and my mail and > webserver and booting them all is a PIA. If it is raining security > holes with every kernel upgrade, that is a big problem, and that is > before all these appliances. there is no "raining security holes with every kernel update", simply bugs get found after release or can't make it to that release cycle(a bug fix may cause regressions that need to be fixed, testing, etc.). Keep your OS up-to-date and you'll be fine. Regards, Alex

3 3

Re: Year 2038 time set problem
by tali.perry＠nuvoton.com March 5, 2018

March 5, 2018

It is not secure because it is not fixed for these issues: https://meltdownattack.com/ If you're CPU is not listed there (unlikely) or your use case does not need that much security( depending on your application) you can stay with 4.1. Fixing these vulnerabilities is a lot of work and no one will fix them for old OS. Tali Perry -----Original Message----- From: kernelnewbies-request(a)kernelnewbies.org [mailto:kernelnewbies-request@kernelnewbies.org] Sent: Thursday, March 1, 2018 7:00 PM To: kernelnewbies(a)kernelnewbies.org Subject: Kernelnewbies Digest, Vol 88, Issue 1 Send Kernelnewbies mailing list submissions to kernelnewbies(a)kernelnewbies.org To subscribe or unsubscribe via the World Wide Web, visit https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.kernelnewbies.or… or, via email, send a message with subject or body 'help' to kernelnewbies-request(a)kernelnewbies.org You can reach the person managing the list at kernelnewbies-owner(a)kernelnewbies.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Kernelnewbies digest..." Today's Topics: 1. Re: Year 2038 time set problem (techi eth) 2. Re: Year 2038 time set problem (Greg KH) ---------------------------------------------------------------------- Message: 1 Date: Thu, 1 Mar 2018 14:49:05 +0530 From: techi eth <techieth(a)gmail.com> To: Greg KH <greg(a)kroah.com> Cc: Valdis Kletnieks <valdis.kletnieks(a)vt.edu>, kernelnewbies(a)kernelnewbies.org Subject: Re: Year 2038 time set problem Message-ID: <CAJw2sSAJBKBR33sLdM285LbRfJTWrZwSDJQUnNzYju6QQTErqw(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" I am just trying to know why 4.1 kernel is insecure ? I have try to look but not able to get right answer. Could you please give me hint or link. I only see it is going to EOL by May 2018. https://urldefense.proofpoint.com/v2/url?u=https-3A__www.kernel.org_categor… Thanks On Sat, Feb 24, 2018 at 9:20 PM, Greg KH <greg(a)kroah.com> wrote: > On Sat, Feb 24, 2018 at 07:29:35PM +0530, techi eth wrote: > > I am trying on 32 Bit micro board with ubifs file system with Linux > Kernel > > 4.1. > > And in your testing, did you find any problems? > > 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. > > best of luck! > > greg k-h >

4 6

Year 2038 time set problem
by techi eth March 1, 2018

March 1, 2018

Hi, Which Linux kernel version have Year 2038 problem solved for Linux running on 32 Bit system. https://en.wikipedia.org/wiki/Year_2038_problem

4 7