[v2,0/5] Support kexec_file on 32-bit RISC-V

Message ID	20220624044811.9682-1-palmer@rivosinc.com (mailing list archive)
Headers	show Return-Path: <linux-security-module-owner@kernel.org> Subject: [PATCH v2 0/5] Support kexec_file on 32-bit RISC-V Date: Thu, 23 Jun 2022 21:48:06 -0700 Message-Id: <20220624044811.9682-1-palmer@rivosinc.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org From: Palmer Dabbelt <palmer@rivosinc.com> To: zohar@linux.ibm.com, dmitry.kasatkin@gmail.com, linux-integrity@vger.kernel.org Precedence: bulk
Series	Support kexec_file on 32-bit RISC-V \| expand [v2,0/5] Support kexec_file on 32-bit RISC-V [v2,1/5] drivers: of: kexec ima: Support 32-bit platforms [v2,2/5] ima: Fix a build issue on 32-bit platforms [v2,3/5] RISC-V: kexec: Use Elf64 on 64-bit targets [v2,4/5] RISC-V: purgatory: Use XLEN-length loads to support rv32 [v2,5/5] RISC-V: Allow kexec_file() on 32-bit platforms

Message ID

20220624044811.9682-1-palmer@rivosinc.com (mailing list archive)

Headers

Subject: [PATCH v2 0/5] Support kexec_file on 32-bit RISC-V
Date: Thu, 23 Jun 2022 21:48:06 -0700
Message-Id: <20220624044811.9682-1-palmer@rivosinc.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
            linux-security-module@vger.kernel.org
From: Palmer Dabbelt <palmer@rivosinc.com>
To: zohar@linux.ibm.com, dmitry.kasatkin@gmail.com,
        linux-integrity@vger.kernel.org
Precedence: bulk

Series

Support kexec_file on 32-bit RISC-V | expand

Message

Palmer Dabbelt June 24, 2022, 4:48 a.m. UTC

This rolled itself back to the top of my inbox, so I figured I'd send it
again as Rob's review landed.  IMO the security/integrity/ima/ change is
sufficiently trivial that it's fine to take it through the RISC-V tree
but I don't have an Review/Ack so I'll wait until this loops back again
to give the security/integrity/ folks a chance to chime in.

If this loops back to the top of my queue (which looks about a month
deep right now) without any comments then I'll put it in riscv/for-next.

Thanks!

Changes since v1
<https://lore.kernel.org/all/20220520154430.18593-1-palmer@rivosinc.com/>
* Collected reviews for drivers/of/kexec.c.

Comments

Mimi Zohar June 30, 2022, 1:21 p.m. UTC | #1

Hi Palmer,

On Thu, 2022-06-23 at 21:48 -0700, Palmer Dabbelt wrote:
> This rolled itself back to the top of my inbox, so I figured I'd send it
> again as Rob's review landed.  IMO the security/integrity/ima/ change is
> sufficiently trivial that it's fine to take it through the RISC-V tree
> but I don't have an Review/Ack so I'll wait until this loops back again
> to give the security/integrity/ folks a chance to chime in.
> 
> If this loops back to the top of my queue (which looks about a month
> deep right now) without any comments then I'll put it in riscv/for-next.
> 
> Thanks!
> 
> Changes since v1
> <https://lore.kernel.org/all/20220520154430.18593-1-palmer@rivosinc.com/>
> * Collected reviews for drivers/of/kexec.c.

Maybe better that you upstream the RISC-V changes.  So far there aren't
any merge conflicts with this patchset, but a number of other kexec
patch sets will hopefully be upstreamed in the coming open window.  I'd
appreciate if you could create a topic branch for the first two
patches.

thanks,

Mimi