linux-kernel - Re: [PATCH 1/2] mm: Export vm_committed

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: <20121008004358.GA12342@kroah.com>
Date:	Sun, 7 Oct 2012 17:43:58 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	"K. Y. Srinivasan" <kys@...rosoft.com>
Cc:	linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
	olaf@...fle.de, apw@...onical.com, akpm@...ux-foundation.org,
	andi@...stfloor.org
Subject: Re: [PATCH 1/2] mm: Export vm_committed_as

On Sun, Oct 07, 2012 at 04:59:45PM -0700, K. Y. Srinivasan wrote:
> The policy engine on the host expects the guest to report the
> committed_as. Since this variable is not exported,
> export this symbol.

Why are these symbols not needed by either Xen or KVM or vmware, which
I think all support the same thing, right?

> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -87,6 +87,7 @@ int sysctl_max_map_count __read_mostly = DEFAULT_MAX_MAP_COUNT;
>   * other variables. It can be updated by several CPUs frequently.
>   */
>  struct percpu_counter vm_committed_as ____cacheline_aligned_in_smp;
> +EXPORT_SYMBOL(vm_committed_as);
>  
>  /*
>   * Check that a process has enough memory to allocate a new virtual
> diff --git a/mm/nommu.c b/mm/nommu.c
> index 45131b4..3914b7e 100644
> --- a/mm/nommu.c
> +++ b/mm/nommu.c
> @@ -68,6 +68,7 @@ atomic_long_t mmap_pages_allocated;
>  
>  EXPORT_SYMBOL(mem_map);
>  EXPORT_SYMBOL(num_physpages);
> +EXPORT_SYMBOL(vm_committed_as);

EXPORT_SYMBOL_GPL() for these new ones?

greg k-h
--
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/