[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170602.143906.818489457650113258.davem@davemloft.net>
Date: Fri, 02 Jun 2017 14:39:06 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: darrick.wong@...cle.com
Cc: herbert@...dor.apana.org.au, linux-crypto@...r.kernel.org,
sparclinux@...r.kernel.org, linux-btrfs@...r.kernel.org,
clm@...com, jbacik@...com, dsterba@...e.com, matorola@...il.com,
sandeen@...deen.net, linux-xfs@...r.kernel.org,
linux-ext4@...r.kernel.org
Subject: Re: crypto: Work around deallocated stack frame reference gcc bug
on sparc.
From: "Darrick J. Wong" <darrick.wong@...cle.com>
Date: Fri, 2 Jun 2017 11:08:08 -0700
> ext4/jbd2's crc32c implementations will also need a fix like this for
> {ext4,jbd2}_chksum. Note that both of these modules call the crypto api
> directly to avoid a static dependence on libcrc32c; this was done to
> reduce kernel footprint for applications that don't need it. (ext2,
> ext3, and ext4 before the metadata_csum feature existed).
Good catch. I even looked at that code the other day so should
have spotted it as well.
I'll integrate fixes for those into my patch when I get a chance,
thanks!
Powered by blists - more mailing lists