[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZlRseMV1HgI4zXNJ@infradead.org>
Date: Mon, 27 May 2024 04:20:24 -0700
From: Christoph Hellwig <hch@...radead.org>
To: "Sukrit.Bhatnagar@...y.com" <Sukrit.Bhatnagar@...y.com>
Cc: Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rafael@...nel.org>,
Christian Brauner <brauner@...nel.org>,
"Darrick J. Wong" <djwong@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-xfs@...r.kernel.org" <linux-xfs@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH 0/2] Improve dmesg output for swapfile+hibernation
On Mon, May 27, 2024 at 11:06:11AM +0000, Sukrit.Bhatnagar@...y.com wrote:
> We can pass the starting physical block offset of a swapfile into
> /sys/power/resume_offset, and hibernate can directly read/write
> into it using the swap extents information created by iomap during
> swapon. On resume, the kernel would read this offset value from
> the commandline parameters, and then access the swapfile.
Reading a physical address from userspace is not a proper interface.
What is this code even trying to do with it?
Powered by blists - more mailing lists