lib: sbi: Add additional range checks for RV32
PATCH 1/1 lib: sbi: Add additional range checks for RV32
On RV32, M-mode can only access the first 4G of the physical address space because M-mode does not have an MMU to access the full 34-bit physical address space. While we already ensure the "hi" registers of RV32 physical address inputs are zero we need to also ensure that the low register plus the size does not cross into 4G address space. The check added to sbi_domain_check_addr_range() should be enough for both DBCN and SSE, but DBCN returns a different error code for high addresses, so we patch that check too.
---
Should the SSE functions return SBI_ERR_FAILED in this case like DBCN does? We'd need to patch the SSE spec to call out SBI_ERR_FAILED as "Failed to write due to I/O errors." like DBCN does too.
lib/sbi/sbi_domain.c | 3 +++ lib/sbi/sbi_ecall_dbcn.c | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-)
lib/sbi/sbi_domain.c +3 -0
@@ -412,6 +412,9 @@ bool sbi_domain_check_addr_range(const struct sbi_domain *dom,if (!dom)return false; +if (max < addr) +return false; +while (addr < max) { reg =find_region (dom, addr);if (!reg)
lib/sbi/sbi_ecall_dbcn.c +1 -1
@@ -39,7 +39,7 @@ static int sbi_ecall_dbcn_handler(unsigned long extid, unsigned long funcid,* physical address (i.e. a2 register) is non-zero on * RV64. */ -if (regs->a2) +if (regs->a2 || regs->a1 + regs->a0 < regs->a1)return SBI_ERR_FAILED ; if (!sbi_domain_check_addr_range(sbi_domain_thishart_ptr(),
Signature · 1 line
2.45.2
PATCH 1/1 lib: sbi: Add additional range checks for RV32
Quoted 11 lines · On Wed, Aug 14, 2024 at 6:02?PM Andrew Jones <[email protected]> wrote:
On RV32, M-mode can only access the first 4G of the physical address space because M-mode does not have an MMU to access the full 34-bit physical address space. While we already ensure the "hi" registers of RV32 physical address inputs are zero we need to also ensure that the low register plus the size does not cross into 4G address space. The check added to
sbi_domain_check_addr_range()should be enough for both DBCN and SSE, but DBCN returns a different error code for high addresses, so we patch that check too.
Quoted 7 lines
Signed-off-by Andrew Jones <[email protected]>---
Should the SSE functions return
SBI_ERR_FAILEDin this case like DBCN does? We'd need to patch the SSE spec to call outSBI_ERR_FAILEDas "Failed to write due to I/O errors." like DBCN does too.
Instead of special-casing wrap-around check separately for each SBI extension, I suggest:
1) Add one more requirement in section 3.2 of the SBI spec to prevent wrap-around
2) Update sbi_domain_check_addr_range() like this patch does.
Regards,
Anup
Quoted 40 lines
lib/sbi/sbi_domain.c | 3 +++ lib/sbi/sbi_ecall_dbcn.c | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-)lib/sbi/sbi_domain.c +3
-0@@ -412,6 +412,9 @@ bool sbi_domain_check_addr_range(const struct sbi_domain *dom,if (!dom)return false; +if (max < addr) +return false; +while (addr < max) { reg =find_region (dom, addr);if (!reg)lib/sbi/sbi_ecall_dbcn.c +1
-2@@ -39,7 +39,7 @@ static int sbi_ecall_dbcn_handler(unsigned long extid, unsigned long funcid,* physical address (i.e. a2 register) is non-zero on * RV64. */ -if (regs->a2) +if (regs->a2 || regs->a1 + regs->a0 < regs->a1)return SBI_ERR_FAILED ; if (!sbi_domain_check_addr_range(sbi_domain_thishart_ptr(), --2.45.2
--
opensbi mailing list
opensbi at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
PATCH 1/1 lib: sbi: Add additional range checks for RV32
Quoted 20 lines · Anup Patel
Quoted 11 lines · On Wed, Aug 14, 2024 at 6:02?PM Andrew Jones <[email protected]> wrote:
On RV32, M-mode can only access the first 4G of the physical address space because M-mode does not have an MMU to access the full 34-bit physical address space. While we already ensure the "hi" registers of RV32 physical address inputs are zero we need to also ensure that the low register plus the size does not cross into 4G address space. The check added to
sbi_domain_check_addr_range()should be enough for both DBCN and SSE, but DBCN returns a different error code for high addresses, so we patch that check too.Quoted 7 lines
Signed-off-by Andrew Jones <[email protected]>---
Should the SSE functions return
SBI_ERR_FAILEDin this case like DBCN does? We'd need to patch the SSE spec to call outSBI_ERR_FAILEDas "Failed to write due to I/O errors." like DBCN does too.
Quoted 5 lines
Instead of special-casing wrap-around check separately for each SBI extension, I suggest:
1) Add one more requirement in section 3.2 of the SBI spec to prevent wrap-around
2) Updatesbi_domain_check_addr_range()like this patch does.
Sounds good to me.
Thanks,
drew
PATCH 1/1 lib: sbi: Add additional range checks for RV32
Quoted 21 lines · Andrew Jones
Quoted 20 lines · Anup Patel
Quoted 18 lines · On Wed, Aug 14, 2024 at 6:02?PM Andrew Jones <[email protected]> wrote:
On RV32, M-mode can only access the first 4G of the physical address space because M-mode does not have an MMU to access the full 34-bit physical address space. While we already ensure the "hi" registers of RV32 physical address inputs are zero we need to also ensure that the low register plus the size does not cross into 4G address space. The check added to
sbi_domain_check_addr_range()should be enough for both DBCN and SSE, but DBCN returns a different error code for high addresses, so we patch that check too.Signed-off-by Andrew Jones <[email protected]>---
Should the SSE functions return
SBI_ERR_FAILEDin this case like DBCN does? We'd need to patch the SSE spec to call outSBI_ERR_FAILEDas "Failed to write due to I/O errors." like DBCN does too.
Quoted 8 lines
Quoted 5 lines
Instead of special-casing wrap-around check separately for each SBI extension, I suggest:
1) Add one more requirement in section 3.2 of the SBI spec to prevent wrap-around
2) Updatesbi_domain_check_addr_range()like this patch does.Sounds good to me.
I've created https://github.com/riscv-non-isa/riscv-sbi-doc/pull/164 for the spec side of things. For v2 of this patch I think it's best to change sbi_domain_check_addr_range() to return an error rather than a boolean and then for cases like hi != 0 and lo + size > max-lo we can return errors other than SBI_ERR_INVALID_ADDR without having to duplicate checks which are currently outside the function.
Thanks,
drew