linux-kernel - 回复: [PATCH] btrfs: remove BTRFS_REF_LAST from btrfs_ref

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <SEZPR06MB52696AF210BDA98300C58FCFE8BD2@SEZPR06MB5269.apcprd06.prod.outlook.com>
Date: Wed, 16 Apr 2025 13:25:34 +0000
From: 李扬韬 <frank.li@...o.com>
To: "dsterba@...e.cz" <dsterba@...e.cz>, Qu Wenruo <quwenruo.btrfs@....com>
CC: "clm@...com" <clm@...com>, "josef@...icpanda.com" <josef@...icpanda.com>,
	"dsterba@...e.com" <dsterba@...e.com>, "linux-btrfs@...r.kernel.org"
	<linux-btrfs@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject:
 回复: [PATCH] btrfs: remove BTRFS_REF_LAST from btrfs_ref_type

> I think in this case it's ok to remove it, although I agree that we have the _LAST or _NR elsewhere. In btrfs_ref_type() tere's an assertion

>  ASSERT(ref->type == BTRFS_REF_DATA || ref->type == BTRFS_REF_METADATA);

> which is validating the values. There's no enumeration or switch that could utilize the upper bound.

Do I need to modify the submission information and resend this patch?

Thx,
Yangtao