linux-kernel - Re: [GIT PULL] bcachefs changes for 6.17

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 for Android: free password hash cracker in your pocket

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

Message-ID: <f993a298-b455-4aa7-a4e1-f0416b255c5e@wiesinger.com>
Date: Sun, 10 Aug 2025 06:29:47 +0200
From: Gerhard Wiesinger <lists@...singer.com>
To: Aquinas Admin <admin@...inas.su>,
        Malte Schröder <malte.schroeder@...ip.de>,
        Kent Overstreet <kent.overstreet@...ux.dev>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "Carl E. Thompson" <list-bcachefs@...lthompson.net>
Cc: linux-bcachefs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] bcachefs changes for 6.17

On 07.08.2025 14:42, Aquinas Admin wrote:
> This "We don't start adding new features just because you found other bugs"
> sounds absurd. So, if we find bugs, they can't be fixed if we need to extend the
> functionality before the release? Excuse me, what? I clearly understand the
> absurdity of this requirement. Because it effectively means that if we notice
> that ext4 is corrupting data only in RC simply because some code was forgotten
> to be added to a subsystem during the release window, we can't accept the fix
> because it requires adding new functionality and we will release the version
> with the problem. I clearly understand that this is not the exact situation,
> but it was done as a solution to an existing user's problem. Moreover, the
> amount of changes is not that significant. Especially since it's not really a
> fix but a workaround, a useful one that can actually help some real users in
> certain situations.
>
> new USB serial driver device ids 6.12-rc7 is this new functionality or not?
> ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx 6.11-rc7 - new
> functionality?
> ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx - 6.11-rc7
> Octeontx2-pf: ethtool: support multi advertise mode - 6.15-rc5
> drm/i915/flipq: Implement Wa_18034343758
> drm/i915/display: Add drm_panic support
> Is this different? Or are the rules somehow not for everyone?
>
> But no, instead, this is what happened.

That mentioned code parts are AFAIK NOT experimental and therefore 
stable. But still include feature request in RC7 phase. Will that be 
removed, too?

I think we should sort out 3 topics:

1. Technical topics

2. Working together from an organizational/process perspective

3. Working together from a personal perspective

my 2 cents.

Ciao,

Gerhard