mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Minfei Huang <mnghuan@gmail.com>
Cc: mst@redhat.com, Minfei Huang <minfei.hmf@alibaba-inc.com>,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio: Return correct errno for function init_vq's failure
Date: Wed, 13 Jul 2016 14:05:40 +0200	[thread overview]
Message-ID: <20160713140540.78c9ab01.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20160713115400.GA16403@MinfeideMacBook-Pro.local>

On Wed, 13 Jul 2016 19:54:00 +0800
Minfei Huang <mnghuan@gmail.com> wrote:

> On 07/06/16 at 11:18P, Cornelia Huck wrote:
> > On Mon, 27 Jun 2016 10:09:18 +0800
> > Minfei Huang <mnghuan@gmail.com> wrote:
> > 
> > > The error number -ENOENT or 0 will be returned, if we can not allocate
> > > more memory in function init_vq. If host can support multiple virtual
> > > queues, and we fails to allocate necessary memory structures for vq,
> > > kernel may crash due to incorrect returning.
> > > 
> > > To fix it, kernel will return correct value in init_vq.
> > The error handling in this function looks horrible.
> > 
> > When mq was introduced, init_vq started mixing up several things:
> > - The mq feature is not available - which is not an error, and
> > therefore should not have any influence on the return code.
> > - One of the several memory allocations failed - only ->vqs gets
> > special treatment, however.
> > - The ->find_vqs callback failed.
> 
> Yep. And without this patch, it is silent for boot failure. I think it
> makes sense to let user notify about this failure.

Agreed.

> 
> > 
> > Your patch fixes the code, but it is still very convoluted due to the
> > temporary arrays.
> > 
> > May it be worthwile to introduce a helper for setting up the virtqueues
> > where all virtqueues are essentially the same and just get a
> > consecutive number? Michael?
> > 
> 
> Hmm, How about refactor this function to make it more readable, since we
> do a lot of work in it.
> 
> I will post an update to refactor this function.

Anything to make this more readable probably helps :)

      reply	other threads:[~2016-07-13 12:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27  2:09 Minfei Huang
2016-07-06  9:18 ` Cornelia Huck
2016-07-13 11:54   ` Minfei Huang
2016-07-13 12:05     ` Cornelia Huck [this message]

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=20160713140540.78c9ab01.cornelia.huck@de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minfei.hmf@alibaba-inc.com \
    --cc=mnghuan@gmail.com \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.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

Powered by JetHome