linux-kernel - Re: [discuss] Re: [PATCH for 2.6.18] [8/8] MM: Remove rogue readahead printk

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: <200607301848.56121.ak@suse.de>
Date:	Sun, 30 Jul 2006 18:48:56 +0200
From:	Andi Kleen <ak@...e.de>
To:	discuss@...-64.org
Cc:	Trond Myklebust <trond.myklebust@....uio.no>,
	Andrew Morton <akpm@...l.org>, nate.diller@...il.com,
	torvalds@...l.org, linux-kernel@...r.kernel.org
Subject: Re: [discuss] Re: [PATCH for 2.6.18] [8/8] MM: Remove rogue readahead printk


> Not necessarily. AFAICS, the spam could be triggered by perfectly
> legitimate activity. For instance, someone on the server may have
> revoked your read permissions to the file, or may have deleted it.

I don't think any of this was the case in the cases I saw it.

It would be probably good to investigate post 2.6.18, but for 2.6.18
itself I think removing the printk was the best short term "fix".

> > Do we know why nfs's readpage isn't bringing the page up to date?
> 
> It may be that other lurking issues were also triggering the printk. For
> instance I know of a couple of corner cases in the krb5 privacy code
> that could result in readpage failing. Those issues are being looked
> into.

I don't use kerberos either.

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