linux-kernel - Re: [git pull] vfs pile 2 (automount work)

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTinZ5ng+hbOHz7DKy82HPqFwYhQvmmbM+ioSWp9x@mail.gmail.com>
Date:	Sun, 16 Jan 2011 13:37:54 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Joachim Eastwood <manabian@...il.com>
Cc:	Al Viro <viro@...iv.linux.org.uk>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [git pull] vfs pile 2 (automount work)

On Sun, Jan 16, 2011 at 1:15 PM, Joachim  Eastwood <manabian@...il.com> wrote:
>
> f03c65993b98eeb909a4012ce7833c5857d74755 - sanitize vfsmount refcounting changes
>
> Breaks my ARM !CONFIG_SMP compile

In fact, any non-SMP compile, it's not ARM-specific.

The simple fix for the build breakage should be to just move the
mnt_longterm thing out of the #ifdef CONFIG_SMP in
include/linux/mount.h. But I do worry that it would cause some count
imbalance, because there are some accesses that are still inside that
CONFIG_SMP case in mntput_no_expire().

Al, please take a look,

                 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/