From: "eshwar" <eshwar@moschip.com>
To: "Raj" <inguva@gmail.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, 21 Oct 2004 09:24:52 +0530 [thread overview]
Message-ID: <011c01c4b721$b7fd96b0$41c8a8c0@Eshwar> (raw)
In-Reply-To: <b2fa632f041013203968418d9f@mail.gmail.com>
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....
Eshwar
----- Original Message -----
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>
Sent: Thursday, October 14, 2004 9:09 AM
Subject: Re: Write USB Device Driver entry not called
> On Sat, 23 Oct 2004 07:12:56 +0530, eshwar <eshwar@moschip.com> wrote:
> > 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;
>
> Wrong. You are confused between file perms & mode of access to files.
> If you cannot open a file due to insufficient perms, then EACCESS is
> what you get.
> If you opened a file for reading, but you tried to write, the you get a
EBADF.
>
> Run the following code, after you create two files, 'foo' ( perms 0400
> ) and 'bar' ( 0700 ).
>
> #include <fcntl.h>
>
> int main()
> {
> int fd;
>
> fd = open("foo",O_WRONLY);
>
> if(fd < 0)
> perror("Opening foo:");
> else
> close (fd);
>
> fd = open("bar",O_RDONLY);
>
> if(fd < 0)
> perror("Opening bar: ");
> else {
> if(write(fd,'a',1) < 0)
> perror("Write to bar failed: ");
> close(fd);
> }
>
> }
>
> Output would be:
> Opening foo:: Permission denied
> Write to bar failed: : Bad file descriptor
> --
> ######
> raj
> ######
> -
> 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 4:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 11:44 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 [this message]
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='011c01c4b721$b7fd96b0$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
Powered by JetHome