OK, I fixed the strcpy to/from user code, in the same branch. For uaccess.h in RISCV, what do we want to do? I don't know it well enough, I don't have anything to build and test, and the only Linux thing on it, is an off-tree stepchild.
On Mon, Nov 9, 2015 at 4:53 PM, Davide Libenzi <[email protected]> wrote: > Let me know if I can go ahead and fix both the uaccess stub and strcpy > code. > > > On Mon, Nov 9, 2015 at 3:45 PM, Davide Libenzi <[email protected]> > wrote: > >> On Mon, Nov 9, 2015 at 3:41 PM, Davide Libenzi <[email protected]> >> wrote: >> >>> More importantly, what happens if the user picks an address close to the >>>> border of the an area where it does not have access, but the string goes >>>> into that area. For instance, in copy_to_user, I think the user could >>>> pick UWLIM - 1, then trick the kernel into writing above that into >>>> memory that is read-only. >>>> >>> >>> The code assume that there is one (at least) separation page between >>> user and kernel VMAs. >>> Should have made it more clear. >>> >> >> Never mind, sorry, that needs fixing. >> >> > -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
