linux-kernel - Re: [patch 4/21] mm: refund memory for a locked buffer

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

Date:	Wed, 1 Apr 2009 02:23:34 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Markus Metzger <markus.t.metzger@...el.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, tglx@...utronix.de,
	hpa@...or.com, markus.t.metzger@...il.com, roland@...hat.com,
	eranian@...glemail.com, juan.villacis@...el.com,
	ak@...ux.jf.intel.com
Subject: Re: [patch 4/21] mm: refund memory for a locked buffer

On 03/31, Markus Metzger wrote:
>
> -void release_locked_buffer(void *buffer, size_t size)
> +void refund_locked_buffer_memory(struct mm_struct *mm, size_t size)

Hmm. Again, this is not bisect friendly, afaoics the kernel can't be
compiled with this patch. Irenames release_locked_buffer(), but we still
have callers (fixed by the next patches).

>  void free_locked_buffer(void *buffer, size_t size)
>  {
> -	release_locked_buffer(buffer, size);
> -
> +	refund_locked_buffer_memory(current->mm, size);
>  	kfree(buffer);
>  }

And this one has no callers after the next patches?

Oleg.

--
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/