From: Mike Fedyk <mfedyk@matchmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6][smbfs] smb_open & smb_readpage_sync errors in kernel log
Date: Mon, 19 Jan 2004 22:37:49 -0800 [thread overview]
Message-ID: <20040120063749.GA23765@srv-lnx2600.matchmail.com> (raw)
In-Reply-To: <20040119202243.3d0aa60a.akpm@osdl.org>
On Mon, Jan 19, 2004 at 08:22:43PM -0800, Andrew Morton wrote:
> Mike Fedyk <mfedyk@matchmail.com> wrote:
> >
> > I've been getting these error messages in my kernel forever, I think even
> > with 2.2 kernels, and it's still there in 2.6:
> >
> > smb_open: config/SAM open failed, result=-26
> > smb_readpage_sync: config/SAM open failed, error=-26
> >
> > It does this for several locked system files on the windows machines.
> >
> > This happens during a find command run on the mounted share from one of my
> > scripts that compares file dates.
> >
> > Can these printk calls be removed?
>
> I think so. We don't want to allow unprivileged users to spam the
> logfiles.
Great!
Thanks Andrew.
prev parent reply other threads:[~2004-01-20 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 18:44 Mike Fedyk
2004-01-20 4:22 ` Andrew Morton
2004-01-20 6:37 ` Mike Fedyk [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=20040120063749.GA23765@srv-lnx2600.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®