[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180815101120.019f069e@canb.auug.org.au>
Date: Wed, 15 Aug 2018 10:11:20 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: "J. Bruce Fields" <bfields@...ldses.org>,
syzbot <syzbot+1f371ca19b341a276761@...kaller.appspotmail.com>,
jlayton@...nel.org, linux-fsdevel <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: general protection fault in send_sigurg_to_task
Hi Bruce,
On Tue, 14 Aug 2018 13:50:20 -0700 Dmitry Vyukov <dvyukov@...gle.com> wrote:
>
> On Tue, Aug 14, 2018 at 12:11 PM, J. Bruce Fields <bfields@...ldses.org> wrote:
> > On Mon, Aug 13, 2018 at 06:33:02AM -0700, syzbot wrote:
> >> syzbot has found a reproducer for the following crash on:
> >>
> >> HEAD commit: 5ed5da74de9e Add linux-next specific files for 20180813
> >> git tree: linux-next
> >
> > I fetched linux-next but don't have 5ed5da74de9e.
>
> +Stephen for the disappeared linux-next commit.
That is just the HEAD commit on linux-next that day. If you fetched
linux-next after I released next-20180814 yesterday, then it would have
a different HEAD commit. If you check out the tag next-20180813, you
will get the above HEAD commit.
> On the dashboard link you can see that it also happened on a more
> recent commit 4e8b38549b50459a22573d756dd1f4e1963c2a8d that I do see
> now in linux-next.
Which is just the HEAD commit of next-20180814.
Linux-next is rebuilt every day based on Linus' tree of the day,
followed by merging all the other branches, so its HEAD is different
every day.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists