From: Suren Baghdasaryan <surenb@google.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: syzbot <syzbot+23de6daeb71241d36a18@syzkaller.appspotmail.com>,
Liam.Howlett@oracle.com, akpm@linux-foundation.org,
jannh@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, pfalcato@suse.de,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz
Subject: Re: [syzbot] [mm?] possible deadlock in __vma_start_write
Date: Tue, 3 Jun 2025 17:51:41 -0700 [thread overview]
Message-ID: <CAJuCfpHeHYxo1ZvG-mjDxcHd63nq_g9o5i-au-wZWHj+_dRy_A@mail.gmail.com> (raw)
In-Reply-To: <59aed5fa-1d19-442b-9b7b-a99aee9b7689@lucifer.local>
On Mon, Jun 2, 2025 at 7:19 AM Lorenzo Stoakes
<lorenzo.stoakes@oracle.com> wrote:
>
> On Mon, Jun 02, 2025 at 07:16:40AM -0700, Suren Baghdasaryan wrote:
> > On Mon, Jun 2, 2025 at 6:04 AM Lorenzo Stoakes
> > <lorenzo.stoakes@oracle.com> wrote:
> > >
> > > +cc Suren
> > >
> > > Suren - could you take a look at this please?
> >
> > Sure. I'll take a look today or tomorrow once I sort out my email
> > backlog. I was away for 10 days and have 2K emails to go through.
> >
>
I spent some time trying to connect the dots and still don't have the
definitive answer. I'll dive into it again tomorrow and post once I
have something useful.
Thanks,
Suren.
> Oh man and I thought my inbox was bad :) Sorry to add to it!
>
> No pressure, just a weird locking case, I'm wondering if there's something
> here or we just need to teach lockdep that this situation is ok.
>
> Hope you had some nice time away anyway :)
>
> Cheers, Lorenzo
next prev parent reply other threads:[~2025-06-04 0:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 15:40 syzbot
2025-06-02 13:04 ` Lorenzo Stoakes
2025-06-02 14:16 ` Suren Baghdasaryan
2025-06-02 14:19 ` Lorenzo Stoakes
2025-06-04 0:51 ` Suren Baghdasaryan [this message]
2025-06-04 5:17 ` Lorenzo Stoakes
2025-06-04 7:52 ` Vlastimil Babka
2025-06-04 8:31 ` John Ogness
2025-06-04 14:29 ` Suren Baghdasaryan
2025-06-05 9:40 ` Petr Mladek
2025-06-05 10:48 ` Peter Zijlstra
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=CAJuCfpHeHYxo1ZvG-mjDxcHd63nq_g9o5i-au-wZWHj+_dRy_A@mail.gmail.com \
--to=surenb@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pfalcato@suse.de \
--cc=syzbot+23de6daeb71241d36a18@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
/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