From: Thomas Meyer <thomas@m3y3r.de>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: user-mode-linux-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH] um: userspace - be more verbose in ptrace set regs error
Date: Thu, 06 Jul 2017 00:06:38 +0200 [thread overview]
Message-ID: <1499292398.5422.1.camel@m3y3r.de> (raw)
In-Reply-To: <CAFLxGvyRDv0mBNm0bXpq+UKhgtaVq6yQoN-wkw51GYSZ1NG2EQ@mail.gmail.com>
Am Mittwoch, den 05.07.2017, 23:34 +0200 schrieb Richard Weinberger:
> Thomas,
>
> On Wed, May 24, 2017 at 12:45 AM, Thomas Meyer <thomas@m3y3r.de>
> wrote:
> > When ptrace fails to set GP/FP regs for the target process,
> > log the error before crashing the UML kernel.
> >
> > Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
> > ---
> > arch/um/os-Linux/skas/process.c | 10 ++++++++--
> > 1 file changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/um/os-Linux/skas/process.c b/arch/um/os-
> > Linux/skas/process.c
> > index 4530867..819d686 100644
> > --- a/arch/um/os-Linux/skas/process.c
> > +++ b/arch/um/os-Linux/skas/process.c
> > @@ -352,11 +352,17 @@ void userspace(struct uml_pt_regs *regs)
> > * fail. In this case, there is nothing to do but
> > * just kill the process.
> > */
> > - if (ptrace(PTRACE_SETREGS, pid, 0, regs->gp))
> > + if (ptrace(PTRACE_SETREGS, pid, 0, regs->gp)) {
> > + printk(UM_KERN_ERR "userspace - ptrace set
> > regs "
> > + "failed, errno = %d\n", errno);
> > fatal_sigsegv();
> > + }
> >
> > - if (put_fp_registers(pid, regs->fp))
> > + if (put_fp_registers(pid, regs->fp)) {
> > + printk(UM_KERN_ERR "userspace - ptrace set
> > fp regs "
> > + "failed, errno = %d\n", errno);
> > fatal_sigsegv();
> > + }
> >
> > /* Now we set local_using_sysemu to be used for one
> > loop */
> > local_using_sysemu = get_using_sysemu();
> >
> > -----------------------------------------------------------------
> > -------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > User-mode-linux-devel mailing list
> > User-mode-linux-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
>
> This patch is also malformed. :-(
I wonder why evolution is messing up my emails...
will check and resend...
sorry and kind regards
thomas
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2017-07-05 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 22:45 [uml-devel] [PATCH] um: userspace - be more verbose in ptrace set regs error Thomas Meyer
2017-07-05 21:34 ` Richard Weinberger
2017-07-05 22:06 ` Thomas Meyer [this message]
2017-07-05 22:09 ` Richard Weinberger
-- strict thread matches above, loose matches on Subject: below --
2017-07-05 22:31 Thomas Meyer
2017-07-07 9:06 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1499292398.5422.1.camel@m3y3r.de \
--to=thomas@m3y3r.de \
--cc=richard.weinberger@gmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox