linux-kernel - Re: zlib oops with ipcomp in 2.6.24

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: <20080228.112355.15717375.davem@davemloft.net>
Date:	Thu, 28 Feb 2008 11:23:55 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	herbert@...dor.apana.org.au
Cc:	Daniel.Beschorner@...ton.com, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, rpurdie@...ys.net
Subject: Re: zlib oops with ipcomp in 2.6.24

From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Fri, 29 Feb 2008 01:50:11 +0800

> [IPCOMP]: Disable BH on output when using shared tfm
> 
> Because we use shared tfm objects in order to conserve memory,
> (each tfm requires 128K of vmalloc memory), BH needs to be turned
> off on output as that can occur in process context.
> 
> Previously this was done implicitly by the xfrm output code.
> That was lost when it became lockless.  So we need to add the
> BH disabling to IPComp directly.
> 
> Signed-off-by: Herbert Xu <herbert@...dor.apana.org.au>

Applied, thanks Herbert.

The xfrm output lockless stuff is only in 2.6.25, so
we should not need this for -stable right?
--
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/