mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zheng Qixing <zhengqixing@huaweicloud.com>
To: gregkh@linuxfoundation.org
Cc: cve@kernel.org, gregkh@kernel.org,
	linux-cve-announce@vger.kernel.org, linux-kernel@vger.kernel.org,
	yukuai@fnnas.com, ming.lei@redhat.com,
	Nilay Shroff <nilay@linux.ibm.com>,
	"zhangyi (F)" <yi.zhang@huawei.com>,
	yangerkun <yangerkun@huawei.com>, Hou Tao <houtao1@huawei.com>
Subject: Re: CVE-2025-40146: blk-mq: fix potential deadlock while nr_requests grown
Date: Thu, 27 Nov 2025 21:22:42 +0800	[thread overview]
Message-ID: <15fb6eed-e107-4ef7-a569-3328a02e2c39@huaweicloud.com> (raw)
In-Reply-To: <2025111256-CVE-2025-40146-b919@gregkh>

Hi,

Commit b86433721f46 ("blk-mq: fix potential deadlock while nr_requests 
grown")  aims to avoid a deadlock issue when the queue is frozen and 
memory reclaim is triggered.

However, the sysfs nr_requests update path is already under a 
memalloc_noio_save() region while the queue is frozen (via 
blk_mq_freeze_queue()).

Would it be possible to reject this CVE, or clarify why it needs CVE 
assignment in this case?

Any feedback or further explanation would be appreciated.


Best regards,

Qixing


       reply	other threads:[~2025-11-27 13:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2025111256-CVE-2025-40146-b919@gregkh>
2025-11-27 13:22 ` Zheng Qixing [this message]
2025-11-27 13:39   ` Greg KH
2025-11-28  1:15     ` Zheng Qixing
2025-11-28  5:20       ` Nilay Shroff
2025-11-28  6:33         ` yangerkun
2025-11-28  7:15           ` Nilay Shroff
2025-11-28  9:44             ` Zheng Qixing
2025-11-29  3:52             ` Zheng Qixing
2025-11-29  4:01 ` Zheng Qixing

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=15fb6eed-e107-4ef7-a569-3328a02e2c39@huaweicloud.com \
    --to=zhengqixing@huaweicloud.com \
    --cc=cve@kernel.org \
    --cc=gregkh@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=houtao1@huawei.com \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=nilay@linux.ibm.com \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai@fnnas.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®