linux-kernel - Re: m68k libc5 regression

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <Pine.LNX.4.64.0806021223120.6718@jikos.suse.cz>
Date:	Mon, 2 Jun 2008 12:27:35 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Ingo Molnar <mingo@...e.hu>,
	Linux/m68k <linux-m68k@...r.kernel.org>,
	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: m68k libc5 regression

On Sun, 1 Jun 2008, Andrew Morton wrote:

> > -	if (brk < mm->start_brk)
> > +#ifdef CONFIG_COMPAT_BRK
> > +	min_brk = mm->end_code;
> > +#else
> > +	min_brk = mm->start_brk;
> > +#endif
> > +	if (brk < min_brk)
> >  		goto out;
> >  
> OK, we have a problem here.
> Somebody has gone and checked this patch into their tree and it now
> appears in linux-next.

Ah, I have expected either you or Ingo (as my patch that introduced the 
bug went through his tree too) to pick that up.

> I do not know how to work out how this patch got into linux-next.

Well, git-blame on mm/mmap.c in linux-next tree shows the commit id, and 
then git-show --pretty=full tells you the comitter name.

-- 
Jiri Kosina
SUSE Labs
--
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/