> 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
