Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #191567

Re: Question on CVE-2017-5754 on Debian 8.9

Path csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From Michael Lange <klappnase@freenet.de>
Newsgroups linux.debian.user
Subject Re: Question on CVE-2017-5754 on Debian 8.9
Date Thu, 25 Jan 2018 23:40:03 +0100
Message-ID <vbYlB-3o7-27@gated-at.bofh.it> (permalink)
References <vbxbI-2FS-21@gated-at.bofh.it> <vby7M-3fx-5@gated-at.bofh.it> <vbzQd-4ml-3@gated-at.bofh.it> <vbBS1-5AP-3@gated-at.bofh.it> <vbE3v-6Or-3@gated-at.bofh.it> <vbMaJ-43Q-11@gated-at.bofh.it> <vbMu6-4do-9@gated-at.bofh.it> <vbOmd-5qu-3@gated-at.bofh.it> <vbPih-60X-5@gated-at.bofh.it> <vbPrY-6kd-3@gated-at.bofh.it> <vbPUZ-6zn-7@gated-at.bofh.it> <vbSpQ-8dj-7@gated-at.bofh.it> <vbTFg-rP-9@gated-at.bofh.it> <vbWWt-2AP-9@gated-at.bofh.it> <vbXSz-3dW-43@gated-at.bofh.it>
X-Mailbox-Line From debian-user-request@lists.debian.org Thu Jan 25 22:37:49 2018
Old-Return-Path <klappnase@freenet.de>
X-Amavis-Spam-Status No, score=-7.109 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, MURPHY_FINANCE10=0.5, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
X-Policyd-Weight using cached result; rate:hard: -7
X-Mailer Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version 1.0
Content-Type text/plain; charset=UTF-8
Content-Transfer-Encoding 8bit
X-Originated-At 46.244.224.240!53446
X-Mailing-List <debian-user@lists.debian.org> archive/latest/731360
List-ID <debian-user.lists.debian.org>
List-URL <https://lists.debian.org/debian-user/>
List-Archive https://lists.debian.org/msgid-search/20180125233521.1945f0a0f225f353e9d26c44@freenet.de
Approved robomod@news.nic.it
Lines 148
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Thu, 25 Jan 2018 23:35:21 +0100
X-Original-Message-ID <20180125233521.1945f0a0f225f353e9d26c44@freenet.de>
X-Original-References <20180124173840.sarlbzwddenpqypy@eeg.ccf.org> <CANc=Sd2hvnrkx=h+4PLauj10DYd8fu4p4hu594Yb0peExoD_ug@mail.gmail.com> <CANc=Sd0MmOzK6GT468BY_h1ezDS_M48crez7ka4akx1i9rM2-A@mail.gmail.com> <20180124233211.f9afd587e7214730282f7dde@freenet.de> <CANc=Sd0Up4274=f=XzZpz+f9sMkt2wQvxcmmk4Qa_gZGhGev+g@mail.gmail.com> <CANc=Sd03YeqC9affc+jRK8duCTTb0ug_+L7P5SbNZyuZ+ivWdQ@mail.gmail.com> <20180125105042.db970fffe0a6a8055b6fb7a6@freenet.de> <CANc=Sd2TR1NNtA2+prrO8Y_t56oUinXV-7G6wOAXTL8FCbNRPg@mail.gmail.com> <CANc=Sd3eHnnTZ9b__EJAf9WEApp_AZmGFR4ia-P3LWKWuRsU+g@mail.gmail.com> <20180125130140.aesrfsqhx2s4l4eq@eeg.ccf.org> <CANc=Sd1w5BvSP2Q+EjBhR=XamNX9Cz=e5SrhbS7XwJ6SfXcePQ@mail.gmail.com> <CANc=Sd1nBSCg2-bYMsYVm1Ag0=ZS6E4OOSTprA80T=oGkbmb7A@mail.gmail.com> <CANc=Sd0BpyUD8VYtJorAgbjDzUQPvkj6Z2t=BZYZfrBEpX5zuQ@mail.gmail.com> <20180125215756.4b4eb909e91504b0e672a730@freenet.de> <CANc=Sd30kdq2meAv+tYruEEwtmsdZcJphMK1QrTuOjArcpAqew@mail.gmail.com>
Xref csiph.com linux.debian.user:191567

Show key headers only | View raw

Hi,

On Thu, 25 Jan 2018 21:43:19 +0000
Michael Fothergill <michael.fothergill@gmail.com> wrote:

> > Not sure, but didn't you want the very latest 4.15rc for some
> > Meltdown/Spectre issues? Are these also in 4.14.15?
> >
> > ​
> >
> 
> ​I copied the config file from the boot directory for the current 4.15.0
> rc8 kernel as .config.
> 
> I then ran make menuconfig and then realised I didn't need to change
> anything and exited.
> 
> I didn't run your
> 
> yes ""|  make oldconfig thing - it seemed a bit peculiar to me.
> 
> Maybe I should have.
> 
> Instead I ran the command recommended here:
> 
> https://wiki.debian.org/BuildADebianKernelPackage
> 
> which was
> 
> make ARCH=i386 defconfig

Didn't want to build for amd64? If yes, you should have followed the
advice from that page saying:
"Create a defconfig with the following command, please change ARCH=i386
to match your target architecture:"
I only built kernel packages for amd64 on an amd64 system, so I never had
to explicitely specify ARCH.

> 
> I then ran
> 
> make-kpkg
> 
> and it then asked me lots of questions concerning kernel options that I
> had to answer interactively.
> 
> I think I should have tried your funny quotation pipe command with the
> oldconfig option - it would have been better.

Actually I don't remember which tutorial I borrowed this from; as far as
I know it will set the default values for any new option not present in
the old config.

> 
> ​​
> 
> ​Here is some of the output before it crashed:​
> 
> 
> 
> kexec system call (KEXEC) [Y/n/?] y
> kexec file based system call (KEXEC_FILE) [N/y/?] n
> kernel crash dumps (CRASH_DUMP) [Y/n/?] y
> kexec jump (KEXEC_JUMP) [N/y/?] n
> Physical address where the kernel is loaded (PHYSICAL_START) [0x1000000]
> 0x1000000
> Build a relocatable kernel (RELOCATABLE) [Y/n/?] y
>   Randomize the address of the kernel image (KASLR) (RANDOMIZE_BASE)
> [Y/n/?] y
> Alignment value to which kernel should be aligned (PHYSICAL_ALIGN)
> [0x200000] 0x200000
> Randomize the kernel memory sections (RANDOMIZE_MEMORY) [Y/n/?] y
> Support for hot-pluggable CPUs (HOTPLUG_CPU) [Y/?] y
>   Set default setting of cpu0_hotpluggable (BOOTPARAM_HOTPLUG_CPU0)
> [N/y/?] n
>   Debug CPU0 hotplug (DEBUG_HOTPLUG_CPU0) [N/y/?] n
> vsyscall table for legacy applications
>   1. Native (LEGACY_VSYSCALL_NATIVE)
> > 2. Emulate (LEGACY_VSYSCALL_EMULATE)
>   3. None (LEGACY_VSYSCALL_NONE)
> choice[1-3?]: 2
> Built-in kernel command line (CMDLINE_BOOL) [N/y/?] n
> #
> # configuration written to .config
> #
> make[2]: Leaving directory '/usr/src/linux-4.14.15'
> make    \
>              ARCH=x86_64  dep
> make[2]: Entering directory '/usr/src/linux-4.14.15'
> Makefile:942: *** "Cannot generate ORC metadata for
> CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or
> elfutils-libelf-devel".  Stop. make[2]: Leaving directory
> '/usr/src/linux-4.14.15' debian/ruleset/targets/common.mk:194: recipe
> for target 'debian/stamp/conf/kernel-conf' failed
> make[1]: *** [debian/stamp/conf/kernel-conf] Error 2
> make[1]: Leaving directory '/usr/src/linux-4.14.15'
> /usr/share/kernel-package/ruleset/minimal.mk:93: recipe for target
> 'debian/stamp/conf/minimal_debian' failed
> make: *** [debian/stamp/conf/minimal_debian] Error 2
> Failed to create a ./debian directory:  at /usr/bin/make-kpkg line 970.
> root@mikef-PC:/usr/src/linux-4.14.15#

Funny thing: just for the sport I tried the same thing on a siduction
system this evening and ended up with the same error message.
Had no time to investigate yet, it looks a bit like this one:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804813

but this one's old and claims to be solved.
Here:
http://forums.debian.net/viewtopic.php?t=74424
it is suggested that an upper case letter in the path to the sources
might be the culprit, but then I have upper case characters here on
stretch too, which didn't harm.
Here:
http://forums.debian.net/viewtopic.php?t=116146
it is suggested that installing gcc-<version>-plugin-dev might help,
might be worth a try. However here on stretch nothing like this is
installed, and still it works. Maybe libgcc-<version>-dev is missing?
Here:
https://superuser.com/questions/677372/error-when-compiling-linux-kernel
someone suggests that bc must be installed. Got that here on stretch, not
sure if it might be missing on siduction.

> 
> 
> It has written things to the config file so I think I might be wise to
> delete it, copy it over again
> and repeat everything with the Shakespearian pipe command next time.
> 
> 
> 
> Suggestions on recovering gracefully here are welcome.

I always cleaned up the source directory with 

# make mrproper

After that you should be able to start over again.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Earth -- mother of the most beautiful women in the universe.
		-- Apollo, "Who Mourns for Adonais?" stardate 3468.1

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-23 22:10 +0100
  Re: Question on CVE-2017-5754 on Debian 8.9 Sven Hartge <sven@svenhartge.de> - 2018-01-23 22:20 +0100
    Re: Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-23 22:40 +0100
      Re: Question on CVE-2017-5754 on Debian 8.9 Sven Hartge <sven@svenhartge.de> - 2018-01-23 22:40 +0100
    Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-23 23:10 +0100
      Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-23 23:50 +0100
        Re: Question on CVE-2017-5754 on Debian 8.9 Richard Hector <richard@walnut.gen.nz> - 2018-01-24 00:00 +0100
          Re: Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-24 00:10 +0100
            Re: Question on CVE-2017-5754 on Debian 8.9 Jonathan Dowland <jmtd@debian.org> - 2018-01-24 11:20 +0100
              Re: Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-24 17:10 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-24 19:20 +0100
          Re: Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-24 00:10 +0100
            Re: Question on CVE-2017-5754 on Debian 8.9 Michael Stone <mstone@debian.org> - 2018-01-24 00:20 +0100
              Re: Question on CVE-2017-5754 on Debian 8.9 Richard Hector <richard@walnut.gen.nz> - 2018-01-24 02:20 +0100
          Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 12:20 +0100
            Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 12:40 +0100
              Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 13:10 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 13:50 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Sven Hartge <sven@svenhartge.de> - 2018-01-24 14:10 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 14:30 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Sven Hartge <sven@svenhartge.de> - 2018-01-24 14:50 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Vincent Lefevre <vincent@vinc17.net> - 2018-01-24 15:20 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 15:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 17:10 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 17:30 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Greg Wooledge <wooledg@eeg.ccf.org> - 2018-01-24 17:30 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 18:10 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 The Wanderer <wanderer@fastmail.fm> - 2018-01-24 18:30 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Greg Wooledge <wooledg@eeg.ccf.org> - 2018-01-24 18:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 19:10 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 19:20 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 19:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 21:30 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-24 23:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 02:00 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 10:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-25 11:00 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 13:00 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 14:00 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Greg Wooledge <wooledg@eeg.ccf.org> - 2018-01-25 14:10 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 14:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 17:20 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-25 18:30 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 19:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 19:50 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-25 22:00 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Brian <ad44@cityscape.co.uk> - 2018-01-25 20:30 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 22:00 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 18:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-25 22:10 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 23:10 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 23:30 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 23:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-25 23:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-26 00:10 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-26 00:20 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 18:30 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Vincent Lefevre <vincent@vinc17.net> - 2018-01-25 15:30 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Greg Wooledge <wooledg@eeg.ccf.org> - 2018-01-25 15:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 David Wright <deblis@lionunicorn.co.uk> - 2018-01-25 16:10 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Vincent Lefevre <vincent@vinc17.net> - 2018-01-25 23:20 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Jochen Spieker <ml@well-adjusted.de> - 2018-01-25 21:30 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Sven Joachim <svenjoac@gmx.de> - 2018-01-25 21:40 +0100
                Re: Question on CVE-2017-5754 on Debian 8.9 Vincent Lefevre <vincent@vinc17.net> - 2018-01-25 23:40 +0100

csiph-web