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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 11 Nov 2009 14:20:42 -0800
From:	Stephen Hemminger <>
To:	Frans Pop <>
Subject: Re: Mount -o sync regression in 2.6.31

On Wed, 11 Nov 2009 22:34:22 +0100
Frans Pop <> wrote:

> Stephen Hemminger wrote:
> > I tried the obvious bisection, but git bisect seems to wonder off into
> > the weeds now. There is no reason that bisecting between v2.6.30 and
> > v2.6.31-rc1 should go off into v2.6.30-rc2
> AFAIK that can happen if some branch was merged after 2.6.30 that happened 
> to be based on a commit from v2.6.30-rc2. Did you check in what branch you 
> were when that happened?
> If you look at 'gitk v2.6.30..v2.6.31-rc1' and scroll to the bottom, you 
> will see quite a few merges of branches that were based on commits from 
> (early) v2.6.30-rcX releases.
> Cheers.

That makes sense but is confusing.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists