public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	kvm-devel <kvm@vger.kernel.org>,
	"Anthony N. Liguori [imap]" <aliguori@us.ibm.com>
Subject: Re: KVM overflows the stack
Date: Thu, 17 Jul 2008 09:42:17 +0300	[thread overview]
Message-ID: <487EE9C9.2050108@qumranet.com> (raw)
In-Reply-To: <1216275288.11664.13.camel@nimitz>

Dave Hansen wrote:
>   
>> switch (...) {
>>     case x: {
>>          struct medium a;
>>          ...
>>     }
>>     case y:
>>           struct medium b;
>>           ...
>>     }
>> };
>>
>> These could be solved either by stack allocation, or by moving into 
>> functions marked noinline.  Whichever is easier.
>>     
>
> Did you mean dynamic allocation? :)
>
>   

Yeah.  Too early in the morning for me.

Roland's trick might be easier than either, though.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2008-07-17  6:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 21:12 kvm causing memory corruption? ~2.6.25-rc6 Dave Hansen
2008-03-26  9:50 ` [kvm-devel] " Avi Kivity
2008-03-26 16:52   ` Dave Hansen
2008-03-26 16:58     ` Avi Kivity
2008-03-26 17:16       ` Dave Hansen
2008-03-27  9:36         ` Avi Kivity
2008-03-27 10:10           ` Avi Kivity
2008-03-27 14:55             ` Dave Hansen
2008-03-27 14:59               ` Avi Kivity
2008-03-27 16:30                 ` Dave Hansen
2008-06-02 22:30                 ` kvm causing memory corruption? now 2.6.26-rc4 Dave Hansen
2008-06-03  0:59                   ` Dave Hansen
2008-06-04 13:42                   ` Avi Kivity
2008-06-06  7:41                     ` Dave Hansen
2008-06-12 13:10                       ` Avi Kivity
2008-06-16 18:07                         ` Dave Hansen
2008-07-15 18:57                         ` kvm causing memory corruption? now 2.6.26-rc8 Dave Hansen
2008-07-16 21:44                           ` kvm causing memory corruption? now 2.6.26 Dave Hansen
2008-07-16 22:48                             ` KVM overflows the stack Dave Hansen
2008-07-17  5:52                               ` Avi Kivity
2008-07-17  6:08                                 ` Roland Dreier
2008-07-17 14:06                                   ` Dave Hansen
2008-07-17 14:15                                     ` Avi Kivity
2008-07-17  6:14                                 ` Dave Hansen
2008-07-17  6:42                                   ` Avi Kivity [this message]
2008-07-17  6:45                                 ` [PATCH] update kvm's anon_inodes.c for r/o bind mounts Dave Hansen
2008-07-19  7:33                                   ` Avi Kivity
2008-07-17  6:27                               ` KVM overflows the stack Dave Hansen
2008-07-17  5:38                             ` kvm causing memory corruption? now 2.6.26 Avi Kivity
2008-03-27 15:50           ` [kvm-devel] kvm causing memory corruption? ~2.6.25-rc6 Dave Hansen
2008-03-27 15:53             ` Avi Kivity
2008-03-27 16:30               ` Dave Hansen

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=487EE9C9.2050108@qumranet.com \
    --to=avi@qumranet.com \
    --cc=aliguori@us.ibm.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.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