From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751990AbbCTNbW (ORCPT ); Fri, 20 Mar 2015 09:31:22 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:59067 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751944AbbCTNbV (ORCPT ); Fri, 20 Mar 2015 09:31:21 -0400 Date: Fri, 20 Mar 2015 13:31:18 +0000 From: Al Viro To: Karel Zak Cc: Miklos Szeredi , linux-kernel@vger.kernel.org Subject: Re: d_path() and overlay fs Message-ID: <20150320133118.GW29656@ZenIV.linux.org.uk> References: <20150320132914.GA1749@ws.net.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150320132914.GA1749@ws.net.home> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 20, 2015 at 02:29:14PM +0100, Karel Zak wrote: > It seems like serious problem because kernel uses d_path() (and > friends) on many places to generate path strings for userspace in > /proc and /sys and people already use overlay fs in containers. It's not d_path(), it's file->f_path being wrong to start with. Same problem as what dhowells is fighting wrt LSM shite.