public inbox for linux-unionfs@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+66a9752fa927f745385e@syzkaller.appspotmail.com>
To: amir73il@gmail.com, dvyukov@google.com,
	linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
	miklos@szeredi.hu, mszeredi@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: WARNING: bad unlock balance in ovl_llseek
Date: Fri, 06 Mar 2020 14:35:02 -0800	[thread overview]
Message-ID: <000000000000ad0f2c05a0374382@google.com> (raw)
In-Reply-To: <CAOQ4uxirc1WwQOzE4Qq=k2R0ntGNTGYsot1b63DPkwCbUYjyZA@mail.gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger crash:

Reported-and-tested-by: syzbot+66a9752fa927f745385e@syzkaller.appspotmail.com

Tested on:

commit:         13944050 ovl: fix lock in ovl_llseek()
git tree:       https://github.com/amir73il/linux.git ovl-fixes
kernel config:  https://syzkaller.appspot.com/x/.config?x=31018567b8f0fc70
dashboard link: https://syzkaller.appspot.com/bug?extid=66a9752fa927f745385e
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2020-03-06 22:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-01 19:13 WARNING: bad unlock balance in ovl_llseek syzbot
2020-03-02 11:10 ` Amir Goldstein
2020-03-02 11:17   ` Miklos Szeredi
2020-03-02 12:19     ` Amir Goldstein
2020-03-03  7:34       ` Amir Goldstein
2020-03-06 22:35         ` syzbot [this message]
2020-03-02 11:29   ` Dmitry Vyukov
2020-03-02 12:10     ` Amir Goldstein
2020-03-02 12:34       ` Dmitry Vyukov
2020-03-02 13:24         ` Amir Goldstein
2020-03-02 14:57           ` Dmitry Vyukov

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=000000000000ad0f2c05a0374382@google.com \
    --to=syzbot+66a9752fa927f745385e@syzkaller.appspotmail.com \
    --cc=amir73il@gmail.com \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /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