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: <9a8748490804101639s7adf468dp6bf4241da5845eea@mail.gmail.com>
Date:	Fri, 11 Apr 2008 01:39:22 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	vincent-perrier <vincent-perrier@...b-internet.fr>
Cc:	"David Miller" <davem@...emloft.net>, tilman@...p.cc, lkml@....ca,
	yoshfuji@...ux-ipv6.org, jeff@...zik.org, rjw@...k.pl,
	linux-kernel@...r.kernel.org, linux-net@...r.kernel.org
Subject: Re: 2.6.25-rc8: FTP transfer errors

On 11/04/2008, vincent-perrier <vincent-perrier@...b-internet.fr> wrote:
> I am an end user, I do not know precisely what bisecting means, but I
>  have spent some time on bug 8895, I suppose I have totally bisseced it,

"bisect" refers to the "git bisect" command of the git tool.

For information on git, look here: http://git.or.cz/

For information on "git bisect" look here:
http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
and here: http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#using-bisect

Basically what bisect does is this; you tell it about your
last-known-good kernel version and your first-known-bad kernel
version. Then git finds all the changesets between those two version,
cuts the set in half and produces the kernel source matching the
middle point. You can then build and test that kernel and then you
tell git if it was good or bad - it'll then use that good/bad info to
cut the set of patches in half again etc etc until you eventually end
up with the exact changeset that caused your problem.  It's very
powerful and can often narrow a problem down to a single commit, but
it does require that your problem is completely reproducible so that
you can reliably test it on each kernel 'git bisect' produces for you.

[please don't top-post : http://www.catb.org/~esr/jargon/html/T/top-post.html ]

<...snip...>

-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ