linux-kernel - Re: [Patch] Incoming XPC channel messages can come in after the channel's partition structures have been torn down.

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]

Date:	Mon, 18 Oct 2010 12:40:55 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Robin Holt <holt@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [Patch] Incoming XPC channel messages can come in after the
 channel's partition structures have been torn down.

On Mon, 18 Oct 2010 08:35:08 -0500
Robin Holt <holt@....com> wrote:

> Under some workloads, some channel messages have been observed being
> delayed on the sending side past the point where the receiving side
> has been able to tear down its partition structures.  This condition is
> already detected in xpc_handle_activate_IRQ_uv(), but that information
> is not given to xpc_handle_activate_mq_msg_uv().  As a result,
> xpc_handle_activate_mq_msg_uv() assumes the structures still exist and
> references them.

With what result?  Machine goes boom?

Would you consider this a 2.6.36 fix?  Backport to -stable?
--
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/