[lkml]   [2019]   [Apr]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: WARNING in ovl_instantiate
On Tue, Mar 26, 2019 at 2:10 PM syzbot
<> wrote:
> syzbot has bisected this bug to:
> commit 01b39dcc95680b04c7af5de7f39f577e9c4865e3
> Author: Amir Goldstein <>
> Date: Fri May 11 08:15:15 2018 +0000
> ovl: use inode_insert5() to hash a newly created inode
> bisection log:
> start commit: de6629eb Merge tag 'pci-v5.0-fixes-1' of git://git.kernel...
> git tree: upstream
> final crash:
> console output:
> kernel config:
> dashboard link:
> syz repro:
> Reported-by:
> Fixes: 01b39dcc9568 ("ovl: use inode_insert5() to hash a newly created
> inode")


The root cause of this bug is that repro is mounting overlapping overlay
layers (i.e. upperdir=./file0,lowerdir=.:file0).
Miklos claimed that the fix should be to fail such mounts.
Below is a patch to test:

#syz test: ovl-check-overlap

However, I see that this specific overlapping layers mount has already
mutated to several other repros out there, like the ones in this bug:

I believe that disallowing overlapping layers will silence some
bugs, whose root cause may be different.

Besides doing the overlapping layers mount, this repro family also
does extensive access to overlay underlying layers concurrently
with overlay access and *that* is the root cause for most of these
"possible deadlock" bugs (some false positives and some real).

Assuming that ovl-check-overlap will get merged, you may need to
hint syzkaller that overlapping layers is no longer a valid input or
maybe it will figure it out on its own?...


 \ /
  Last update: 2019-04-19 21:54    [W:0.088 / U:1.348 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site