so I have this patchset (sent to lkml recently ),
it adds a new struct:
struct _ddebug_info
dyndbg: create and use struct _ddebug_info
this new struct gathers the linker provided vectors/sections:
descs - the vector of descriptors in __dyndbg section.
num_descs - length of
On 04/Aug/2022 13:24, jim.cro...@gmail.com wrote:
> so I have this patchset (sent to lkml recently ),
> it adds a new struct:
> struct _ddebug_info
<...>
> is there some git command magic to work this ?
>
> in a pre-git world, I might try
> perl -pi -e 's/_ddebug_info/_ddebug_stateinfo/g'
Hi,
Le 04/08/2022 à 20:01, Viacheslav Biriukov a écrit :
But what I can't understand is how and where the kernel modifies the
arguments of the write system call and where it collects the return
values of all these restarts, thus the userspace caller ultimately
sees the correct number of
Hello team,
It would be great if someone can help me with a question about blocking
write calls to a pipe and syscall restart logic.
>From my experiments I can see that if the SA_RESTART flag is set, the
kernel (?) restarts the write call if the process gets a signal.
The logic lives in the
Hi Yann,
Thank you for your time and quick response.
You are right. I found what misled me. It was a buffered writer to the
stdout, which did all my syscals restarts and it confused me.
The kernel does what it should, if a portion of data was written, then it's
a partial write, otherwise a
