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]
Message-ID: <alpine.LNX.2.00.1106271226260.11049@pobox.suse.cz>
Date:	Mon, 27 Jun 2011 12:26:42 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Jesper Juhl <jj@...osbits.net>
Cc:	Torbjörn Svensson 
	<azoff@...nskalinuxforeningen.se>,
	Dan Magenheimer <dan.magenheimer@...cle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Corrected a small typo in help text for
 CONFIG_CLEANCACHE

On Sun, 26 Jun 2011, Jesper Juhl wrote:

> > Signed-of-by: Torbjörn Svensson <azoff@...nskalinuxforeningen.se>
> > ---
> >  mm/Kconfig |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/mm/Kconfig b/mm/Kconfig
> > index 8ca47a5..f2f1ca1 100644
> > --- a/mm/Kconfig
> > +++ b/mm/Kconfig
> > @@ -356,7 +356,7 @@ config CLEANCACHE
> >  	  for clean pages that the kernel's pageframe replacement algorithm
> >  	  (PFRA) would like to keep around, but can't since there isn't enough
> >  	  memory.  So when the PFRA "evicts" a page, it first attempts to use
> > -	  cleancacne code to put the data contained in that page into
> > +	  cleancache code to put the data contained in that page into
> >  	  "transcendent memory", memory that is not directly accessible or
> >  	  addressable by the kernel and is of unknown and possibly
> >  	  time-varying size.  And when a cleancache-enabled
> > 
> For what it's worth;
> 
> Reviewed-by: Jesper Juhl <jj@...osbits.net>

Already fixed in my tree by 140a1ef2f.

-- 
Jiri Kosina
SUSE Labs
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ