Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753458Ab3EJONd (ORCPT ); Fri, 10 May 2013 10:13:33 -0400 Received: from mail-la0-f43.google.com ([209.85.215.43]:39726 "EHLO mail-la0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753232Ab3EJONc (ORCPT ); Fri, 10 May 2013 10:13:32 -0400 MIME-Version: 1.0 X-Originating-IP: [188.6.195.195] Date: Fri, 10 May 2013 16:13:30 +0200 Message-ID: Subject: Mount failure due to restricted access to a point along the mount path From: Miklos Szeredi To: linux-cifs@vger.kernel.org Cc: Steve French , Jeff Layton , Kernel Mailing List , sjayaraman@novell.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 782 Lines: 22 Hi, A while ago this was discussed: http://thread.gmane.org/gmane.linux.kernel.cifs/7779 This is essentially a regression introduced by the shared superblock changes in 3.0 and several SUSE customers are complaining about it. I've created a temporary fix which reverts 29 commits related to the shared superblock changes. It works, but it's obviously not a permanent fix, especially since we definitely don't want to diverge from mainline. Is this issue being worked on? Don't other distros have similar reports? Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/