mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Aleksandr Nogikh <nogikh@google.com>,
	david@redhat.com, joannelkoong@gmail.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, m.szyprowski@samsung.com,
	mszeredi@redhat.com, willy@infradead.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] mm: fix lockdep issues in writeback handling
Date: Wed, 3 Sep 2025 09:09:34 +1000	[thread overview]
Message-ID: <20250903090934.4b5479d8@canb.auug.org.au> (raw)
In-Reply-To: <20250902154043.7214448ff3a9cb68c8d231d5@linux-foundation.org>

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

Hi Andrew,

On Tue, 2 Sep 2025 15:40:43 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> Perhaps Stephen can directly add it to linux-next for a while?

I will add it to linux-next from today (until Miklos sorts it out).
Note that the fuse tree was updated since yesterday's linux-next, but
this patch is still not included.

> From: Marek Szyprowski <m.szyprowski@samsung.com>
> To: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
> Cc: Marek Szyprowski <m.szyprowski@samsung.com>, "Matthew Wilcox (Oracle)" <willy@infradead.org>, Andrew Morton <akpm@linux-foundation.org>, David Hildenbrand <david@redhat.com>, Miklos Szeredi <mszeredi@redhat.com>, Joanne Koong <joannelkoong@gmail.com>
> Subject: [PATCH] mm: fix lockdep issues in writeback handling
> Date: Tue, 26 Aug 2025 15:09:48 +0200
> Sender: owner-linux-mm@kvack.org
> X-Mailer: git-send-email 2.34.1
> 
> Commit 167f21a81a9c ("mm: remove BDI_CAP_WRITEBACK_ACCT") removed
> BDI_CAP_WRITEBACK_ACCT flag and refactored code that depend on it.
> Unfortunately it also moved some variable intialization out of guarded
> scope in writeback handling, what triggers a true lockdep warning. Fix
> this by moving initialization to the proper place.
> 
> Fixes: 167f21a81a9c ("mm: remove BDI_CAP_WRITEBACK_ACCT")

This is now commit

  2841808f35ee ("mm: remove BDI_CAP_WRITEBACK_ACCT")

in the fuse tree.

> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-09-02 23:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250826131210eucas1p21a27a684042f37080b7a19599f479b7a@eucas1p2.samsung.com>
2025-08-26 13:09 ` Marek Szyprowski
2025-08-27 19:01   ` Joanne Koong
2025-08-27 19:57   ` David Hildenbrand
2025-09-02  9:52     ` Aleksandr Nogikh
2025-09-02 22:40       ` Andrew Morton
2025-09-02 23:09         ` Stephen Rothwell [this message]
2025-09-03  8:28           ` Miklos Szeredi

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=20250903090934.4b5479d8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=joannelkoong@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mszeredi@redhat.com \
    --cc=nogikh@google.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --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

all inboxes | Powered by JetHome®