[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YoTmGREvHTpTeeUH@lunn.ch>
Date: Wed, 18 May 2022 14:27:05 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Vivek Kumar <quic_vivekuma@...cinc.com>
Cc: corbet@....net, catalin.marinas@....com, will@...nel.org,
tglx@...utronix.de, maz@...nel.org, axboe@...nel.dk,
rafael@...nel.org, akpm@...ux-foundation.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-block@...r.kernel.org,
linux-pm@...r.kernel.org, linux-mm@...ck.org, len.brown@...el.com,
pavel@....cz, paulmck@...nel.org, bp@...e.de,
keescook@...omium.org, songmuchun@...edance.com,
rdunlap@...radead.org, damien.lemoal@...nsource.wdc.com,
pasha.tatashin@...een.com, tabba@...gle.com, ardb@...nel.org,
tsoni@...cinc.com, quic_psodagud@...cinc.com,
quic_svaddagi@...cinc.com,
Prasanna Kumar <quic_kprasan@...cinc.com>
Subject: Re: [RFC 4/6] mm: swap: Add randomization check for swapon/off calls
On Wed, May 18, 2022 at 01:18:39PM +0530, Vivek Kumar wrote:
> Add addtional check on swapon/swapoff sycalls to disable
> randomization of swap offsets if GENHD_FL_NO_RANDOMIZE
> flag is passed.
Is there already a flag in the image header which tells you if the
image is randomozied or not? I assume the bootloader needs to know,
doing a linear read of a randomized image is not going to end well.
Andrew
Powered by blists - more mailing lists