All of lore.kernel.org
 help / color / mirror / Atom feed
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:09:36 +0530	[thread overview]
Message-ID: <b2fa632f041013203968418d9f@mail.gmail.com> (raw)
In-Reply-To: <004f01c4b8a1$9ee2b6c0$41c8a8c0@Eshwar>

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
######

  reply	other threads:[~2004-10-14  3:39 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 [this message]
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=b2fa632f041013203968418d9f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.