From: Andreas Schwab <schwab@linux-m68k.org>
To: Michael Schmitz <schmitzmic@googlemail.com>
Cc: Akinobu Mita <akinobu.mita@gmail.com>, linux-m68k@lists.linux-m68k.org
Subject: Re: find_next bitops on m68k may cause out of bounds memory access
Date: Mon, 07 Feb 2011 23:33:28 +0100 [thread overview]
Message-ID: <m2bp2nfpaf.fsf@igel.home> (raw)
In-Reply-To: <AANLkTi=LA1fmipUSycAEk48TwVXhzwbY5KMSfu=YMiCy@mail.gmail.com> (Michael Schmitz's message of "Tue, 8 Feb 2011 10:22:30 +1300")
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."
next prev parent reply other threads:[~2011-02-07 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 12:37 find_next bitops on m68k may cause out of bounds memory access Akinobu Mita
2011-02-07 21:22 ` Michael Schmitz
2011-02-07 22:33 ` Andreas Schwab [this message]
2011-02-08 0:55 ` Michael Schmitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2bp2nfpaf.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=akinobu.mita@gmail.com \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox