linux-kernel - Re: suspicious RCU usage with unlazy

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]

Date:	Mon, 9 Sep 2013 07:31:44 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jerry Snitselaar <jerry.snitselaar@...cle.com>
Cc:	Waiman Long <Waiman.Long@...com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: suspicious RCU usage with unlazy_walk()

On Sun, Sep 8, 2013 at 1:46 AM, Jerry Snitselaar
<jerry.snitselaar@...cle.com> wrote:
> Running 3.11.0-07547-g44598f9 I hit the following last night. I have
> not had it reproduce since then. Should there be some lock cleanup in
> the error path prior to the dput() call like unlock_rcu_walk()?

Heh. I should have read more email yesterday, but I was too busy
looking at the dentry code, so I didn't get to some of my mailbox
until now.

Happily, the reason I was too busy was that I had noticed that my
d_rcu_to_refcount() changes were bad, and spent that time cleaning it
up and fixing this bug.

So this should be fixed in the current tree (current top of tree,
commit e5c832d55588 in particular).

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