DOCSLIB.ORG

Dec 12 11:12:06 Tununo-Vates Kernel

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Dec 12 11:12:06 Tununo-Vates Kernel -- Journal begins at Fri 2020-09-18 22:30:59 WEST, ends at Sat 2020-12-12 17:02:32 WET. -- Dec 12 11:12:06 tununo-vates kernel: microcode: microcode updated early to revision 0x838, date = 2019-04-22 Dec 12 11:12:06 tununo-vates kernel: Linux version 5.9.13-arch1-1 (linux@archlinux) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35.1) #1 SMP PREEMPT Tue, 08 Dec 2020 12:09:55 +0000 Dec 12 11:12:06 tununo-vates kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=0e62d18b-b71d-4bbb-9f71- 934ea89b2f3a rw quiet resume=UUID=2d897922-8b2d-482a-9539- 015f44054253 loglevel=3 nowatchdog Dec 12 11:12:06 tununo-vates kernel: KERNEL supported cpus: Dec 12 11:12:06 tununo-vates kernel: Intel GenuineIntel Dec 12 11:12:06 tununo-vates kernel: AMD AuthenticAMD Dec 12 11:12:06 tununo-vates kernel: Hygon HygonGenuine Dec 12 11:12:06 tununo-vates kernel: Centaur CentaurHauls Dec 12 11:12:06 tununo-vates kernel: zhaoxin Shanghai Dec 12 11:12:06 tununo-vates kernel: x86/fpu: x87 FPU will use FXSAVE Dec 12 11:12:06 tununo-vates kernel: BIOS-provided physical RAM map: Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usable Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] ACPI NVS Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x0000000000070000-0x000000000008ffff] usable Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x0000000000090000-0x000000000009ffff] reserved Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000200fffff] reserved Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x0000000020100000-0x0000000078147fff] usable Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x0000000078148000-0x00000000781d7fff] type 20 Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x00000000781d8000-0x0000000078a57fff] reserved Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x0000000078a58000-0x0000000078b57fff] ACPI NVS Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x0000000078b58000-0x0000000078b97fff] ACPI data Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x0000000078b98000-0x00000000796f1fff] usable Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x00000000796f2000-0x0000000079ff1fff] reserved Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x0000000079ff2000-0x0000000079ffffff] usable Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x00000000e00f8000-0x00000000e00f8fff] reserved Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x00000000fed01000-0x00000000fed01fff] reserved Dec 12 11:12:06 tununo-vates kernel: BIOS-e820: [mem 0x00000000ffc00000-0x00000000ffffffff] reserved Dec 12 11:12:06 tununo-vates kernel: NX (Execute Disable) protection: active Dec 12 11:12:06 tununo-vates kernel: efi: EFI v2.40 by INSYDE Corp. Dec 12 11:12:06 tununo-vates kernel: efi: ACPI 2.0=0x78b97014 ESRT=0x78280418 SMBIOS=0x7840f000 Dec 12 11:12:06 tununo-vates kernel: SMBIOS 2.7 present. Dec 12 11:12:06 tununo-vates kernel: DMI: LENOVO 80M0/Mini, BIOS C0CN31WW 07/30/2015 Dec 12 11:12:06 tununo-vates kernel: tsc: Detected 2166.667 MHz processor Dec 12 11:12:06 tununo-vates kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Dec 12 11:12:06 tununo-vates kernel: e820: remove [mem 0x000a0000-0x000fffff] usable Dec 12 11:12:06 tununo-vates kernel: last_pfn = 0x7a000 max_arch_pfn = 0x400000000 Dec 12 11:12:06 tununo-vates kernel: MTRR default type: uncachable Dec 12 11:12:06 tununo-vates kernel: MTRR fixed ranges enabled: Dec 12 11:12:06 tununo-vates kernel: 00000-9FFFF write-back Dec 12 11:12:06 tununo-vates kernel: A0000-BFFFF uncachable Dec 12 11:12:06 tununo-vates kernel: C0000-FFFFF write-protect Dec 12 11:12:06 tununo-vates kernel: MTRR variable ranges enabled: Dec 12 11:12:06 tununo-vates kernel: 0 base 0FFC00000 mask FFFC00000 write-protect Dec 12 11:12:06 tununo-vates kernel: 1 base 000000000 mask F80000000 write-back Dec 12 11:12:06 tununo-vates kernel: 2 base 07C000000 mask FFC000000 uncachable Dec 12 11:12:06 tununo-vates kernel: 3 base 07B000000 mask FFF000000 uncachable Dec 12 11:12:06 tununo-vates kernel: 4 base 07AE00000 mask FFFE00000 uncachable Dec 12 11:12:06 tununo-vates kernel: 5 disabled Dec 12 11:12:06 tununo-vates kernel: 6 disabled Dec 12 11:12:06 tununo-vates kernel: 7 disabled Dec 12 11:12:06 tununo-vates kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT Dec 12 11:12:06 tununo-vates kernel: esrt: Reserving ESRT space from 0x0000000078280418 to 0x0000000078280450. Dec 12 11:12:06 tununo-vates kernel: check: Scanning 1 areas for low memory corruption Dec 12 11:12:06 tununo-vates kernel: Secure boot could not be determined Dec 12 11:12:06 tununo-vates kernel: RAMDISK: [mem 0x369ff000- 0x374f6fff] Dec 12 11:12:06 tununo-vates kernel: ACPI: Early table checksum verification disabled Dec 12 11:12:06 tununo-vates kernel: ACPI: RSDP 0x0000000078B97014 000024 (v02 LENOVO) Dec 12 11:12:06 tununo-vates kernel: ACPI: XSDT 0x0000000078B97120 0000A4 (v01 LENOVO CB-01 00000003 01000013) Dec 12 11:12:06 tununo-vates kernel: ACPI: FACP 0x0000000078B93000 00010C (v05 LENOVO CB-01 00000003 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: DSDT 0x0000000078B83000 00BDDB (v02 LENOVO CB-01 00000003 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: FACS 0x0000000078B1E000 000040 Dec 12 11:12:06 tununo-vates kernel: ACPI: UEFI 0x0000000078B96000 000236 (v01 LENOVO CB-01 00000001 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: MSDM 0x0000000078B95000 000055 (v03 LENOVO CB-01 00000001 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: UEFI 0x0000000078B94000 000042 (v01 LENOVO CB-01 00000000 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: HPET 0x0000000078B92000 000038 (v01 LENOVO CB-01 00000003 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: APIC 0x0000000078B91000 000084 (v03 LENOVO CB-01 00000003 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: MCFG 0x0000000078B90000 00003C (v01 LENOVO CB-01 00000003 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: SSDT 0x0000000078B82000 0006BD (v01 INSYDE CpuDptf 00000003 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: SSDT 0x0000000078B81000 0004D7 (v01 INSYDE DptfTab 00000003 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: SSDT 0x0000000078B80000 000763 (v01 INSYDE CpuPm 00003000 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: SSDT 0x0000000078B7F000 000290 (v01 INSYDE Cpu0Tst 00003000 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: SSDT 0x0000000078B7E000 00017A (v01 INSYDE ApTst 00003000 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: SLIC 0x0000000078B8F000 000176 (v01 LENOVO CB-01 00000003 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: SSDT 0x0000000078B7D000 0003E6 (v01 INSYDE IsctTabl 00001000 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: FPDT 0x0000000078B7C000 000044 (v01 LENOVO CB-01 00000002 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: BGRT 0x0000000078B7B000 000038 (v01 LENOVO CB-01 00000001 ACPI 00040000) Dec 12 11:12:06 tununo-vates kernel: ACPI: Local APIC address 0xfee00000 Dec 12 11:12:06 tununo-vates kernel: No NUMA configuration found Dec 12 11:12:06 tununo-vates kernel: Faking a node at [mem 0x0000000000000000-0x0000000079ffffff] Dec 12 11:12:06 tununo-vates kernel: NODE_DATA(0) allocated [mem 0x77e11000-0x77e14fff] Dec 12 11:12:06 tununo-vates kernel: Zone ranges: Dec 12 11:12:06 tununo-vates kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff] Dec 12 11:12:06 tununo-vates kernel: DMA32 [mem 0x0000000001000000-0x0000000079ffffff] Dec 12 11:12:06 tununo-vates kernel: Normal empty Dec 12 11:12:06 tununo-vates kernel: Device empty Dec 12 11:12:06 tununo-vates kernel: Movable zone start for each node Dec 12 11:12:06 tununo-vates kernel: Early memory node ranges Dec 12 11:12:06 tununo-vates kernel: node 0: [mem 0x0000000000001000-0x000000000006efff] Dec 12 11:12:06 tununo-vates kernel: node 0: [mem 0x0000000000070000-0x000000000008ffff] Dec 12 11:12:06 tununo-vates kernel: node 0: [mem 0x0000000000100000-0x000000001fffffff] Dec 12 11:12:06 tununo-vates kernel: node 0: [mem 0x0000000020100000-0x0000000078147fff] Dec 12 11:12:06 tununo-vates kernel: node 0: [mem 0x0000000078b98000-0x00000000796f1fff] Dec 12 11:12:06 tununo-vates kernel: node 0: [mem 0x0000000079ff2000-0x0000000079ffffff] Dec 12 11:12:06 tununo-vates kernel: Zeroed struct page in unavailable ranges: 29890 pages Dec 12 11:12:06 tununo-vates kernel: Initmem setup node 0 [mem 0x0000000000001000-0x0000000079ffffff] Dec 12 11:12:06 tununo-vates kernel: On node 0 totalpages: 494398 Dec 12 11:12:06 tununo-vates kernel: DMA zone: 64 pages used for memmap Dec 12 11:12:06 tununo-vates kernel: DMA zone: 1142 pages reserved Dec 12 11:12:06 tununo-vates kernel: DMA zone: 3982 pages, LIFO batch:0 Dec 12 11:12:06 tununo-vates kernel: DMA32 zone: 7744 pages used for memmap Dec 12 11:12:06 tununo-vates kernel: DMA32 zone: 490416 pages, LIFO batch:63 Dec 12 11:12:06 tununo-vates kernel: x86/hpet: Will disable the HPET for this platform because it's not reliable Dec 12 11:12:06 tununo-vates kernel: Reserving Intel graphics memory at [mem 0x7b000000-0x7effffff] Dec 12 11:12:06 tununo-vates kernel: ACPI: PM-Timer IO Port: 0x408 Dec 12 11:12:06 tununo-vates kernel: ACPI: Local APIC address 0xfee00000 Dec 12 11:12:06 tununo-vates kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1]) Dec 12 11:12:06 tununo-vates kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1]) Dec 12 11:12:06 tununo-vates kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1]) Dec 12 11:12:06 tununo-vates kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1]) Dec 12 11:12:06 tununo-vates kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-86 Dec 12 11:12:06 tununo-vates kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Dec 12 11:12:06 tununo-vates kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Dec 12 11:12:06 tununo-vates kernel: ACPI: IRQ0 used by override.
Load more

Recommended publications
  • Measuring Software Performance on Linux Technical Report
    Measuring Software Performance on Linux Technical Report November 21, 2018 Martin Becker Samarjit Chakraborty Chair of Real-Time Computer Systems Chair of Real-Time Computer Systems Technical University of Munich Technical University of Munich Munich, Germany Munich, Germany [email protected] [email protected] OS program program CPU .text .bss + + .data +/- + instructions cache branch + coherency scheduler misprediction core + pollution + migrations data + + interrupt L1i$ miss access + + + + + + context mode + + (TLB flush) TLB + switch data switch miss L1d$ +/- + (KPTI TLB flush) miss prefetch +/- + + + higher-level readahead + page cache miss walk + + multicore + + (TLB shootdown) TLB coherency page DRAM + page fault + cache miss + + + disk + major minor I/O Figure 1. Event interaction map for a program running on an Intel Core processor on Linux. Each event itself may cause processor cycles, and inhibit (−), enable (+), or modulate (⊗) others. Abstract that our measurement setup has a large impact on the results. Measuring and analyzing the performance of software has More surprisingly, however, they also suggest that the setup reached a high complexity, caused by more advanced pro- can be negligible for certain analysis methods. Furthermore, cessor designs and the intricate interaction between user we found that our setup maintains significantly better per- formance under background load conditions, which means arXiv:1811.01412v2 [cs.PF] 20 Nov 2018 programs, the operating system, and the processor’s microar- chitecture. In this report, we summarize our experience on it can be used to improve high-performance applications. how performance characteristics of software should be mea- CCS Concepts • Software and its engineering → Soft- sured when running on a Linux operating system and a ware performance; modern processor.
    [Show full text]
  • Linux Kernel and Driver Development Training Slides
    Linux Kernel and Driver Development Training Linux Kernel and Driver Development Training © Copyright 2004-2021, Bootlin. Creative Commons BY-SA 3.0 license. Latest update: October 9, 2021. Document updates and sources: https://bootlin.com/doc/training/linux-kernel Corrections, suggestions, contributions and translations are welcome! embedded Linux and kernel engineering Send them to [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/470 Rights to copy © Copyright 2004-2021, Bootlin License: Creative Commons Attribution - Share Alike 3.0 https://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Document sources: https://github.com/bootlin/training-materials/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/470 Hyperlinks in the document There are many hyperlinks in the document I Regular hyperlinks: https://kernel.org/ I Kernel documentation links: dev-tools/kasan I Links to kernel source files and directories: drivers/input/ include/linux/fb.h I Links to the declarations, definitions and instances of kernel symbols (functions, types, data, structures): platform_get_irq() GFP_KERNEL struct file_operations - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/470 Company at a glance I Engineering company created in 2004, named ”Free Electrons” until Feb.
    [Show full text]
  • An Evolutionary Study of Linux Memory Management for Fun and Profit Jian Huang, Moinuddin K
    An Evolutionary Study of Linux Memory Management for Fun and Profit Jian Huang, Moinuddin K. Qureshi, and Karsten Schwan, Georgia Institute of Technology https://www.usenix.org/conference/atc16/technical-sessions/presentation/huang This paper is included in the Proceedings of the 2016 USENIX Annual Technical Conference (USENIX ATC ’16). June 22–24, 2016 • Denver, CO, USA 978-1-931971-30-0 Open access to the Proceedings of the 2016 USENIX Annual Technical Conference (USENIX ATC ’16) is sponsored by USENIX. An Evolutionary Study of inu emory anagement for Fun and rofit Jian Huang, Moinuddin K. ureshi, Karsten Schwan Georgia Institute of Technology Astract the patches committed over the last five years from 2009 to 2015. The study covers 4587 patches across Linux We present a comprehensive and uantitative study on versions from 2.6.32.1 to 4.0-rc4. We manually label the development of the Linux memory manager. The each patch after carefully checking the patch, its descrip- study examines 4587 committed patches over the last tions, and follow-up discussions posted by developers. five years (2009-2015) since Linux version 2.6.32. In- To further understand patch distribution over memory se- sights derived from this study concern the development mantics, we build a tool called MChecker to identify the process of the virtual memory system, including its patch changes to the key functions in mm. MChecker matches distribution and patterns, and techniues for memory op- the patches with the source code to track the hot func- timizations and semantics. Specifically, we find that tions that have been updated intensively.
    [Show full text]
  • Review Der Linux Kernel Sourcen Von 4.9 Auf 4.10
    Review der Linux Kernel Sourcen von 4.9 auf 4.10 Reviewed by: Tested by: stecan stecan Period of Review: Period of Test: From: Thursday, 11 January 2018 07:26:18 o'clock +01: From: Thursday, 11 January 2018 07:26:18 o'clock +01: To: Thursday, 11 January 2018 07:44:27 o'clock +01: To: Thursday, 11 January 2018 07:44:27 o'clock +01: Report automatically generated with: LxrDifferenceTable, V0.9.2.548 Provided by: Certified by: Approved by: Account: stecan Name / Department: Date: Friday, 4 May 2018 13:43:07 o'clock CEST Signature: Review_4.10_0_to_1000.pdf Page 1 of 793 May 04, 2018 Review der Linux Kernel Sourcen von 4.9 auf 4.10 Line Link NR. Descriptions 1 .mailmap#0140 Repo: 9ebf73b275f0 Stephen Tue Jan 10 16:57:57 2017 -0800 Description: mailmap: add codeaurora.org names for nameless email commits ----------- Some codeaurora.org emails have crept in but the names don't exist for them. Add the names for the emails so git can match everyone up. Link: http://lkml.kernel.org/r/[email protected] 2 .mailmap#0154 3 .mailmap#0160 4 CREDITS#2481 Repo: 0c59d28121b9 Arnaldo Mon Feb 13 14:15:44 2017 -0300 Description: MAINTAINERS: Remove old e-mail address ----------- The ghostprotocols.net domain is not working, remove it from CREDITS and MAINTAINERS, and change the status to "Odd fixes", and since I haven't been maintaining those, remove my address from there. CREDITS: Remove outdated address information ----------- This address hasn't been accurate for several years now.
    [Show full text]
  • OMV Crash 25Feb2020 Syslog
    Feb 25 00:00:00 prometheus rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="858" x-info="https://www.rsyslog.com"] rsyslogd was HUPed Feb 25 00:00:00 prometheus systemd[1]: logrotate.service: Succeeded. Feb 25 00:00:00 prometheus systemd[1]: Started Rotate log files. Feb 25 00:00:01 prometheus CRON[10420]: (root) CMD (/usr/sbin/omv- mkrrdgraph >/dev/null 2>&1) Feb 25 00:09:00 prometheus systemd[1]: Starting Clean php session files... Feb 25 00:09:00 prometheus sessionclean[10668]: PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php/20151012/pam.so' - /usr/lib/php/20151012/pam.so: cannot open shared object file: No such file or directory in Unknown on line 0 Feb 25 00:09:00 prometheus sessionclean[10668]: PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php/20151012/pam.so' - /usr/lib/php/20151012/pam.so: cannot open shared object file: No such file or directory in Unknown on line 0 Feb 25 00:09:00 prometheus sessionclean[10668]: PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php/20151012/pam.so' - /usr/lib/php/20151012/pam.so: cannot open shared object file: No such file or directory in Unknown on line 0 Feb 25 00:09:00 prometheus systemd[1]: phpsessionclean.service: Succeeded. Feb 25 00:09:00 prometheus systemd[1]: Started Clean php session files. Feb 25 00:09:01 prometheus CRON[10770]: (root) CMD ( [ -x /usr/lib/ php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/ php/sessionclean; fi) Feb 25 00:15:01 prometheus CRON[10858]: (root) CMD (/usr/sbin/omv- mkrrdgraph >/dev/null 2>&1) Feb 25 00:17:01 prometheus CRON[10990]: (root) CMD ( cd / && run- parts --report /etc/cron.hourly) Feb 25 00:17:01 prometheus postfix/postsuper[10993]: fatal: scan_dir_push: open directory hold: No such file or directory Feb 25 00:30:01 prometheus CRON[11200]: (root) CMD (/usr/sbin/omv- mkrrdgraph >/dev/null 2>&1) Feb 25 00:39:00 prometheus systemd[1]: Starting Clean php session files..
    [Show full text]
  • Open Source Practice of LG Electronics
    Open Source Practice of LG Electronics Hyo Jun Im Software Platform Laboratory, LG Electronics Introduction to LG Electronics LG Electronics is a global leader and technology innovator in consumer electronics, mobile communications and home appliances. Overview This presentation covers both the open source compliance and open source engagement Compliance LG Community Engagement Open Source Compliance How LG Electronics built the open source compliance process from scratch. Steps for Building Up Open Source Compliance Process | Kick-starting open source compliance | Raising awareness | Setting up the process | Filling holes in the process | Efficient open source compliance Kick-starting Open Source Compliance | Challenges > Lack of knowledge on open source compliance > Lack of verification tools | What we did > Just rushed into writing the open source software notice in the user manual > Manual open source identification and verification | What we got > Basic knowledge of popular open source licenses > Need for automated verification tools > Knowledge on practical issues with open source compliance Raising Awareness | Introduction to relevant lawsuit case | Online / Offline training | Escalation of the open source compliance issues to management | Help from outside experts Industry Lawsuit Case • 2006 Set the precedent that the sale of a product can be prohibited 2007 • Distributors can be held responsible, and lawsuits filed against them • 2008 Similar to the case with Skype • 2010 Forced to give TVs to charity organizations as well as
    [Show full text]
  • Red Hat Enterprise Linux Roadmap
    RED HAT ENTERPRISE LINUX ROADMAP Transforming Application Delivery While Protecting Your Application Investments Ron Pacheco, Director, Product Management Karen Noel, Director of Engineering May 2, 2017 Disclaimer The content set forth herein does not constitute in any way a binding or legal agreement or impose any legal obligation or duty on Red Hat. This information is provided for discussion purposes only and is subject to change for any or no reason. MARKET REQUIREMENTS “Light up my hardware.” “Enable my operations.” Circa 2002 Circa 2017 ● Light up my hardware ● Everything I’m used to and... ● Award winning support ● More software available ● Vast ecosystem ● Less software installed ● Peerless security ● Non-disruptive updates ● Lifecycle options ● More automation BRIEF HISTORY OF RED HAT ENTERPRISE LINUX Not pictured: tens of thousands of incremental improvements Control Groups Mandatory access controls Secure Virtualization IBM Power Automated security Real-time kernel IBM Z Series RHEL is born. audits ‘02 ‘03 ‘05 ‘07 ‘10 ‘11 ‘12 ‘13 ‘15 Virtualization Containers Software-defined Cluster file Software-defined Networking systems storage FLEXIBILITY ACROSS DEPLOYMENT TARGETS via a Trusted, Consistent Host Environment RED HAT ENTERPRISE LINUX IS THE FOUNDATION RED HAT ENTERPRISE LINUX ROADMAP Red Hat CY2016 CY2017 Summit CY2018 CY2019 CY2020 2017 RHEL 7 RHEL ATOMIC HOST RHEL FOR REAL TIME .2 .3 .4 .5 .6.5 .7 RHEL FOR SAP APPLICATIONS RHEL FOR SAP HANA RHEL 6 RHEL FOR SAP APPLICATIONS .8 .9 .10 RHEL FOR SAP HANA RHEL 5 .11 SOFTWARE
    [Show full text]
  • Architecture of the Linux Kernel
    Architecture of the Linux kernel Gerion Entrup Felix Herrmann Sophie Matter Elias Entrup Matthias Jakob Jan Eberhardt Mathias Casselt March 21, 2018 Contents 1 Introduction 7 1.1 Overview of Linux components ................................... 7 1.2 License ................................................. 9 2 Process Management 11 2.1 Processes ............................................... 11 2.2 Process creation - Forking a process ................................ 13 2.3 Threads ................................................ 16 3 Scheduling in Linux 17 3.1 Scheduling-Classes .......................................... 17 3.2 Process Categories .......................................... 17 3.3 O(1)-Scheduler ............................................ 18 3.4 Priorities and Timeslices ....................................... 18 3.5 Completely Fair Scheduler ...................................... 19 3.5.1 Implementation details .................................... 20 3.6 Kernel Preemption .......................................... 21 4 Interrupts 23 4.1 Interrupt processing ......................................... 23 4.2 Interrupt entry ............................................ 23 4.3 Event handler ............................................. 24 4.3.1 Example: Generic Top Halve ................................ 24 4.3.2 Example: Handler ...................................... 24 4.4 /proc/interrupts ........................................... 25 4.5 Conclusion .............................................. 25 5 Bottom Halves 27 5.1
    [Show full text]
  • Slab Allocators in the Linux Kernel: SLAB, SLOB, SLUB
    Slab allocators in the Linux Kernel: SLAB, SLOB, SLUB Christoph Lameter, LinuxCon/Düsseldorf 2014 (Revision Oct 3, 2014) The Role of the Slab allocator in Linux • PAGE_SIZE (4k) basic allocation unit via page allocator. • Allows fractional allocation. Frequently needed for small objects that the kernel allocates f.e. for network descriptors. • Slab allocation is very performance sensitive. • Caching. • All other subsystems need the services of the slab allocators. • Terminology: SLAB is one of the slab allocator. • A SLAB could be a page frame or a slab cache as a whole. It's confusing. Yes. System Components around Slab Allocators kmalloc(size, flags) Device kfree(object) Page Drivers kzalloc(size, flags) Allocator kmem_cache_alloc(cahe, flags) kmem_cache_free(object) s Slab e kmalloc_node(size, flags, node) m File allocator a kmem_cache_alloc_node(cache, r F Systems flags, node) s e t c g e a j b P o l l a m S Memory Management User space code Slab allocators available • SLOB: K&R allocator (1991-1999) • SLAB: Solaris type allocator (1999-2008) • SLUB: Unqueued allocator (2008-today) • Design philosophies – SLOB: As compact as possible – SLAB: As cache friendly as possible. Benchmark friendly. – SLUB: Simple and instruction cost counts. Superior Debugging. Defragmentation. Execution time friendly. 1991 1991 Initial K&R allocator 1996 SLAB allocator development subsystem Slab line: Time 2000 2003 SLOB allocator 2004 NUMA SLAB 2007 SLUB allocator 2008 SLOB multilist 2010 2011 SLUB fastpath rework 2013 Common slab code 2014 2014 SLUBification of SLAB Maintainers • Manfred Spraul <SLAB Retired> • Matt Mackall <SLOB Retired> • Pekka Enberg • Christoph Lameter <SLUB, SLAB NUMA> • David Rientjes • Joonsoo Kim Contributors • Alokk N Kataria SLAB NUMA code • Shobhit Dayal SLAB NUMA architecture • Glauber Costa Cgroups support • Nick Piggin SLOB NUMA support and performance optimizations.
    [Show full text]
  • Linux.Kernel.And.Driver.Development
    Linux Kernel and Driver Development Training Linux Kernel and Driver Development Training Gr´egory Cl´ement,Michael Opdenacker, Free Electrons Maxime Ripard, S´ebastienJan, Thomas Petazzoni Embedded Linux Free Electrons Developers c Copyright 2004-2013, Free Electrons. Creative Commons BY-SA 3.0 license. Latest update: March 29, 2013. Document updates and sources: http://free-electrons.com/doc/training/linux-kernel Corrections, suggestions, contributions and translations are welcome! Free Electrons. Kernel, drivers and embedded Linux development, consulting, training and support. http://free-electrons.com 1/496 Rights to copy c Copyright 2004-2013, Free Electrons License: Creative Commons Attribution - Share Alike 3.0 http://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Free Electrons. Kernel, drivers and embedded Linux development, consulting, training and support. http://free-electrons.com 2/496 Electronic copies of these documents I Electronic copies of your particular version of the materials are available on: http://free-electrons.com/doc/training/linux-kernel I Open the corresponding documents and use them throughout the course to look for explanations given earlier by the instructor.
    [Show full text]
  • Software Fault Isolation with Api Integrity and Multi-Principal Modules
    Software Fault Isolation with Api Integrity and Multi-Principal Modules The MIT Faculty has made this article openly available. Please share how this access benefits you. Your story matters. Citation Yandong Mao, Haogang Chen, Dong Zhou, Xi Wang, Nickolai Zeldovich, and M. Frans Kaashoek. 2011. Software fault isolation with API integrity and multi-principal modules. In Proceedings of the Twenty-Third ACM Symposium on Operating Systems Principles (SOSP '11). ACM, New York, NY, USA, 115-128. As Published http://dx.doi.org/10.1145/2043556.2043568 Publisher Association for Computing Machinery (ACM) Version Author's final manuscript Citable link http://hdl.handle.net/1721.1/72580 Terms of Use Creative Commons Attribution-Noncommercial-Share Alike 3.0 Detailed Terms http://creativecommons.org/licenses/by-nc-sa/3.0/ Software fault isolation with API integrity and multi-principal modules Yandong Mao, Haogang Chen, Dong Zhou†, Xi Wang, Nickolai Zeldovich, and M. Frans Kaashoek MIT CSAIL, †Tsinghua University IIIS ABSTRACT complex, irregular kernel interfaces such as the ones found in the The security of many applications relies on the kernel being secure, Linux kernel and exploited by attackers. but history suggests that kernel vulnerabilities are routinely discov- Previous systems such as XFI [9] have used software isola- ered and exploited. In particular, exploitable vulnerabilities in kernel tion [26] to isolate kernel modules from the core kernel, thereby modules are common. This paper proposes LXFI, a system which protecting against a class of attacks on kernel modules. The chal- isolates kernel modules from the core kernel so that vulnerabilities lenge is that modules need to use support functions in the core in kernel modules cannot lead to a privilege escalation attack.
    [Show full text]
  • Ret2dir: Rethinking Kernel Isolation Vasileios P
    ret2dir: Rethinking Kernel Isolation Vasileios P. Kemerlis, Michalis Polychronakis, and Angelos D. Keromytis, Columbia University https://www.usenix.org/conference/usenixsecurity14/technical-sessions/presentation/kemerlis This paper is included in the Proceedings of the 23rd USENIX Security Symposium. August 20–22, 2014 • San Diego, CA ISBN 978-1-931971-15-7 Open access to the Proceedings of the 23rd USENIX Security Symposium is sponsored by USENIX ret2dir: Rethinking Kernel Isolation Vasileios P. Kemerlis Michalis Polychronakis Angelos D. Keromytis Columbia University {vpk, mikepo, angelos}@cs.columbia.edu Abstract equally attractive target. Continuing the increasing trend of the previous years, in 2013 there were 355 reported Return-to-user (ret2usr) attacks redirect corrupted kernel kernel vulnerabilities according to the National Vulnera- pointers to data residing in user space. In response, sev- bility Database, 140 more than in 2012 [73]. Admittedly, eral kernel-hardening approaches have been proposed to the exploitation of user-level software has become much enforce a more strict address space separation, by pre- harder, as recent versions of popular OSes come with nu- venting arbitrary control flow transfers and dereferences merous protections and exploit mitigations. The princi- from kernel to user space. Intel and ARM also recently ple of least privilege is better enforced in user accounts introduced hardware support for this purpose in the form and system services, compilers offer more protections of the SMEP, SMAP, and PXN processor features. Un- against common software flaws, and highly targeted ap- fortunately, although mechanisms like the above prevent plications, such as browsers and document viewers, have the explicit sharing of the virtual address space among started to employ sandboxing.
    [Show full text]