On Fri, Mar 22, 2019 at 03:02:11PM +, Srinivas Kandagatla wrote:
>
>
> On 20/03/2019 17:50, Gaurav Kohli wrote:
> >
> > > Is root only option not helping you in this case?
> > Yes we want to protect at root level as well, i mean it is better if we
> > can avoid exposing to userspace at all.
Hi Srinivas,
Thanks for the patch, Can you please merge , So will cherry pick the same.
Regards
Gaurav
On 3/25/2019 11:45 AM, Gaurav Kohli wrote:
On 3/22/2019 11:42 PM, Gaurav Kohli wrote:
Hi Srinivas,
Thanks for the patch, Something like this only i have tested in the
morning, instead
On 3/22/2019 11:42 PM, Gaurav Kohli wrote:
Hi Srinivas,
Thanks for the patch, Something like this only i have tested in the
morning, instead of unused, i have put dev group inside config as well.
We will test the exact patch and update the same.
Regards
Gaurav
On 3/22/2019 8:32 PM,
Hi Srinivas,
Thanks for the patch, Something like this only i have tested in the
morning, instead of unused, i have put dev group inside config as well.
We will test the exact patch and update the same.
Regards
Gaurav
On 3/22/2019 8:32 PM, Srinivas Kandagatla wrote:
On 20/03/2019 17:50,
On 20/03/2019 17:50, Gaurav Kohli wrote:
Is root only option not helping you in this case?
Yes we want to protect at root level as well, i mean it is better if we
can avoid exposing to userspace at all.
Can you try below patch!
We could go down the route of adding new config option
On 20/03/2019 18:50, Gaurav Kohli wrote:
> On 3/20/2019 9:56 PM, Srinivas Kandagatla wrote:
>
>> Am guessing these are some kind of keys or something that you do not
>> want user to see.
>
> Yes exactly, there are certain keys or even certain bit that we don't
> want to expose to user.
>
>>
On 3/20/2019 9:56 PM, Srinivas Kandagatla wrote:
On 20/03/2019 15:50, Gaurav Kohli wrote:
On 3/20/2019 8:04 PM, Srinivas Kandagatla wrote:
On 17/03/2019 14:12, Gaurav Kohli wrote:
Current nvmem framework allows user space to read all register space
populated by nvmem binary file, In
On 20/03/2019 15:50, Gaurav Kohli wrote:
On 3/20/2019 8:04 PM, Srinivas Kandagatla wrote:
On 17/03/2019 14:12, Gaurav Kohli wrote:
Current nvmem framework allows user space to read all register space
populated by nvmem binary file, In case we don't want to expose value
of registers to
On 3/20/2019 8:04 PM, Srinivas Kandagatla wrote:
On 17/03/2019 14:12, Gaurav Kohli wrote:
Current nvmem framework allows user space to read all register space
populated by nvmem binary file, In case we don't want to expose value
of registers to userspace and only want kernel space to read
On 17/03/2019 14:12, Gaurav Kohli wrote:
Current nvmem framework allows user space to read all register space
populated by nvmem binary file, In case we don't want to expose value
of registers to userspace and only want kernel space to read cell
value from nvmem_cell_read_u32.
To protect the
Current nvmem framework allows user space to read all register space
populated by nvmem binary file, In case we don't want to expose value
of registers to userspace and only want kernel space to read cell
value from nvmem_cell_read_u32.
To protect the same, Add no-read-write property to prevent
11 matches
Mail list logo
