Le 06/06/2017 à 13:00, Michael Ellerman a écrit :
christophe leroy writes:
Le 05/06/2017 à 12:45, Michael Ellerman a écrit :
Christophe LEROY writes:
Le 02/06/2017 à 11:26, Michael Ellerman a écrit :
Christophe Leroy
Le 06/06/2017 à 13:00, Michael Ellerman a écrit :
christophe leroy writes:
Le 05/06/2017 à 12:45, Michael Ellerman a écrit :
Christophe LEROY writes:
Le 02/06/2017 à 11:26, Michael Ellerman a écrit :
Christophe Leroy writes:
Only the get_user() in store_updates_sp() has to be done
christophe leroy writes:
> Le 05/06/2017 à 12:45, Michael Ellerman a écrit :
>> Christophe LEROY writes:
>>
>>> Le 02/06/2017 à 11:26, Michael Ellerman a écrit :
Christophe Leroy writes:
> Only the
christophe leroy writes:
> Le 05/06/2017 à 12:45, Michael Ellerman a écrit :
>> Christophe LEROY writes:
>>
>>> Le 02/06/2017 à 11:26, Michael Ellerman a écrit :
Christophe Leroy writes:
> Only the get_user() in store_updates_sp() has to be done outside
> the mm semaphore.
Le 05/06/2017 à 12:45, Michael Ellerman a écrit :
Christophe LEROY writes:
Le 02/06/2017 à 11:26, Michael Ellerman a écrit :
Christophe Leroy writes:
Only the get_user() in store_updates_sp() has to be done outside
the mm semaphore. All
Le 05/06/2017 à 12:45, Michael Ellerman a écrit :
Christophe LEROY writes:
Le 02/06/2017 à 11:26, Michael Ellerman a écrit :
Christophe Leroy writes:
Only the get_user() in store_updates_sp() has to be done outside
the mm semaphore. All the comparison can be done within the semaphore,
Christophe LEROY writes:
> Le 02/06/2017 à 14:11, Benjamin Herrenschmidt a écrit :
>> On Fri, 2017-06-02 at 11:39 +0200, Christophe LEROY wrote:
>>> The difference between get_user() and __get_user() is that get_user()
>>> performs an access_ok() in addition.
>>>
>>>
Christophe LEROY writes:
> Le 02/06/2017 à 14:11, Benjamin Herrenschmidt a écrit :
>> On Fri, 2017-06-02 at 11:39 +0200, Christophe LEROY wrote:
>>> The difference between get_user() and __get_user() is that get_user()
>>> performs an access_ok() in addition.
>>>
>>> Doesn't access_ok() only
Christophe LEROY writes:
> Le 02/06/2017 à 11:26, Michael Ellerman a écrit :
>> Christophe Leroy writes:
>>
>>> Only the get_user() in store_updates_sp() has to be done outside
>>> the mm semaphore. All the comparison can be done within the
Christophe LEROY writes:
> Le 02/06/2017 à 11:26, Michael Ellerman a écrit :
>> Christophe Leroy writes:
>>
>>> Only the get_user() in store_updates_sp() has to be done outside
>>> the mm semaphore. All the comparison can be done within the semaphore,
>>> so only when really needed.
>>>
>>> As
Le 02/06/2017 à 14:11, Benjamin Herrenschmidt a écrit :
On Fri, 2017-06-02 at 11:39 +0200, Christophe LEROY wrote:
The difference between get_user() and __get_user() is that get_user()
performs an access_ok() in addition.
Doesn't access_ok() only checks whether addr is below TASK_SIZE to
Le 02/06/2017 à 14:11, Benjamin Herrenschmidt a écrit :
On Fri, 2017-06-02 at 11:39 +0200, Christophe LEROY wrote:
The difference between get_user() and __get_user() is that get_user()
performs an access_ok() in addition.
Doesn't access_ok() only checks whether addr is below TASK_SIZE to
On Fri, 2017-06-02 at 11:39 +0200, Christophe LEROY wrote:
> The difference between get_user() and __get_user() is that get_user()
> performs an access_ok() in addition.
>
> Doesn't access_ok() only checks whether addr is below TASK_SIZE to
> ensure it is a valid user address ?
Do you have a
On Fri, 2017-06-02 at 11:39 +0200, Christophe LEROY wrote:
> The difference between get_user() and __get_user() is that get_user()
> performs an access_ok() in addition.
>
> Doesn't access_ok() only checks whether addr is below TASK_SIZE to
> ensure it is a valid user address ?
Do you have a
Le 02/06/2017 à 11:26, Michael Ellerman a écrit :
Christophe Leroy writes:
Only the get_user() in store_updates_sp() has to be done outside
the mm semaphore. All the comparison can be done within the semaphore,
so only when really needed.
As we got a DSI exception,
Le 02/06/2017 à 11:26, Michael Ellerman a écrit :
Christophe Leroy writes:
Only the get_user() in store_updates_sp() has to be done outside
the mm semaphore. All the comparison can be done within the semaphore,
so only when really needed.
As we got a DSI exception, the address pointed by
Christophe Leroy writes:
> Only the get_user() in store_updates_sp() has to be done outside
> the mm semaphore. All the comparison can be done within the semaphore,
> so only when really needed.
>
> As we got a DSI exception, the address pointed by regs->nip is
>
Christophe Leroy writes:
> Only the get_user() in store_updates_sp() has to be done outside
> the mm semaphore. All the comparison can be done within the semaphore,
> so only when really needed.
>
> As we got a DSI exception, the address pointed by regs->nip is
> obviously valid, otherwise we
Christophe Leroy writes:
> Only the get_user() in store_updates_sp() has to be done outside
> the mm semaphore. All the comparison can be done within the semaphore,
> so only when really needed.
>
> As we got a DSI exception, the address pointed by regs->nip is
>
Christophe Leroy writes:
> Only the get_user() in store_updates_sp() has to be done outside
> the mm semaphore. All the comparison can be done within the semaphore,
> so only when really needed.
>
> As we got a DSI exception, the address pointed by regs->nip is
> obviously valid, otherwise we
Only the get_user() in store_updates_sp() has to be done outside
the mm semaphore. All the comparison can be done within the semaphore,
so only when really needed.
As we got a DSI exception, the address pointed by regs->nip is
obviously valid, otherwise we would have had a instruction exception.
Only the get_user() in store_updates_sp() has to be done outside
the mm semaphore. All the comparison can be done within the semaphore,
so only when really needed.
As we got a DSI exception, the address pointed by regs->nip is
obviously valid, otherwise we would have had a instruction exception.
22 matches
Mail list logo