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

Groups > linux.debian.user > #191570

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

From Michael Fothergill <michael.fothergill@gmail.com>
Newsgroups linux.debian.user
Subject Re: Question on CVE-2017-5754 on Debian 8.9
Date 2018-01-26 00:10 +0100
Message-ID <vbYOB-3MC-1@gated-at.bofh.it> (permalink)
References (11 earlier) <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> <vbYlB-3o7-27@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On 25 January 2018 at 22:35, Michael Lange <klappnase@freenet.de> wrote:

> 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.
>

​Should it not be ARCH =​x86-64 rather than amd64.

It is so confusing.

MF

>
>  >
> > 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