Re: [PATCH net-next] tools: bpf: handle long path in jit disasm

2017-11-02 Thread David Miller
From: "Rustad, Mark D" Date: Thu, 2 Nov 2017 21:19:44 + > >> On Nov 2, 2017, at 1:09 AM, Prashant Bhole >> wrote: >> >> Use PATH_MAX instead of hardcoded array size 256 >> >> Signed-off-by: Prashant Bhole ... >> static void get_asm_insns(uint8_t *image, size_t len, int opcodes) >> { >>

Re: [PATCH net-next] tools: bpf: handle long path in jit disasm

2017-11-02 Thread Rustad, Mark D
> On Nov 2, 2017, at 1:09 AM, Prashant Bhole > wrote: > > Use PATH_MAX instead of hardcoded array size 256 > > Signed-off-by: Prashant Bhole > --- > tools/bpf/bpf_jit_disasm.c | 3 ++- > tools/bpf/bpftool/jit_disasm.c | 3 ++- > 2 files changed, 4 insertions(+), 2 deletions(-) > > diff --g

Re: [PATCH net-next] tools: bpf: handle long path in jit disasm

2017-11-02 Thread David Miller
From: Prashant Bhole Date: Thu, 2 Nov 2017 17:09:45 +0900 > Use PATH_MAX instead of hardcoded array size 256 > > Signed-off-by: Prashant Bhole Applied, thank you.

[PATCH net-next] tools: bpf: handle long path in jit disasm

2017-11-02 Thread Prashant Bhole
Use PATH_MAX instead of hardcoded array size 256 Signed-off-by: Prashant Bhole --- tools/bpf/bpf_jit_disasm.c | 3 ++- tools/bpf/bpftool/jit_disasm.c | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/tools/bpf/bpf_jit_disasm.c b/tools/bpf/bpf_jit_disasm.c index 422d9abd