linux-kernel - Re: [PATCH] bcache: enhancing the security of dirty data writeback

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: <20250805033120.7pzcpcjtpz5clnnz@P16.>
Date: Tue, 5 Aug 2025 11:31:20 +0800
From: Coly Li <colyli@...nel.org>
To: Kent Overstreet <kent.overstreet@...ux.dev>
Cc: Zhou Jifeng <zhoujifeng@...inos.com.cn>,
	linux-bcache <linux-bcache@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] bcache: enhancing the security of dirty data writeback

On Mon, Aug 04, 2025 at 09:31:38PM -0400, Kent Overstreet wrote:
> > Could we consider the solution I submitted, which is based on the
> > following main principle:
> > 1. Firstly, in the write_dirty_finish stage, the dirty marking bkeys are
> > not inserted into the btree immediately. Instead, they are temporarily
> > stored in an internal memory queue called Alist.
> > 2. Then, when the number of bkeys in Alist exceeds a certain limit, a
> > flush request is sent to the backend HDD.
> > 3. After the flush is sent, the bkeys recorded in Alist are then
> > inserted into the btree.
> > This process ensures that the written dirty data is written to the disk
> > before the btree is updated. The length of Alist can be configured,
> > allowing for better control of the flush sending frequency and reducing
> > the impact of the flush on the write speed.
> 
> That approach should work as well. You'll want to make the list size
> rather bit, and add statistics for how ofter flushes are being issued.
>

OK, then let me review this patch.

Coly Li