From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 3 Jun 2016 23:29:27 +0100 From: Al Viro To: Linus Torvalds Cc: Oleg Drokin , " Mailing List" , "" Subject: Re: Dcache oops Message-ID: <20160603222927.GX14480@ZenIV.linux.org.uk> References: <0C971585-6BFC-4665-832B-9B262F733BFC@linuxhacker.ru> <20160603042648.GN14480@ZenIV.linux.org.uk> <74306F63-DBDF-4DED-85D2-5C3FB21B8A1E@linuxhacker.ru> <20160603182203.GR14480@ZenIV.linux.org.uk> <4285E00F-7228-485C-AD32-97552ED746F2@linuxhacker.ru> <20160603200759.GS14480@ZenIV.linux.org.uk> <20160603212652.GT14480@ZenIV.linux.org.uk> <20160603222355.GW14480@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160603222355.GW14480@ZenIV.linux.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: On Fri, Jun 03, 2016 at 11:23:55PM +0100, Al Viro wrote: > It's not that. It's explicit put_link() in do_last(), followed by > ESTALEOPEN and subsequent misbegotten "retry the last step on ESTALEOPEN" > looking at now-freed nd->last.name. IOW, the bug predates delayed_call > stuff. FWIW, I'd stepped into that in d63ff28f "namei: make should_follow_link() store the link in nd->link", so it's 4.1+ mess. delayed_call stuff is 4.4+...