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  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]
Date:   Sun, 5 Jan 2020 10:47:35 -0500
From:   Sasha Levin <>
To:     Pavel Machek <>
Cc:     Greg Kroah-Hartman <>,,,
        Johannes Weiner <>,
        Chris Down <>,
        Vlastimil Babka <>,
        David Hildenbrand <>,
        Michal Hocko <>,
        Alexey Dobriyan <>,
        Andrew Morton <>,
        Linus Torvalds <>
Subject: Re: [PATCH 4.19 071/114] kernel: sysctl: make drop_caches write-only

On Fri, Jan 03, 2020 at 07:29:11PM +0100, Pavel Machek wrote:
>> From: Johannes Weiner <>
>> [ Upstream commit 204cb79ad42f015312a5bbd7012d09c93d9b46fb ]
>> Currently, the drop_caches proc file and sysctl read back the last value
>> written, suggesting this is somehow a stateful setting instead of a
>> one-time command.  Make it write-only, like e.g.  compact_memory.
>I have no problem with that, but is it good idea for stable?

Usually I'd drop it, yes. In this case it seems like it made "real"
users interact with the switch incorrectly, which I parse as a bug.

>Plus, I seem to recall that drop_caches was somehow dangerous,
>debugging-only stuff, one should not use on production system. Did
>that get fixed in the meantime?

Sounds like it's being used in production, at scale, so I'd hope so :)


Powered by blists - more mailing lists