All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: SF Markus Elfring <elfring@users.sourceforge.net>,
	kvm@vger.kernel.org, netdev@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	kernel-janitors@vger.kernel.org, Jason Wang <jasowang@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 2/2] vhost/scsi: Delete error messages for failed memory allocations in five functions
Date: Mon, 22 May 2017 15:38:33 +0300	[thread overview]
Message-ID: <20170522123833.asx2biaw4xaz4qpv@mwanda> (raw)
In-Reply-To: <20170522112320.GA22806@stefanha-x1.localdomain>

On Mon, May 22, 2017 at 12:23:20PM +0100, Stefan Hajnoczi wrote:
> I'm not sure if kmalloc() and friends guarantee to show
> a message (not just the first time, but for every failed allocation)?
>

It prints multiple times, but it's ratelimited.  It can also be disabled
using a config option.

See slab_out_of_memory().

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	netdev@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
	kernel-janitors@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	virtualization@lists.linux-foundation.org,
	SF Markus Elfring <elfring@users.sourceforge.net>
Subject: Re: [PATCH 2/2] vhost/scsi: Delete error messages for failed memory allocations in five functions
Date: Mon, 22 May 2017 15:38:33 +0300	[thread overview]
Message-ID: <20170522123833.asx2biaw4xaz4qpv@mwanda> (raw)
In-Reply-To: <20170522112320.GA22806@stefanha-x1.localdomain>

On Mon, May 22, 2017 at 12:23:20PM +0100, Stefan Hajnoczi wrote:
> I'm not sure if kmalloc() and friends guarantee to show
> a message (not just the first time, but for every failed allocation)?
>

It prints multiple times, but it's ratelimited.  It can also be disabled
using a config option.

See slab_out_of_memory().

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	netdev@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
	kernel-janitors@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	virtualization@lists.linux-foundation.org,
	SF Markus Elfring <elfring@users.sourceforge.net>
Subject: Re: [PATCH 2/2] vhost/scsi: Delete error messages for failed memory allocations in five functions
Date: Mon, 22 May 2017 12:38:33 +0000	[thread overview]
Message-ID: <20170522123833.asx2biaw4xaz4qpv@mwanda> (raw)
In-Reply-To: <20170522112320.GA22806@stefanha-x1.localdomain>

On Mon, May 22, 2017 at 12:23:20PM +0100, Stefan Hajnoczi wrote:
> I'm not sure if kmalloc() and friends guarantee to show
> a message (not just the first time, but for every failed allocation)?
>

It prints multiple times, but it's ratelimited.  It can also be disabled
using a config option.

See slab_out_of_memory().

regards,
dan carpenter


  parent reply	other threads:[~2017-05-22 12:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-20 14:30 [PATCH 0/2] vhost/scsi: Adjustments for five function implementations SF Markus Elfring
2017-05-20 14:30 ` SF Markus Elfring
2017-05-20 14:31 ` [PATCH 1/2] vhost/scsi: Improve a size determination in four functions SF Markus Elfring
2017-05-20 14:31   ` SF Markus Elfring
2017-05-22  9:37   ` Stefan Hajnoczi
2017-05-22  9:37     ` Stefan Hajnoczi
2017-05-22  9:37     ` Stefan Hajnoczi
2017-05-20 14:31 ` SF Markus Elfring
2017-05-20 14:32 ` [PATCH 2/2] vhost/scsi: Delete error messages for failed memory allocations in five functions SF Markus Elfring
2017-05-20 14:32   ` SF Markus Elfring
2017-05-22  9:43   ` Stefan Hajnoczi
2017-05-22  9:43     ` Stefan Hajnoczi
2017-05-22  9:43     ` Stefan Hajnoczi
2017-05-22 10:50     ` SF Markus Elfring
2017-05-22 10:50     ` SF Markus Elfring
2017-05-22 10:50       ` SF Markus Elfring
2017-05-22 11:23       ` Stefan Hajnoczi
2017-05-22 11:23       ` Stefan Hajnoczi
2017-05-22 11:23         ` Stefan Hajnoczi
2017-05-22 11:34         ` SF Markus Elfring
2017-05-22 11:34         ` SF Markus Elfring
2017-05-22 11:34           ` SF Markus Elfring
2017-05-22 14:09           ` Stefan Hajnoczi
2017-05-22 14:09           ` Stefan Hajnoczi
2017-05-22 14:09             ` Stefan Hajnoczi
2017-05-22 14:21             ` SF Markus Elfring
2017-05-22 14:21               ` SF Markus Elfring
2017-05-22 14:21               ` SF Markus Elfring
2017-05-22 12:38         ` Dan Carpenter [this message]
2017-05-22 12:38           ` [PATCH 2/2] " Dan Carpenter
2017-05-22 12:38           ` Dan Carpenter
2017-05-22 14:08           ` Stefan Hajnoczi
2017-05-22 14:08             ` Stefan Hajnoczi
2017-05-22 14:08             ` Stefan Hajnoczi
2017-05-20 14:32 ` SF Markus Elfring

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=20170522123833.asx2biaw4xaz4qpv@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=elfring@users.sourceforge.net \
    --cc=jasowang@redhat.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=stefanha@gmail.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=wsa@the-dreams.de \
    /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.