From: Mark Brown <broonie@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, hch@infradead.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.12-rc5
Date: Tue, 22 Oct 2024 20:34:58 +0100 [thread overview]
Message-ID: <28cd4d7e-c6fb-468e-81f8-35e0591f8360@sirena.org.uk> (raw)
In-Reply-To: <202410221225.32958DF786@keescook>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-10-22 19:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 17:39 Kent Overstreet
2024-10-22 19:06 ` Sasha Levin
2024-10-22 19:30 ` Kees Cook
2024-10-22 19:34 ` Mark Brown [this message]
2024-10-23 11:39 ` Sasha Levin
2024-10-22 20:49 ` Darrick J. Wong
2024-10-22 21:20 ` Sasha Levin
2024-10-23 10:42 ` Michael Ellerman
2024-10-23 11:41 ` Sasha Levin
2024-10-24 22:19 ` Kent Overstreet
2024-10-22 22:58 ` Kent Overstreet
2024-10-24 20:33 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28cd4d7e-c6fb-468e-81f8-35e0591f8360@sirena.org.uk \
--to=broonie@kernel.org \
--cc=hch@infradead.org \
--cc=kees@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®