linux-kernel - Re: [PATCH] trace: correct start_index in find

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: <20160106225016.2e730dd3@gandalf.local.home>
Date:	Wed, 6 Jan 2016 22:50:16 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
Cc:	"Qiu, PeiyangX" <peiyangx.qiu@...el.com>,
	linux-kernel@...r.kernel.org,
	Rusty Russell <rusty@...tcorp.com.au>,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH] trace: correct start_index in find_next

On Thu, 07 Jan 2016 10:56:56 +0800
"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com> wrote:

> How is this patch? It fixes a kernel panic.
> 

Linus already pulled it. It's also marked for stable. See commit:
f36d1be2930ede0a1947686e1126ffda5d5ee1bb in Linus's tree.

I renamed the subject slightly to:

"tracing: Fix setting of start_index in find_next()"

-- Steve
--
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/