From: Aleksandr Nogikh <nogikh@google.com>
To: david@redhat.com
Cc: akpm@linux-foundation.org, 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: Re: [PATCH] mm: fix lockdep issues in writeback handling
Date: Tue, 2 Sep 2025 11:52:50 +0200 [thread overview]
Message-ID: <20250902095250.1319807-1-nogikh@google.com> (raw)
In-Reply-To: <345d49d2-5b6b-4307-824b-5167db737ad2@redhat.com>
Hi,
When can the patch be expected to reach linux-next?
Syzbot can't build/boot the tree for more than 12 days already :(
--
Aleksandr
On 27.08.25, David Hildenbrand wrote:
> On 26.08.25 15:09, Marek Szyprowski wrote:
> > 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.
>
> Nasty
>
> >
> > Fixes: 167f21a81a9c ("mm: remove BDI_CAP_WRITEBACK_ACCT")
> > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> > ---
>
> Acked-by: David Hildenbrand <david@redhat.com>
>
> --
> Cheers
>
> David / dhildenb
next prev parent reply other threads:[~2025-09-02 9:52 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 [this message]
2025-09-02 22:40 ` Andrew Morton
2025-09-02 23:09 ` Stephen Rothwell
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=20250902095250.1319807-1-nogikh@google.com \
--to=nogikh@google.com \
--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=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®