From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dominique Martinet Subject: Re: Re: BUG: corrupted list in p9_read_work Date: Wed, 10 Oct 2018 18:10:03 +0200 Message-ID: <20181010161003.GA5371@nautica> References: <20181010144855.GB20918@nautica> <00000000000010889e0577e0f5f2@google.com> <20181010160022.GD20918@nautica> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: davem@davemloft.net, dvyukov@google.com, ericvh@gmail.com, linux-kernel@vger.kernel.org, lucho@ionkov.net, netdev@vger.kernel.org, rminnich@sandia.gov, syzkaller-bugs@googlegroups.com, v9fs-developer@lists.sourceforge.net To: syzbot Return-path: Content-Disposition: inline In-Reply-To: <20181010160022.GD20918@nautica> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Dominique Martinet wrote on Wed, Oct 10, 2018: > It works though, is it just picky because I didn't end it in .git? let's > try again, sorry for the noise... > > #syz test: git://github.com/martinetd/linux.git e4ca13f7d075e551dc158df6af18fb412a1dba0a And I guess the commit hash needs to be in the default clone branch to work ? ('git fetch ' happily fetches the commit in a new clone for me... But that feels like a github specific behaviour maybe) Oh, well; made a branch for it, last try for me. #syz test: git://github.com/martinetd/linux.git for-syzbot -- Dominique