On Thu, 8 Apr 2021 14:39:09 +
"Luck, Tony" wrote:
> > I have one scenario, may you take into account:
> >
> > If one copyin case occurs, write() returned by your patch, the user process
> > may
> > check the return values, for errors, it may exit the process, then the
> > error page
> >
> I have one scenario, may you take into account:
>
> If one copyin case occurs, write() returned by your patch, the user process
> may
> check the return values, for errors, it may exit the process, then the error
> page
> will be freed, and then the page maybe alloced to other process or to
On Thu, 25 Mar 2021 17:02:31 -0700
Tony Luck wrote:
> Maybe this is the way forward? I made some poor choices before
> to treat poison consumption in the kernel when accessing user data
> (get_user() or copy_from_user()) ... in particular assuming that
> the right action was sending a SIGBUS to
Maybe this is the way forward? I made some poor choices before
to treat poison consumption in the kernel when accessing user data
(get_user() or copy_from_user()) ... in particular assuming that
the right action was sending a SIGBUS to the task as if it had
synchronously accessed the poison
4 matches
Mail list logo
