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

Andi Kleen
2006-07-30T17:00:30Z

> 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