All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: Bart Van Assche <bvanassche@acm.org>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Ming Lei <ming.lei@redhat.com>, Martin Wilck <mwilck@suse.com>,
	Benjamin Marzinski <bmarzins@redhat.com>,
	stable@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
	Damien Le Moal <dlemoal@kernel.org>,
	Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [PATCH v6 2/2] block: Remove queue freezing from several sysfs store callbacks
Date: Mon, 17 Nov 2025 14:31:46 +0530	[thread overview]
Message-ID: <542de632-aace-4ff4-940e-55b57142b496@linux.ibm.com> (raw)
In-Reply-To: <20251114210409.3123309-3-bvanassche@acm.org>

Hi Bart,

On 11/15/25 2:34 AM, Bart Van Assche wrote:
> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
> index 2fff8a80dbd2..cb4ba09959ee 100644
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -495,7 +495,7 @@ struct request_queue {
>  	 */
>  	unsigned long		queue_flags;
>  
> -	unsigned int		rq_timeout;
> +	unsigned int __data_racy rq_timeout;
>  
>  	unsigned int		queue_depth;

This change look good to me however as I mentioned earlier, 
introducing __data_racy would break the kernel build. So 
are you going to raise a separate bug report to fix it? 

  AS      .tmp_vmlinux2.kallsyms.o
  LD      vmlinux.unstripped
  BTFIDS  vmlinux.unstripped
WARN: multiple IDs found for 'task_struct': 116, 10183 - using 116
WARN: multiple IDs found for 'module': 190, 10190 - using 190
WARN: multiple IDs found for 'vm_area_struct': 324, 10227 - using 324
WARN: multiple IDs found for 'inode': 956, 10314 - using 956
WARN: multiple IDs found for 'path': 989, 10344 - using 989
WARN: multiple IDs found for 'file': 765, 10375 - using 765
WARN: multiple IDs found for 'cgroup': 1030, 10409 - using 1030
WARN: multiple IDs found for 'seq_file': 1358, 10593 - using 1358
WARN: multiple IDs found for 'bpf_prog': 2054, 10984 - using 2054
WARN: multiple IDs found for 'bpf_map': 2134, 11012 - using 2134
[...]
[...]
make[2]: *** [scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 255
make[2]: *** Deleting file 'vmlinux.unstripped'
make[1]: *** [/home/src/linux/Makefile:1242: vmlinux] Error 2
make: *** [Makefile:248: __sub-make] Error 2

Thanks,
--Nilay

  reply	other threads:[~2025-11-17  9:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 21:04 [PATCH v6 0/2] Fix a recently introduced deadlock Bart Van Assche
2025-11-14 21:04 ` [PATCH v6 1/2] fs: Add the __data_racy annotation to backing_dev_info.ra_pages Bart Van Assche
2025-11-18  6:55   ` Nilay Shroff
2025-11-14 21:04 ` [PATCH v6 2/2] block: Remove queue freezing from several sysfs store callbacks Bart Van Assche
2025-11-17  9:01   ` Nilay Shroff [this message]
2025-11-17 20:44     ` Bart Van Assche
2025-11-18  6:54       ` Nilay Shroff
2025-11-18  6:56   ` Nilay Shroff
2025-11-18 15:38 ` [PATCH v6 0/2] Fix a recently introduced deadlock Jens Axboe

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=542de632-aace-4ff4-940e-55b57142b496@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=axboe@kernel.dk \
    --cc=bmarzins@redhat.com \
    --cc=bvanassche@acm.org \
    --cc=dlemoal@kernel.org \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kch@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=mwilck@suse.com \
    --cc=stable@vger.kernel.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.