[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200715063639.GA5451@dhcp22.suse.cz>
Date: Wed, 15 Jul 2020 08:36:39 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: Todd Kjos <tkjos@...gle.com>, Hridya Valsaraju <hridya@...gle.com>,
Hillf Danton <hdanton@...a.com>,
Eric Biggers <ebiggers@...nel.org>,
syzbot <syzbot+7a0d9d0b26efefe61780@...kaller.appspotmail.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Arve Hjønnevåg <arve@...roid.com>,
Christian Brauner <christian@...uner.io>,
"open list:ANDROID DRIVERS" <devel@...verdev.osuosl.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Hugh Dickins <hughd@...gle.com>,
"Joel Fernandes (Google)" <joel@...lfernandes.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux-MM <linux-mm@...ck.org>, Martijn Coenen <maco@...roid.com>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
Todd Kjos <tkjos@...roid.com>,
Markus Elfring <Markus.Elfring@....de>
Subject: Re: possible deadlock in shmem_fallocate (4)
On Tue 14-07-20 10:32:20, Suren Baghdasaryan wrote:
[...]
> I'm not sure how we can annotate the fact that the inode_lock in
> generic_file_write_iter and in shmem_fallocate always operate on
> different inodes. Ideas?
I believe that the standard way is to use lockdep_set_class on your
backing inode. But asking lockdep experts would be better than relying
on my vague recollection
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists