On Thu, Aug 8, 2013 at 9:22 AM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > On Thu, 08 Aug 2013 16:05:44 +0200 > Marcus Moeller <marcus.moeller@xxxxxx> wrote: > >> Am 07.08.2013 15:42, schrieb David McBride: >> > On 07/08/13 14:06, Jeff Layton wrote: >> > >> >> This patch is untested (other than for compilation), but I think it'll >> >> do the right thing. Metze, David could you test it and let us know if >> >> it helps? >> >> Just to verify: could it be that mfsymlink is already broken in >> 3.9.6-301.fc19? At least links created with fedora 18 are no longer >> readable there. Newly created links seems to work fine (at least till now). >> >> Greets >> Marcus >> > > Yes, 3.9.6 has the patch that broke it. > > What matters is how the (in memory) inode is created after mounting. If > you first run across an mfsymlink with a readdir() call, then you'll > get an inode that's "stuck" as a regular file. If you instead do > something like stat() it before ever running a readdir over the > containing directory, it should work just fine. > > This patch probably is probably reasonable for stable, given that the > original one also went there. > > Steve, want to mark as such? It is already marked for stable -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
