From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Andrew Morton <akpm@osdl.org>,
nate.diller@gmail.com, torvalds@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: [PATCH for 2.6.18] [8/8] MM: Remove rogue readahead printk
Date: Sun, 30 Jul 2006 18:48:56 +0200 [thread overview]
Message-ID: <200607301848.56121.ak@suse.de> (raw)
In-Reply-To: <1154275941.5784.131.camel@localhost>
> 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
prev parent reply other threads:[~2006-07-30 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 19:42 [PATCH for 2.6.18] [8/8] MM: Remove rogue readahead printk Andi Kleen
2006-07-29 21:14 ` Trond Myklebust
2006-07-30 1:04 ` Nate Diller
2006-07-30 4:22 ` Trond Myklebust
2006-07-30 6:26 ` Andrew Morton
2006-07-30 16:12 ` Trond Myklebust
2006-07-30 16:48 ` Andi Kleen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200607301848.56121.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nate.diller@gmail.com \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox