public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Robin Getz <rgetz@blackfin.uclinux.org>
Cc: viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: debugfs & vfs file permission issue?
Date: Mon, 5 Jan 2009 21:48:58 -0800	[thread overview]
Message-ID: <20090106054858.GA9040@suse.de> (raw)
In-Reply-To: <200901052157.07306.rgetz@blackfin.uclinux.org>

On Mon, Jan 05, 2009 at 09:57:07PM -0500, Robin Getz wrote:
> On 2.6.28-rc2, If I create a debugfs file with
> 
>     debugfs_create_x16("SPORT1_TX", 0200 , parent, 0xFFC00910);

Um, are you are passing in a pointer to a known memory location
properly?  Why would it be ok for the kernel to directly read that
location?

> Although the file shows up as write only (no read):
> 
> root:/> ls -l /sys/kernel/debug/blackfin/SPORT/SPORT1_TX
> --w-------    1 root     root            0 Jan  1  
> 2007 /sys/kernel/debug/blackfin/SPORT/SPORT1_TX
> 
> root:/> cat /sys/kernel/debug/blackfin/SPORT/SPORT1_TX
> 
> Still works - and causes the read to occur, which crashes :(

You're root, you can do anything :)


> System MMR Error
> .....
> 
> I can do the same to any file by hand too.
> 
> root:/> ls -l /sys/kernel/debug/blackfin/RTC/RTC_STAT
> -rw-------    1 root     root            0 Jan  1  
> 2007 /sys/kernel/debug/blackfin/RTC/RTC_STAT
> root:/> cat /sys/kernel/debug/blackfin/RTC/RTC_STAT
> 0xb81d3181
> root:/> chmod 0000 /sys/kernel/debug/blackfin/RTC/RTC_STAT
> root:/> ls -l /sys/kernel/debug/blackfin/RTC/RTC_STAT
> ----------    1 root     root            0 Jan  1  
> 2007 /sys/kernel/debug/blackfin/RTC/RTC_STAT
> root:/> cat /sys/kernel/debug/blackfin/RTC/RTC_STAT
> 0xb81d31a5
> 
> ?
> 
> From what I can tell from the call trace:
> 
> cat (userspace)
>   system_call (into kernel)
>     sys_read
>       vfs_read
>         simple_attr_read
>           debugfs_u16_get
>             crash
> 
> 
> I would think that vfs_read should fail....
> 
> ./fs/read_write.c:vfs_read()
> 
>         if (!(file->f_mode & FMODE_READ))
>                 return -EBADF; 

I think f_mode is the mode of the file descriptor, not the inode you are
looking at.  You told userspace to open the file in read mode, right?
So this is why it passes.

Hope this helps,

greg k-h

  reply	other threads:[~2009-01-06  5:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06  2:57 debugfs & vfs file permission issue? Robin Getz
2009-01-06  5:48 ` Greg KH [this message]
2009-01-06  5:54   ` Mike Frysinger
2009-01-06  6:19     ` Greg KH
2009-01-06  6:32       ` Mike Frysinger
2009-01-06 12:05         ` Robin Getz
2009-01-06 15:12           ` Robin Getz
2009-01-06 15:20             ` Mike Frysinger
2009-01-06 21:20               ` Robin Getz
2009-01-06 23:11             ` Greg KH
2009-01-07  3:30               ` Robin Getz
2009-01-25 21:34             ` Greg KH
2009-06-02  7:00               ` [PATCH] debugfs: use specified mode to possibly mark files read/write only Mike Frysinger
2009-06-02 23:23                 ` Greg KH

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=20090106054858.GA9040@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=viro@zeniv.linux.org.uk \
    /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