All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: netdev@vger.kernel.org,
	Eugenio Perez Martin <eperezma@redhat.com>,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] vhost-vdpa: print error when vhost_vdpa_alloc_domain fails
Date: Wed, 1 Feb 2023 11:03:28 -0500	[thread overview]
Message-ID: <20230201110253-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJs=3_Bw5QiZRu-nSeprhT1AMyGqw4oggTY=t+yaPeXBOAOjLQ@mail.gmail.com>

On Wed, Feb 01, 2023 at 05:54:53PM +0200, Alvaro Karsz wrote:
> > I'm not sure this is a good idea. Userspace is not supposed to be
> > able to trigger dev_err.
> 
> dev_warn then?

dev_warn_once is ok.

-- 
MST

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: jasowang@redhat.com, virtualization@lists.linux-foundation.org,
	kvm@vger.kernel.org, netdev@vger.kernel.org,
	Eugenio Perez Martin <eperezma@redhat.com>
Subject: Re: [PATCH] vhost-vdpa: print error when vhost_vdpa_alloc_domain fails
Date: Wed, 1 Feb 2023 11:03:28 -0500	[thread overview]
Message-ID: <20230201110253-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJs=3_Bw5QiZRu-nSeprhT1AMyGqw4oggTY=t+yaPeXBOAOjLQ@mail.gmail.com>

On Wed, Feb 01, 2023 at 05:54:53PM +0200, Alvaro Karsz wrote:
> > I'm not sure this is a good idea. Userspace is not supposed to be
> > able to trigger dev_err.
> 
> dev_warn then?

dev_warn_once is ok.

-- 
MST


  reply	other threads:[~2023-02-01 16:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 15:20 [PATCH] vhost-vdpa: print error when vhost_vdpa_alloc_domain fails Alvaro Karsz
2023-02-01 15:20 ` Alvaro Karsz
2023-02-01 15:52 ` Michael S. Tsirkin
2023-02-01 15:52   ` Michael S. Tsirkin
2023-02-01 15:54   ` Alvaro Karsz
2023-02-01 15:54     ` Alvaro Karsz
2023-02-01 16:03     ` Michael S. Tsirkin [this message]
2023-02-01 16:03       ` Michael S. Tsirkin
2023-02-01 16:51       ` Alvaro Karsz
2023-02-01 16:51         ` Alvaro Karsz
2023-02-02  8:42 ` [PATCH v2] vhost-vdpa: print warning " Alvaro Karsz
2023-02-02  8:42   ` Alvaro Karsz
2023-02-02 19:01   ` Eugenio Perez Martin

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=20230201110253-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alvaro.karsz@solid-run.com \
    --cc=eperezma@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=netdev@vger.kernel.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.