linux-kernel - Re: [GIT PULL] bcachefs fixes for 6.12-rc5

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: <dctt3tf65qsvwyr5exvee7bkmwh6aejqcd4t7uwfzvjiowqtzk@fncmtmgdbg5b>
Date: Tue, 22 Oct 2024 18:58:09 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: Sasha Levin <sashal@...nel.org>, 
	Linus Torvalds <torvalds@...ux-foundation.org>, linux-bcachefs@...r.kernel.org, linux-fsdevel@...r.kernel.org, 
	linux-kernel@...r.kernel.org, kees@...nel.org, hch@...radead.org, broonie@...nel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.12-rc5

On Tue, Oct 22, 2024 at 01:49:31PM -0700, Darrick J. Wong wrote:
> On Tue, Oct 22, 2024 at 03:06:38PM -0400, Sasha Levin wrote:
> > On Tue, Oct 22, 2024 at 01:39:10PM -0400, Kent Overstreet wrote:
> > > 
> > > The following changes since commit 5e3b72324d32629fa013f86657308f3dbc1115e1:
> > > 
> > >  bcachefs: Fix sysfs warning in fstests generic/730,731 (2024-10-14 05:43:01 -0400)
> > > 
> > > are available in the Git repository at:
> > > 
> > >  https://github.com/koverstreet/bcachefs tags/bcachefs-2024-10-22
> > 
> > Hi Linus,
> > 
> > There was a sub-thread on the linus-next discussion around improving
> > telemetry around -next/lore w.r.t soaking time and mailing list reviews
> > (https://lore.kernel.org/all/792F4759-EA33-48B8-9AD0-FA14FA69E86E@kernel.org/).
> > 
> > I've prototyped a set of scripts based on suggestions in the thread, and
> > wanted to see if you'd find it useful. A great way to test it out is with
> > a random pull request you'd review anyway :)
> > 
> > Is the below useful in any way? Or do you already do something like this
> > locally and I'm just wasting your time?
> > 
> > If it's useful, is bot reply to PRs the best way to share this? Any
> > other information that would be useful?
> 
> As a maintainer I probably would've found this to be annoying, but with
> all my other outside observer / participant hats on, I think it's very
> good to have a bot to expose maintainers not following the process.

That's the interesting about face...

Personally, I'm curious what people are trying to achieve here.