[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221011113511.1.I1cf52674cd85d07b300fe3fff3ad6ce830304bb6@changeid>
Date: Tue, 11 Oct 2022 11:36:31 -0700
From: pso@...omium.org
To: LKML <linux-kernel@...r.kernel.org>,
Linux-Fsdevel <linux-fsdevel@...r.kernel.org>
Cc: Kees Cook <keescook@...omium.org>,
Dmitry Torokhov <dtor@...omium.org>,
Paramjit Oberoi <psoberoi@...gle.com>,
Paramjit Oberoi <pso@...omium.org>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Tony Luck <tony.luck@...el.com>
Subject: [PATCH 1/1] pstore/ram: Ensure stable pmsg address with per-CPU ftrace buffers
From: Paramjit Oberoi <psoberoi@...gle.com>
When allocating ftrace pstore zones, there may be space left over at the
end of the region. The paddr pointer needs to be advanced to account for
this so that the next region (pmsg) ends up at the correct location.
Signed-off-by: Paramjit Oberoi <pso@...omium.org>
Reviewed-by: Dmitry Torokhov <dtor@...omium.org>
Signed-off-by: Paramjit Oberoi <psoberoi@...gle.com>
---
fs/pstore/ram.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
index fefe3d391d3af..3bca6cd34c02a 100644
--- a/fs/pstore/ram.c
+++ b/fs/pstore/ram.c
@@ -554,10 +554,12 @@ static int ramoops_init_przs(const char *name,
goto fail;
}
*paddr += zone_sz;
+ mem_sz -= zone_sz;
prz_ar[i]->type = pstore_name_to_type(name);
}
*przs = prz_ar;
+ *paddr += mem_sz;
return 0;
fail:
--
2.38.0.rc1.362.ged0d419d3c-goog
Powered by blists - more mailing lists