From: Andrew Morton <akpm@osdl.org>
To: Mike Fedyk <mfedyk@matchmail.com>
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 20:22:43 -0800 [thread overview]
Message-ID: <20040119202243.3d0aa60a.akpm@osdl.org> (raw)
In-Reply-To: <20040119184435.GT8664@srv-lnx2600.matchmail.com>
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.
fs/smbfs/file.c | 5 +----
fs/smbfs/proc.c | 5 +----
2 files changed, 2 insertions(+), 8 deletions(-)
diff -puN fs/smbfs/proc.c~smbfs-fix-noisiness fs/smbfs/proc.c
--- 25/fs/smbfs/proc.c~smbfs-fix-noisiness 2004-01-19 20:18:16.000000000 -0800
+++ 25-akpm/fs/smbfs/proc.c 2004-01-19 20:18:16.000000000 -0800
@@ -1181,11 +1181,8 @@ smb_open(struct dentry *dentry, int wish
result = 0;
if (!smb_is_open(inode))
result = smb_proc_open(server, dentry, wish);
- if (result) {
- PARANOIA("%s/%s open failed, result=%d\n",
- DENTRY_PATH(dentry), result);
+ if (result)
goto out;
- }
/*
* A successful open means the path is still valid ...
*/
diff -puN fs/smbfs/file.c~smbfs-fix-noisiness fs/smbfs/file.c
--- 25/fs/smbfs/file.c~smbfs-fix-noisiness 2004-01-19 20:22:21.000000000 -0800
+++ 25-akpm/fs/smbfs/file.c 2004-01-19 20:22:23.000000000 -0800
@@ -64,11 +64,8 @@ smb_readpage_sync(struct dentry *dentry,
DENTRY_PATH(dentry), count, offset, rsize);
result = smb_open(dentry, SMB_O_RDONLY);
- if (result < 0) {
- PARANOIA("%s/%s open failed, error=%d\n",
- DENTRY_PATH(dentry), result);
+ if (result < 0)
goto io_error;
- }
do {
if (count < rsize)
_
next prev parent reply other threads:[~2004-01-20 4:22 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 [this message]
2004-01-20 6:37 ` Mike Fedyk
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=20040119202243.3d0aa60a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
/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
Powered by JetHome