From: Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Alexey Dobriyan
<adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 1/2] ppc vdso: make sure rc is defined
Date: Tue, 07 Jul 2009 15:47:39 -0500 [thread overview]
Message-ID: <m3my7gp6dw.fsf@pobox.com> (raw)
In-Reply-To: <20090706233425.GA3186-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> (Serge E. Hallyn's message of "Mon\, 6 Jul 2009 18\:34\:25 -0500")
"Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> writes:
> Signed-off-by: Serge Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> ---
> arch/powerpc/kernel/vdso.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/kernel/vdso.c b/arch/powerpc/kernel/vdso.c
> index 48beff6..679b394 100644
> --- a/arch/powerpc/kernel/vdso.c
> +++ b/arch/powerpc/kernel/vdso.c
> @@ -240,8 +240,10 @@ int arch_setup_additional_pages(struct linux_binprm *bprm,
> }
>
> /* for restart(2), double check that we got we asked for */
> - if (start && vdso_base != start)
> + if (start && vdso_base != start) {
> + rc = -EBUSY;
> goto fail_mmapsem;
> + }
>
> /*
> * our vma flags don't have VM_WRITE so by default, the process isn't
Is this why you sent this patch?
cc1: warnings being treated as errors
arch/powerpc/kernel/vdso.c: In function arch_setup_additional_pages:
arch/powerpc/kernel/vdso.c:194: error: rc may be used uninitialized in this function
If so, looks fine to me.
next prev parent reply other threads:[~2009-07-07 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 23:34 [PATCH 1/2] ppc vdso: make sure rc is defined Serge E. Hallyn
[not found] ` <20090706233425.GA3186-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-07 20:47 ` Nathan Lynch [this message]
[not found] ` <m3my7gp6dw.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-07-07 20:58 ` Serge E. Hallyn
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=m3my7gp6dw.fsf@pobox.com \
--to=ntl-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
--cc=adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
/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