On Friday, 15 September 2023 14:25:24 CEST Mauro Carvalho Chehab wrote:
> On Wed, 13 Sep 2023 16:04:10 +0200
> Janusz Krzysztofik wrote:
>
> > On Monday, 11 September 2023 11:01:42 CEST Mauro Carvalho Chehab wrote:
> > > On Fri, 8 Sep 2023 14:32:41 +0200
> > > Janusz Krzysztofik wrote:
> > >
On Wed, 13 Sep 2023 16:04:10 +0200
Janusz Krzysztofik wrote:
> On Monday, 11 September 2023 11:01:42 CEST Mauro Carvalho Chehab wrote:
> > On Fri, 8 Sep 2023 14:32:41 +0200
> > Janusz Krzysztofik wrote:
> >
> > > While reading KTAP data from /dev/kmsg we now ignore interrupt signals
> > >
On Monday, 11 September 2023 11:01:42 CEST Mauro Carvalho Chehab wrote:
> On Fri, 8 Sep 2023 14:32:41 +0200
> Janusz Krzysztofik wrote:
>
> > While reading KTAP data from /dev/kmsg we now ignore interrupt signals
> > that may occur during read() and we continue reading the data. No
> >
On Fri, 8 Sep 2023 14:32:41 +0200
Janusz Krzysztofik wrote:
> While reading KTAP data from /dev/kmsg we now ignore interrupt signals
> that may occur during read() and we continue reading the data. No
> explanation has been provided on what that could be needed for.
The reason is that kunit
While reading KTAP data from /dev/kmsg we now ignore interrupt signals
that may occur during read() and we continue reading the data. No
explanation has been provided on what that could be needed for.
Always return with an error code to the caller when read() fails with
errno == EINTR, so
