From: Raj <inguva@gmail.com>
To: eshwar <eshwar@moschip.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Write USB Device Driver entry not called
Date: Thu, 14 Oct 2004 09:49:16 +0530 [thread overview]
Message-ID: <b2fa632f04101321193488c984@mail.gmail.com> (raw)
In-Reply-To: <011c01c4b721$b7fd96b0$41c8a8c0@Eshwar>
On Thu, 21 Oct 2004 09:24:52 +0530, eshwar <eshwar@moschip.com> wrote:
> if I modify the code like this
>
> char abc;
> if(read(fd,&abc,1) < 0)
> perror("read to bar failed: ");
> close(fd);
>
> Which will be sucess... This intern states that my file descriptor is right
> .... but write returns EBADF... both are contradicting statements....
It's this simple. File was opened for Read-Only. So for vfs_read it is
a 'good' file
descriptor. And for vfs_write it is a 'BAD' file descriptor.
--
######
raj
######
prev parent reply other threads:[~2004-10-14 4:20 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
2004-10-14 3:39 ` Raj
2004-10-21 3:54 ` eshwar
2004-10-14 4:19 ` Raj [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=b2fa632f04101321193488c984@mail.gmail.com \
--to=inguva@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eshwar@moschip.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