On 2/3/2022 5:16 AM, Vishal Goel wrote:
Currently tracer process info is printed in object field in
smack error log for ptrace check which is wrong.
Object process should print the tracee process info.
Tracee info is not printed in the smack error logs.
So it is not possible to debug
Currently tracer process info is printed in object field in
smack error log for ptrace check which is wrong.
Object process should print the tracee process info.
Tracee info is not printed in the smack error logs.
So it is not possible to debug the
> Currently tracer process info is printed in object field in
> smack error log for ptrace check which is wrong.
> Object process should print the tracee process info.
> Tracee info is not printed in the smack error logs.
> So it is not possible to debug the ptrace smack
On 2/2/2022 7:20 AM, Paul Moore wrote:
On Wed, Feb 2, 2022 at 5:38 AM Vishal Goel wrote:
Currently tracer process info is printed in object field in
smack error log for ptrace check which is wrong.
Object process should print the tracee process info.
Tracee info is not printed in the smack
On Wed, Feb 2, 2022 at 5:38 AM Vishal Goel wrote:
> > Currently tracer process info is printed in object field in
> > smack error log for ptrace check which is wrong.
> > Object process should print the tracee process info.
> > Tracee info is not printed in the smack error logs.
>
>>> Currently tracer process info is printed in object field in
>>> smack error log for ptrace check which is wrong.
>>> Object process should print the tracee process info.
>>> Tracee info is not printed in the smack error logs.
>>> So it is not possible to debug the ptrace smack issues.
>>>
>>>
On Tue, Feb 1, 2022 at 2:55 AM Vishal Goel wrote:
> >>> Currently tracer process info is printed in object field in
> >>> smack error log for ptrace check which is wrong.
> >>> Object process should print the tracee process info.
> >>> Tracee info is not printed in the smack error logs.
> >>> So
On Fri, Jan 28, 2022 at 11:25 AM Casey Schaufler wrote:
> On 12/20/2021 2:13 AM, Vishal Goel wrote:
> > Currently tracer process info is printed in object field in
> > smack error log for ptrace check which is wrong.
> > Object process should print the tracee process info.
> > Tracee info is not
On 12/20/2021 2:13 AM, Vishal Goel wrote:
Currently tracer process info is printed in object field in
smack error log for ptrace check which is wrong.
Object process should print the tracee process info.
Tracee info is not printed in the smack error logs.
So it is not possible to debug the
Hi,
> Signed-off-by: Vishal Goel Could you include a permissive license with this code?>I'd like to add it or a derivative of it to the Smack test suite.
You can use below license:-
#
On 12/21/2021 5:12 AM, Vishal Goel wrote:
Hi,
Signed-off-by: Vishal Goel
What test case do you have that generates these records?
Could you include a permissive license with this code?
I'd like to add it or a derivative of it to the Smack test suite.
Test case for 1st log:-
void main(int
Hi,
>>> Signed-off-by: Vishal Goel
>
> What test case do you have that generates these records?
Test case for 1st log:-
void main(int argc,char *argv[])
{
int pid;
if (argc < 2) {
printf("enter pid of the tracee process\n");
exit(0);
}
On 12/20/2021 8:41 AM, Casey Schaufler wrote:
On 12/20/2021 2:13 AM, Vishal Goel wrote:
Currently tracer process info is printed in object field in
smack error log for ptrace check which is wrong.
Object process should print the tracee process info.
Tracee info is not printed in the smack error
On 12/20/2021 2:13 AM, Vishal Goel wrote:
Currently tracer process info is printed in object field in
smack error log for ptrace check which is wrong.
Object process should print the tracee process info.
Tracee info is not printed in the smack error logs.
So it is not possible to debug the
14 matches
Mail list logo