On 4/7/24 18:13, Masami Hiramatsu (Google) wrote:
On Wed, 3 Apr 2024 16:36:25 +0200
Daniel Borkmann wrote:
On 4/2/24 6:58 PM, Andrii Nakryiko wrote:
On Mon, Apr 1, 2024 at 12:16 PM Kui-Feng Lee wrote:
rethook_find_ret_addr() prints a warning message and returns 0 when the
target task
On Wed, 3 Apr 2024 16:36:25 +0200
Daniel Borkmann wrote:
> On 4/2/24 6:58 PM, Andrii Nakryiko wrote:
> > On Mon, Apr 1, 2024 at 12:16 PM Kui-Feng Lee wrote:
> >>
> >> rethook_find_ret_addr() prints a warning message and returns 0 when the
> >> target task is running and not the "current" task
Kui-Feng Lee wrote:
> rethook_find_ret_addr() prints a warning message and returns 0 when the
> target task is running and not the "current" task to prevent returning an
> incorrect return address. However, this check is incomplete as the target
> task can still transition to the running state
On 4/2/24 6:58 PM, Andrii Nakryiko wrote:
On Mon, Apr 1, 2024 at 12:16 PM Kui-Feng Lee wrote:
rethook_find_ret_addr() prints a warning message and returns 0 when the
target task is running and not the "current" task to prevent returning an
incorrect return address. However, this check is
On Mon, Apr 1, 2024 at 12:16 PM Kui-Feng Lee wrote:
>
> rethook_find_ret_addr() prints a warning message and returns 0 when the
> target task is running and not the "current" task to prevent returning an
> incorrect return address. However, this check is incomplete as the target
> task can still
rethook_find_ret_addr() prints a warning message and returns 0 when the
target task is running and not the "current" task to prevent returning an
incorrect return address. However, this check is incomplete as the target
task can still transition to the running state when finding the return
