[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251113144807.GA31071@lst.de>
Date: Thu, 13 Nov 2025 15:48:07 +0100
From: Christoph Hellwig <hch@....de>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: Oliver Sang <oliver.sang@...el.com>, Christoph Hellwig <hch@....de>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Lameter <cl@...two.org>,
David Rientjes <rientjes@...gle.com>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Harry Yoo <harry.yoo@...cle.com>, linux-mm@...ck.org,
oe-lkp@...ts.linux.dev, lkp@...el.com, Jens Axboe <axboe@...nel.dk>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Johannes Thumshirn <johannes.thumshirn@....com>,
Anuj Gupta <anuj20.g@...sung.com>,
Kanchan Joshi <joshi.k@...sung.com>, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: poison_element vs highmem, was Re: [linux-next:master] [block]
ec7f31b2a2: BUG:unable_to_handle_page_fault_for_address
On Thu, Nov 13, 2025 at 02:48:06PM +0100, Vlastimil Babka wrote:
> I'll make this a full patch then. How urgent is it, Christoph? I suppose
> this is related to the bulk mempool changes, and we discussed the users will
> target 6.20 (7.0?) merge window? So landing this fix in 6.19 is enough?
The trigger is a change in the block tree that is in linux-next. So 6.19
should be fine, although getting it into linux-next ASAP would be great.
Powered by blists - more mailing lists