From: "eshwar" <eshwar@moschip.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Raj" <inguva@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Write USB Device Driver entry not called
Date: Sat, 23 Oct 2004 07:12:56 +0530 [thread overview]
Message-ID: <004f01c4b8a1$9ee2b6c0$41c8a8c0@Eshwar> (raw)
In-Reply-To: 1097663878.4440.0.camel@localhost.localdomain
I agree but the return value from the vfs_write should not be the -EBADF
(Bad File descriptor) it might be -EACCES (premission denied)... Correct me
if I am wrong...
this can be code in fs/read_write.c vfs_write()
if (!(file->f_mode & FMODE_WRITE))
return -EACCES;
Eshwar
----- Original Message -----
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
To: "eshwar" <eshwar@moschip.com>
Cc: "Raj" <inguva@gmail.com>; "Linux Kernel Mailing List"
<linux-kernel@vger.kernel.org>
Sent: Wednesday, October 13, 2004 4:07 PM
Subject: Re: Write USB Device Driver entry not called
> On Iau, 2004-10-21 at 18:52, eshwar wrote:
> > Open is sucessfull.... I don't think the problem the flags of open
>
> I do. See any book on C/Unix style file opening. For an existing file
> you want
> open("foo", O_flags)
>
> for a new file possibly
>
> open("foo", O_CREAT|o_flags, S_Iblah)
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-10-14 3:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 11:44 Write USB Device Driver entry not called eshwar
2004-10-13 6:15 ` Raj
2004-10-21 17:52 ` eshwar
2004-10-13 6:38 ` Raj
2004-10-13 10:37 ` Alan Cox
2004-10-23 1:42 ` eshwar [this message]
2004-10-14 3:39 ` Raj
2004-10-21 3:54 ` eshwar
2004-10-14 4:19 ` Raj
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='004f01c4b8a1$9ee2b6c0$41c8a8c0@Eshwar' \
--to=eshwar@moschip.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=inguva@gmail.com \
--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