linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Genes Lists <lists@sapience.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 6.6.8 stable: crash in folio_mark_dirty
Date: Sun, 31 Dec 2023 16:12:24 -0500	[thread overview]
Message-ID: <0903da3a0713698d32a7e15767b29f0743d8adc9.camel@sapience.com> (raw)
In-Reply-To: <ZZHWFOJln4I1A0sd@casper.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

On Sun, 2023-12-31 at 20:59 +0000, Matthew Wilcox wrote:
> On Sat, Dec 30, 2023 at 10:23:26AM -0500, Genes Lists wrote:
> > Apologies in advance, but I cannot git bisect this since machine
> > was
> > running for 10 days on 6.6.8 before this happened.
> 
> This problem simply doesn't make sense.  There's just no way we shoud
> be
> able to get a not-uptodate folio into the page tables.  We do have
> one
> pending patch which fixes a situation in which we can get some very
> odd-looking situations due to reusing a page which has been freed.
> I appreciate your ability to reproduce this is likely nil, but if you
> could add
> 
> https://lore.kernel.org/all/20231220214715.912B4C433CA@smtp.kernel.org/
> 
> to your kernel, it might make things more stable for you.
> 

Ok looks like that's in mainline - machine is now running 6.7.0-rc7 -
unless you prefer I patch 6.6.8 with above and change to that.

thanks and sorry about bringing up wacky problem.

gene




[-- Attachment #2: Type: text/html, Size: 1978 bytes --]

  reply	other threads:[~2023-12-31 21:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 15:23 Genes Lists
2023-12-30 18:02 ` Matthew Wilcox
2023-12-30 19:16   ` Genes Lists
2023-12-31  1:28 ` Hillf Danton
2023-12-31 13:07   ` Matthew Wilcox
2024-01-01  1:55     ` Hillf Danton
2024-01-01  9:07       ` Matthew Wilcox
2024-01-01 11:33         ` Hillf Danton
2024-01-01 14:11           ` Matthew Wilcox
2024-01-03 10:49             ` Hillf Danton
2024-01-03 17:53               ` Matthew Wilcox
2023-12-31 20:59 ` Matthew Wilcox
2023-12-31 21:12   ` Genes Lists [this message]
2023-12-31 21:15   ` Genes Lists

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=0903da3a0713698d32a7e15767b29f0743d8adc9.camel@sapience.com \
    --to=lists@sapience.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=willy@infradead.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