netdev - Re: [PATCH net] rhashtable: don't allocate ht structure on stack in test_rht

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] [day] [month] [year] [list]

Message-Id: <20150220.163407.2037909158415351477.davem@davemloft.net>
Date:	Fri, 20 Feb 2015 16:34:07 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	daniel@...earbox.net
Cc:	tgraf@...g.ch, netdev@...r.kernel.org
Subject: Re: [PATCH net] rhashtable: don't allocate ht structure on stack
 in test_rht_init

From: Daniel Borkmann <daniel@...earbox.net>
Date: Fri, 20 Feb 2015 21:14:21 +0100

> With object runtime debugging enabled, the rhashtable test suite
> will rightfully throw a warning "ODEBUG: object is on stack, but
> not annotated" from rhashtable_init().
> 
> This is because run_work is (correctly) being initialized via
> INIT_WORK(), and not annotated by INIT_WORK_ONSTACK(). Meaning,
> rhashtable_init() is okay as is, we just need to move ht e.g.,
> into global scope.
> 
> It never triggered anything, since test_rhashtable is rather a
> controlled environment and effectively runs to completion, so
> that stack memory is not vanishing underneath us, we shouldn't
> confuse any testers with it though.
> 
> Fixes: 7e1e77636e36 ("lib: Resizable, Scalable, Concurrent Hash Table")
> Signed-off-by: Daniel Borkmann <daniel@...earbox.net>

Applied and queued up for -stable, thanks Daniel.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html