linux-kernel - Re: [mm 4.15-rc8] Random oopses under memory pressure.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180120052432.GN13338@ZenIV.linux.org.uk>
Date:   Sat, 20 Jan 2018 05:24:32 +0000
From:   Al Viro <viro@...IV.linux.org.uk>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Matthew Wilcox <willy@...radead.org>,
        "Kirill A. Shutemov" <kirill@...temov.name>,
        Peter Zijlstra <peterz@...radead.org>,
        Andrea Arcangeli <aarcange@...hat.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
        "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Johannes Weiner <hannes@...xchg.org>,
        Joonsoo Kim <iamjoonsoo.kim@....com>,
        Mel Gorman <mgorman@...hsingularity.net>,
        Tony Luck <tony.luck@...el.com>,
        Vlastimil Babka <vbabka@...e.cz>,
        Michal Hocko <mhocko@...nel.org>,
        "hillf.zj" <hillf.zj@...baba-inc.com>,
        Hugh Dickins <hughd@...gle.com>,
        Oleg Nesterov <oleg@...hat.com>,
        Rik van Riel <riel@...hat.com>,
        Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
        Vladimir Davydov <vdavydov.dev@...il.com>,
        Ingo Molnar <mingo@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-mm <linux-mm@...ck.org>,
        the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [mm 4.15-rc8] Random oopses under memory pressure.

On Sat, Jan 20, 2018 at 02:02:37AM +0000, Al Viro wrote:

> Note that those sizes are rather sensitive to lockdep, spinlock debugging, etc.

That they certainly are: on one of the testing .config I'm using it gave this:
   1104 sizeof struct page = 56
     81 sizeof struct cpufreq_frequency_table = 12
     32 sizeof struct Indirect = 24
      7 sizeof struct zone = 1400
      7 sizeof struct hstate = 152
      6 sizeof struct lock_class = 336
      6 sizeof struct hpet_dev = 152
      6 sizeof struct ext4_extent = 12
      4 sizeof struct ext4_extent_idx = 12
      3 sizeof struct mbox_chan = 456
      2 sizeof struct strip_zone = 24
      2 sizeof struct kobj_attribute = 48
      2 sizeof struct kernel_param = 40
      2 sizeof struct exception_table_entry = 12
      1 sizeof struct vif_device = 104
      1 sizeof struct unixware_slice = 12
      1 sizeof struct svc_pool = 152
      1 sizeof struct srcu_node = 152
      1 sizeof struct r5worker_group = 56
      1 sizeof struct pebs_record_core = 144
      1 sizeof struct netdev_queue = 384
      1 sizeof struct mirror = 40
      1 sizeof struct mif_device = 56
      1 sizeof struct e1000_tx_ring = 48
      1 sizeof struct dx_frame = 24
      1 sizeof struct bts_record = 24
      1 sizeof struct ata_device = 2560
      1 sizeof struct acpi_processor_cx = 52