linux-kernel - [v5.15 Regression] block: rename GENHD_FL_NO_PART_SCAN to GENHD_FL_NO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <924449dc-9b1f-4943-afe3-a68c03aedbb5@canonical.com>
Date: Wed, 3 Apr 2024 13:50:09 -0400
From: Joseph Salisbury <joseph.salisbury@...onical.com>
To: hch@....de
Cc: linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
 axboe@...nel.dk, gregkh@...uxfoundation.org, sashal@...nel.org,
 stable@...r.kernel.org, Francis Ginther <francis.ginther@...onical.com>
Subject: [v5.15 Regression] block: rename GENHD_FL_NO_PART_SCAN to
 GENHD_FL_NO_PART

Hi Christoph,

A kernel bug report was opened against Ubuntu [0].  This bug is a 
regression introduced in mainline version v5.17-rc1 and made it's way 
into v5.15 stable updates.

The following commit was identified as the cause of the regression in 5.15:

c6ce1c5dd327 ("block: rename GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART")

I was hoping to get your feedback, since you are the patch author. Is 
the best approach to revert this commit, since many third parties rely 
on the name being GENHD_FL_NO_PART_SCAN in kernel headers?  Is there a 
specific need that you know of that requires this commit in the 5.15 and 
earlier stable kernels?

Thanks,

Joe

[0] http://pad.lv/2053101