From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: tvrtko.ursulin@sophos.com
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
urban@teststation.com
Subject: Re: [BUG ?] smbfs open always succeeds
Date: Wed, 8 Dec 2004 19:32:20 -0200 [thread overview]
Message-ID: <20041208213220.GE2348@dmt.cyclades> (raw)
In-Reply-To: <OF3F6FA812.9B17E2B3-ON80256F64.005AD229-80256F64.005AFF55@sophos.com>
On Wed, Dec 08, 2004 at 04:33:56PM +0000, tvrtko.ursulin@sophos.com wrote:
> >Not saying that smbfs is right, just explaining that it _might_ be right.
> >
> >Urban, did you see the thread?
>
> Urban seems to be MIA. Or on a long holiday. :) What shall we do?
It seems Andrew applied this to the -mm tree.
smb_file_open-retval-fix.patch
From: <tvrtko.ursulin@sophos.com>
Correctly propagate the return value from smb_open().
Signed-off-by: Andrew Morton <akpm@osdl.org>
---
25-akpm/fs/smbfs/file.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/smbfs/file.c~smb_file_open-retval-fix fs/smbfs/file.c
--- 25/fs/smbfs/file.c~smb_file_open-retval-fix Mon Nov 29 13:08:30 2004
+++ 25-akpm/fs/smbfs/file.c Mon Nov 29 13:08:38 2004
@@ -363,7 +363,7 @@ smb_file_open(struct inode *inode, struc
SMB_I(inode)->openers++;
out:
unlock_kernel();
- return 0;
+ return result;
}
next prev parent reply other threads:[~2004-12-09 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 16:33 [BUG ?] smbfs open always succeeds tvrtko.ursulin
2004-12-08 21:32 ` Marcelo Tosatti [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-10 11:06 tvrtko.ursulin
2004-12-11 21:24 ` Marcelo Tosatti
2004-12-12 0:20 ` Gene Heskett
2004-11-30 15:19 tvrtko.ursulin
2004-11-30 15:43 ` Linus Torvalds
2004-11-29 11:11 tvrtko.ursulin
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=20041208213220.GE2348@dmt.cyclades \
--to=marcelo.tosatti@cyclades.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=tvrtko.ursulin@sophos.com \
--cc=urban@teststation.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