All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: KVM list <kvm@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PULL] vhost: cleanups and fixes
Date: Tue, 12 Jun 2018 04:36:54 +0300	[thread overview]
Message-ID: <20180612042600-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CA+55aFz4uBHaWnBarVUEG90s2ucyVtoLmwYpYVwDV+XQESNRqw@mail.gmail.com>

On Mon, Jun 11, 2018 at 11:44:05AM -0700, Linus Torvalds wrote:
> On Mon, Jun 11, 2018 at 11:32 AM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > So now we apparently do a GFP_KERNEL allocation insider the mm zone
> > lock, which is broken on just _so_ many levels.
> 
> Oh, I see the comment about how it doesn't actually do an allocation
> at all because it's a single-entry.
> 
> Still too damn ugly to live, and much too fragile. No way in hell do
> we even _hint_ at a GFP_KERNEL when we're inside a context that can't
> do any memory allocation at all.
> 
> Plus I'm not convinced it's a "no allocation" path even despite that
> comment, because it also does a "dma_map_page()" etc, which can cause
> allocations to do the dma mapping thing afaik. No?

Well no because DMA is triggered by the IOMMU flag and
that is always off for the balloon. But I hear what you
are saying about it being fragile.

> Maybe there's some reason why that doesn't happen either, but
> basically this whole callchain looks *way* to complicated to be used
> under a core VM spinlock.
> 
>                 Linus

Maybe it will help to have GFP_NONE which will make any allocation
fail if attempted. Linus, would this address your comment?
-- 
MST

WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: KVM list <kvm@vger.kernel.org>,
	virtualization <virtualization@lists.linux-foundation.org>,
	Network Development <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	wei.w.wang@intel.com
Subject: Re: [PULL] vhost: cleanups and fixes
Date: Tue, 12 Jun 2018 04:36:54 +0300	[thread overview]
Message-ID: <20180612042600-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CA+55aFz4uBHaWnBarVUEG90s2ucyVtoLmwYpYVwDV+XQESNRqw@mail.gmail.com>

On Mon, Jun 11, 2018 at 11:44:05AM -0700, Linus Torvalds wrote:
> On Mon, Jun 11, 2018 at 11:32 AM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > So now we apparently do a GFP_KERNEL allocation insider the mm zone
> > lock, which is broken on just _so_ many levels.
> 
> Oh, I see the comment about how it doesn't actually do an allocation
> at all because it's a single-entry.
> 
> Still too damn ugly to live, and much too fragile. No way in hell do
> we even _hint_ at a GFP_KERNEL when we're inside a context that can't
> do any memory allocation at all.
> 
> Plus I'm not convinced it's a "no allocation" path even despite that
> comment, because it also does a "dma_map_page()" etc, which can cause
> allocations to do the dma mapping thing afaik. No?

Well no because DMA is triggered by the IOMMU flag and
that is always off for the balloon. But I hear what you
are saying about it being fragile.

> Maybe there's some reason why that doesn't happen either, but
> basically this whole callchain looks *way* to complicated to be used
> under a core VM spinlock.
> 
>                 Linus

Maybe it will help to have GFP_NONE which will make any allocation
fail if attempted. Linus, would this address your comment?
-- 
MST

  reply	other threads:[~2018-06-12  1:36 UTC|newest]

Thread overview: 125+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11 16:23 [PULL] vhost: cleanups and fixes Michael S. Tsirkin
2018-06-11 16:23 ` Michael S. Tsirkin
2018-06-11 18:32 ` Linus Torvalds
2018-06-11 18:32   ` Linus Torvalds
2018-06-11 18:44   ` Linus Torvalds
2018-06-11 18:44     ` Linus Torvalds
2018-06-12  1:36     ` Michael S. Tsirkin [this message]
2018-06-12  1:36       ` Michael S. Tsirkin
2018-06-12  1:59       ` Linus Torvalds
2018-06-12  1:59         ` Linus Torvalds
2018-06-12 11:05         ` Wei Wang
2018-06-12 11:05           ` Wei Wang
2018-06-14 15:01           ` Nitesh Narayan Lal
2018-06-15  3:53             ` Wei Wang
2018-06-15  3:53               ` Wei Wang
2018-06-12  1:57   ` Michael S. Tsirkin
2018-06-12  1:57     ` Michael S. Tsirkin
  -- strict thread matches above, loose matches on Subject: below --
2020-02-10  6:02 Michael S. Tsirkin
2020-02-11  2:07 ` Linus Torvalds
2020-02-11  2:07   ` Linus Torvalds
2020-02-07  7:39 Michael S. Tsirkin
2019-10-28  8:29 Michael S. Tsirkin
2019-10-15 21:19 Michael S. Tsirkin
2019-10-15 22:25 ` pr-tracker-bot
2019-10-15 22:25 ` pr-tracker-bot
2019-10-15 21:19 Michael S. Tsirkin
2019-06-03 14:30 Michael S. Tsirkin
2019-05-14 21:11 Michael S. Tsirkin
2019-05-14 21:11 Michael S. Tsirkin
2019-05-14 21:20 ` pr-tracker-bot
2019-05-14 21:20 ` pr-tracker-bot
2018-11-01 21:19 Michael S. Tsirkin
2018-11-01 21:19 ` Michael S. Tsirkin
2018-11-01 21:19 ` Michael S. Tsirkin
2018-11-01 21:44 ` Linus Torvalds
2018-11-01 21:44 ` Linus Torvalds
2018-11-01 23:00 ` Kees Cook
2018-11-01 23:00 ` Kees Cook
2018-11-01 23:00   ` Kees Cook
2018-11-01 23:06   ` Linus Torvalds
2018-11-01 23:55     ` Michael S. Tsirkin
2018-11-01 23:55     ` Michael S. Tsirkin
2018-11-02 11:46     ` Mark Rutland
2018-11-02 13:04       ` Michael S. Tsirkin
2018-11-02 16:14         ` Linus Torvalds
2018-11-02 16:59           ` Michael S. Tsirkin
2018-11-02 16:59           ` Michael S. Tsirkin
2018-11-02 17:10             ` Linus Torvalds
2018-11-02 17:10               ` Linus Torvalds
2018-11-02 17:15               ` Linus Torvalds
2018-11-02 17:15               ` Linus Torvalds
2018-11-02 19:01                 ` Al Viro
2018-11-02 19:01                 ` Al Viro
2018-11-02 17:21               ` Michael S. Tsirkin
2018-11-02 18:02                 ` Linus Torvalds
2018-11-02 18:02                 ` Linus Torvalds
2018-11-02 18:12                   ` Michael S. Tsirkin
2018-11-02 18:12                   ` Michael S. Tsirkin
2018-11-02 17:21               ` Michael S. Tsirkin
2018-11-02 16:14         ` Linus Torvalds
2018-11-02 13:04       ` Michael S. Tsirkin
2018-11-02 11:46     ` Mark Rutland
2018-11-30 13:44     ` Michael S. Tsirkin
2018-11-30 13:44       ` Michael S. Tsirkin
2018-11-30 19:01       ` Bijan Mottahedeh
2018-11-30 19:55         ` Michael S. Tsirkin
2018-11-30 19:55         ` Michael S. Tsirkin
2018-11-01 23:06   ` Linus Torvalds
2018-11-01 23:38   ` Michael S. Tsirkin
2018-11-01 23:38     ` Michael S. Tsirkin
2017-12-08 15:47 Michael S. Tsirkin
2017-12-08 15:47 Michael S. Tsirkin
2017-12-04 13:25 Michael S. Tsirkin
2017-08-25 18:47 Michael S. Tsirkin
2017-04-10 21:36 Michael S. Tsirkin
2017-04-10 21:36 ` Michael S. Tsirkin
2017-03-02  5:49 Michael S. Tsirkin
2017-03-02  5:49 ` Michael S. Tsirkin
2017-02-03 21:43 Michael S. Tsirkin
2017-02-03 21:43 ` Michael S. Tsirkin
2017-01-23 15:05 Michael S. Tsirkin
2017-01-23 15:05 ` Michael S. Tsirkin
2017-01-23 21:50 ` Linus Torvalds
2017-01-24  2:45   ` Michael S. Tsirkin
2017-01-24  2:45     ` Michael S. Tsirkin
2017-01-23 21:50 ` Linus Torvalds
2016-05-24 11:57 Michael S. Tsirkin
2016-05-24 11:57 ` Michael S. Tsirkin
2015-12-21  7:58 Michael S. Tsirkin
2015-12-21  7:58 ` Michael S. Tsirkin
2015-12-07 17:07 Michael S. Tsirkin
2015-09-18 10:42 Michael S. Tsirkin
2015-09-18 10:42 Michael S. Tsirkin
2015-09-09  9:15 Michael S. Tsirkin
2015-09-09  9:15 Michael S. Tsirkin
2015-07-28 10:00 Michael S. Tsirkin
2015-07-15 10:50 Michael S. Tsirkin
2015-07-15 10:50 ` Michael S. Tsirkin
2015-07-15 11:26 ` Michael S. Tsirkin
2015-07-15 11:26   ` Michael S. Tsirkin
2015-06-01 19:18 Michael S. Tsirkin
2015-06-01 19:45 ` Michael S. Tsirkin
2015-06-01 19:45   ` Michael S. Tsirkin
2015-06-01 19:18 Michael S. Tsirkin
2015-01-08  7:51 Michael S. Tsirkin
2015-01-01 12:26 Michael S. Tsirkin
2015-01-01 12:26 Michael S. Tsirkin
2014-12-18 10:46 Michael S. Tsirkin
2014-12-18 10:46 ` Michael S. Tsirkin
2014-11-13 21:22 Michael S. Tsirkin
2014-11-13 21:22 ` Michael S. Tsirkin
2014-06-25 11:05 Michael S. Tsirkin
2014-06-25 11:05 ` Michael S. Tsirkin
2013-07-15 18:31 Michael S. Tsirkin
2013-07-15 18:31 ` Michael S. Tsirkin
2013-07-22  8:07 ` Michael S. Tsirkin
2013-07-22  8:07   ` Michael S. Tsirkin
2013-07-08 11:45 Michael S. Tsirkin
2013-07-08 11:45 ` Michael S. Tsirkin
2013-05-02 10:53 Michael S. Tsirkin
2013-05-02 10:53 ` Michael S. Tsirkin
2013-05-02 18:55 ` Nicholas A. Bellinger
2013-05-02 19:33   ` Michael S. Tsirkin
2013-05-02 19:49     ` Linus Torvalds
2013-06-05 15:53       ` Michael S. Tsirkin

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=20180612042600-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.