mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: "Eugenio Pérez" <eperezma@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>
Cc: Yongji Xie <xieyongji@bytedance.com>, Cindy Lu <lulu@redhat.com>,
	jasowang@redhat.com, linux-kernel@vger.kernel.org,
	Maxime Coquelin <mcoqueli@redhat.com>,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
	Laurent Vivier <lvivier@redhat.com>,
	virtualization@lists.linux.dev,
	Stefano Garzarella <sgarzare@redhat.com>,
	Linux kernel regressions list <regressions@lists.linux.dev>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH v4 1/6] vduse: make domain_lock an rwlock
Date: Sat, 27 Sep 2025 08:27:22 +0200	[thread overview]
Message-ID: <3e5abb75-2192-46dc-a44e-d66fed87fc63@leemhuis.info> (raw)
In-Reply-To: <20250925091335.1964283-2-eperezma@redhat.com>

On 25.09.25 11:13, Eugenio Pérez wrote:
> It will be used in a few more scenarios read-only so make it more
> scalable.
> [...]
> diff --git a/drivers/vdpa/vdpa_user/vduse_dev.c b/drivers/vdpa/vdpa_user/vduse_dev.c
> index e7bced0b5542..2b6a8958ffe0 100644
> --- a/drivers/vdpa/vdpa_user/vduse_dev.c
> +++ b/drivers/vdpa/vdpa_user/vduse_dev.c
> @@ -14,6 +14,7 @@
>  #include <linux/cdev.h>
>  #include <linux/device.h>
>  #include <linux/eventfd.h>
> +#include <linux/rwlock.h>

Lo! My daily -next builds based for Fedora using the Fedora rawhide
failed yesterday on various archs. I suspect it's due to above change,
as this was the error I got:

"""
In file included from drivers/vdpa/vdpa_user/vduse_dev.c:17:
./include/linux/rwlock.h:5:3: error: #error "Please do not include this
file directly."
    5 | # error "Please do not include this file directly."
      |   ^~~~~
./include/linux/rwlock.h:27:10: warning: ‘rwlock_init’ redefined
   27 | # define rwlock_init(lock)                                      \
      |          ^~~~~~~~~~~
In file included from ./include/linux/spinlock_rt.h:153,
                 from ./include/linux/spinlock.h:455,
                 from ./include/linux/sched.h:37,
                 from ./include/linux/percpu.h:12,
                 from ./arch/x86/include/asm/msr.h:16,
                 from ./arch/x86/include/asm/tsc.h:11,
                 from ./arch/x86/include/asm/timex.h:6,
                 from ./include/linux/timex.h:67,
                 from ./include/linux/time32.h:13,
                 from ./include/linux/time.h:60,
                 from ./include/linux/jiffies.h:10,
                 from ./include/linux/ktime.h:25,
                 from ./include/linux/timer.h:6,
                 from ./include/linux/netdevice.h:24,
                 from ./include/linux/if_vlan.h:10,
                 from ./include/linux/virtio_net.h:5,
                 from drivers/vdpa/vdpa_user/vduse_dev.c:11:
"""

For a complete log, see
https://download.copr.fedorainfracloud.org/results/@kernel-vanilla/next/fedora-rawhide-x86_64/09603789-next-next-all/builder-live.log.gz

Reverting the series made things work for me.

> [...]

Ciao, Thorsten

  reply	other threads:[~2025-09-27  7:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25  9:13 [PATCH v4 0/6] Add multiple address spaces support to VDUSE Eugenio Pérez
2025-09-25  9:13 ` [PATCH v4 1/6] vduse: make domain_lock an rwlock Eugenio Pérez
2025-09-27  6:27   ` Thorsten Leemhuis [this message]
2025-09-29  5:42     ` Eugenio Perez Martin
2025-09-25  9:13 ` [PATCH v4 2/6] vduse: add v1 API definition Eugenio Pérez
2025-09-25  9:13 ` [PATCH v4 3/6] vduse: add vq group support Eugenio Pérez
2025-09-26  7:42   ` Jason Wang
2025-09-26  8:15     ` Eugenio Perez Martin
2025-09-26  8:36       ` Jason Wang
2025-09-25  9:13 ` [PATCH v4 4/6] vduse: return internal vq group struct as map token Eugenio Pérez
2025-09-25  9:13 ` [PATCH v4 5/6] vduse: add vq group asid support Eugenio Pérez
2025-09-26  7:58   ` Jason Wang
2025-09-26  8:17     ` Eugenio Perez Martin
2025-09-26  8:37       ` Jason Wang
2025-09-25  9:13 ` [PATCH v4 6/6] vduse: bump version number Eugenio Pérez

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=3e5abb75-2192-46dc-a44e-d66fed87fc63@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lulu@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mcoqueli@redhat.com \
    --cc=mst@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=sgarzare@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xieyongji@bytedance.com \
    --cc=xuanzhuo@linux.alibaba.com \
    /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

all inboxes | Powered by JetHome®