linux-kernel - Re: How to report kernel panic in 4.4.x

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180824163338.4bd9db8f@ninja>
Date:   Fri, 24 Aug 2018 16:33:38 +0200
From:   "Matthias B." <matthias@...terdrache.de>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: How to report kernel panic in 4.4.x

On Fri, 24 Aug 2018 16:12:54 +0200
Greg KH <gregkh@...uxfoundation.org> wrote:

> 
> All of the stable trees are here:
> 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/
> you want the linux-4.4.y branch to work off of.
> 
> All of the kernels releases are tagged, so you can start with v4.4.147
> as the good entry for 'git bisect'.

I've never used git bisect on the kernel. Can I simply do "make" for
each step or do I need to "make mrproper" every time?

MSB