linux-kernel - Re: [ 41/45] m68k: Truncate base in do

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: <20130818205042.GA22572@kroah.com>
Date:	Sun, 18 Aug 2013 13:50:42 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	stable <stable@...r.kernel.org>
Subject: Re: [ 41/45] m68k: Truncate base in do_div()

On Sun, Aug 18, 2013 at 10:39:01PM +0200, Geert Uytterhoeven wrote:
> On Sun, Aug 18, 2013 at 10:36 PM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> > 3.10-stable review patch.  If anyone has any objections, please let me know.
> >
> > ------------------
> >
> > From: Andreas Schwab <schwab@...ux-m68k.org>
> >
> > commit ea077b1b96e073eac5c3c5590529e964767fc5f7 upstream.
> >
> > Explicitly truncate the second operand of do_div() to 32 bits to guard
> > against bogus code calling it with a 64-bit divisor.
> >
> > [Thorsten]
> >
> > After upgrading from 3.2 to 3.10, mounting a btrfs volume fails with:
> >
> > btrfs: setting nodatacow, compression disabled
> > btrfs: enabling auto recovery
> > btrfs: disk space caching is enabled
> 
> What happened to the rest of the commit message?

It looks like quilt will cut off the rest of the message after it sees
the "*** ZERO DIVIDE ***   FORMAT=2" line.

I don't know why it does that, never noticed that before, I'll go fix
this up, thanks.

greg k-h
--
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/