From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Nick Desaulniers <nick.desaulniers@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: dynamically allocate large struct in em_fxrstor
Date: Wed, 24 May 2017 16:19:57 +0200 [thread overview]
Message-ID: <20170524141957.GA8174@potion> (raw)
In-Reply-To: <20170524062433.20680-1-nick.desaulniers@gmail.com>
2017-05-23 23:24-0700, Nick Desaulniers:
> Fixes the warning:
>
> arch/x86/kvm/emulate.c:4018:12: warning: stack frame size of 1080 bytes in
> function
> 'em_fxrstor' [-Wframe-larger-than=]
> static int em_fxrstor(struct x86_emulate_ctxt *ctxt)
> ^
>
> Found with CONFIG_FRAME_WARN set to 1024.
>
> Signed-off-by: Nick Desaulniers <nick.desaulniers@gmail.com>
> ---
> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
> @@ -4017,30 +4017,38 @@ static int fxrstor_fixup(struct x86_emulate_ctxt *ctxt,
>
> static int em_fxrstor(struct x86_emulate_ctxt *ctxt)
> {
> - struct fxregs_state fx_state;
> + struct fxregs_state *fx_state;
> int rc;
>
> rc = check_fxsr(ctxt);
> if (rc != X86EMUL_CONTINUE)
> return rc;
>
> - rc = segmented_read_std(ctxt, ctxt->memop.addr.mem, &fx_state, 512);
> + fx_state = kmalloc(sizeof(*fx_state), GFP_KERNEL);
> + fx_state = kmalloc(sizeof(*fx_state), GFP_KERNEL);
fx_state must be 16 byte aligned and x86 ARCH_KMALLOC_MINALIGN is 8, so
this needs manual correction.
Also, please kmalloc also fxregs_state in fxrstor_fixup and em_fxsave so
we again have only one storage type.
> + if (!fx_state)
> + return -ENOMEM;
The caller does not understand -ENOMEM. The appropriate return value is
X86EMUL_UNHANDLEABLE.
> if (ctxt->mode < X86EMUL_MODE_PROT64)
> - rc = fxrstor_fixup(ctxt, &fx_state);
> + rc = fxrstor_fixup(ctxt, fx_state);
Ah, fxrstor_fixup most likely got inlined and both of them put ~512 byte
fxregs_state on the stack ... noinline attribute should solve the
warning too.
Thanks.
next prev parent reply other threads:[~2017-05-24 14:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 6:24 [PATCH] KVM: x86: dynamically allocate large struct in em_fxrstor Nick Desaulniers
2017-05-24 14:19 ` Radim Krčmář [this message]
2017-05-25 1:36 ` Nick Desaulniers
2017-05-25 14:07 ` Paolo Bonzini
2017-05-26 4:13 ` Nick Desaulniers
2017-05-26 7:18 ` Paolo Bonzini
2017-05-29 19:55 ` [PATCH v2] KVM: x86: avoid large stack allocations " Nick Desaulniers
2017-05-29 20:14 ` kbuild test robot
2017-05-29 20:29 ` Nick Desaulniers
2017-05-29 20:39 ` [PATCH v3] " Nick Desaulniers
2017-05-29 22:40 ` Nick Desaulniers
2017-05-29 22:48 ` [PATCH v4] " Nick Desaulniers
2017-05-30 10:15 ` Paolo Bonzini
2017-05-30 14:05 ` Radim Krčmář
2017-05-31 3:08 ` [PATCH v5] " Nick Desaulniers
2017-05-31 11:01 ` Paolo Bonzini
2017-06-01 1:05 ` Nick Desaulniers
2017-06-01 7:36 ` Paolo Bonzini
2017-06-02 2:10 ` Nick Desaulniers
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=20170524141957.GA8174@potion \
--to=rkrcmar@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nick.desaulniers@gmail.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).