[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <28cd4d7e-c6fb-468e-81f8-35e0591f8360@sirena.org.uk>
Date: Tue, 22 Oct 2024 20:34:58 +0100
From: Mark Brown <broonie@...nel.org>
To: Kees Cook <kees@...nel.org>
Cc: Sasha Levin <sashal@...nel.org>,
Kent Overstreet <kent.overstreet@...ux.dev>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-bcachefs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, hch@...radead.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.12-rc5
On Tue, Oct 22, 2024 at 12:30:38PM -0700, Kees Cook wrote:
> On Tue, Oct 22, 2024 at 03:06:38PM -0400, Sasha Levin wrote:
> > --------------------
> > a069f014797fd bcachefs: Set bch_inode_unpacked.bi_snapshot in old inode path
> > e04ee8608914d bcachefs: Mark more errors as AUTOFIX
> > f0d3302073e60 bcachefs: Workaround for kvmalloc() not supporting > INT_MAX allocations
> > 3956ff8bc2f39 bcachefs: Don't use wait_event_interruptible() in recovery
> > eb5db64c45709 bcachefs: Fix __bch2_fsck_err() warning
> And then maybe limit this to 5 or 10 (imagine a huge PR like netdev or
> drm).
OTOH since this is supposed to be only for commits that didn't spend
time in -next perhaps exploding badly is getting the message over
clearly? Or at least putting something in that makes it stand out that
truncation happened. It's a constant tradeoff with this sort of thing.
> Nice work!
Indeed.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists