[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-m68k
Subject:    Re: find_next bitops on m68k may cause out of bounds memory access
From:       Michael Schmitz <schmitzmic () googlemail ! com>
Date:       2011-02-08 0:55:47
Message-ID: AANLkTi=DE3k6WB-Ee0rq3XBWfUWsWFM9jXXiodmMy_Mr () mail ! gmail ! com
[Download RAW message or body]

Thanks Andreas - there goes my theory I guess. Ralf's linux-m68k CVS
conversion tree predates 2.6.32 by quite some time.

  Michael


On Tue, Feb 8, 2011 at 11:33 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Michael Schmitz <schmitzmic@googlemail.com> writes:
>
>> Thanks for spotting this - does anyone remember when this version of
>> find_next bitops was first introduced?
>
> c82db5b in git.kernel.org:ralf/linux-m68k.git
>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]