From: Gobinda Charan Maji <gobinda.cemk07@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Stricter module param and sysfs permission checks
Date: Thu, 26 Jun 2014 02:54:59 +0000 (UTC) [thread overview]
Message-ID: <loom.20140626T044310-195@post.gmane.org> (raw)
In-Reply-To: <loom.20140618T155046-940@post.gmane.org>
Gobinda Charan Maji <gobinda.cemk07 <at> gmail.com> writes:
>
> Hi All,
>
> As per the newly added restriction (User perms >= group perms >= other
> perms) is concerned, there is an inconsistency in the permission. Say for
> example, permission value is "0432". Here User has only READ permission
> whereas Group has both WRITE and EXECUTE permission and Other has WRITE
> permission. I think it is not good to give Group and Other at least WRITE
> permission whereas User itself has no WRITE permission.
>
> May be, it's better to check those three permissions bit wise rather than
as
> a whole. Please rethink about my point and let me know your opinion.
>
> Thanks,
> Gobinda
>
>
Hi All,
I could not get any response yet.
Hi Rusty,
Please at least give me a reply even if my concept seems to be incorrect to
you.
Thanks in advance,
Gobinda
next prev parent reply other threads:[~2014-06-26 2:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 17:31 [PATCH] virtio-blk: make the queue depth configurable Theodore Ts'o
2014-03-14 17:38 ` Joe Perches
2014-03-14 18:02 ` Theodore Ts'o
2014-03-17 3:55 ` Rusty Russell
2014-03-17 5:00 ` Joe Perches
2014-03-17 7:26 ` Joe Perches
2014-03-19 6:37 ` Rusty Russell
2014-03-19 6:50 ` Joe Perches
2014-03-20 3:13 ` Stricter module param and sysfs permission checks Rusty Russell
2014-03-20 4:27 ` Dave Jones
2014-03-20 9:15 ` Alexey Dobriyan
2014-03-20 16:28 ` Robert Jarzmik
2014-06-18 15:07 ` Gobinda Charan Maji
2014-06-26 2:54 ` Gobinda Charan Maji [this message]
2014-07-03 5:52 ` Gobinda Charan Maji
2015-04-28 14:02 ` Gobinda Charan Maji
2014-03-19 16:07 ` [PATCH] virtio-blk: make the queue depth configurable Greg Kroah-Hartman
2014-03-19 16:57 ` Bjorn Helgaas
2014-03-19 17:31 ` Joe Perches
2014-03-20 3:35 ` Rusty Russell
2014-03-20 2:50 ` Rusty Russell
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=loom.20140626T044310-195@post.gmane.org \
--to=gobinda.cemk07@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