[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZJP_qPeJ37H4qhEN@yuki>
Date: Thu, 22 Jun 2023 10:00:40 +0200
From: Cyril Hrubis <chrubis@...e.cz>
To: Niklas Cassel <Niklas.Cassel@....com>
Cc: Damien Le Moal <dlemoal@...nel.org>,
kernel test robot <oliver.sang@...el.com>,
"lkp@...el.com" <lkp@...el.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
Linux Memory Management List <linux-mm@...ck.org>,
Hannes Reinecke <hare@...e.de>,
"oe-lkp@...ts.linux.dev" <oe-lkp@...ts.linux.dev>,
Christoph Hellwig <hch@....de>,
"ltp@...ts.linux.it" <ltp@...ts.linux.it>,
Petr Vorel <pvorel@...e.cz>
Subject: Re: [LTP] [linux-next:master] [scsi] eca2040972:
ltp.ioprio_set03.fail
Hi!
> But... shouldn't the installed uapi headers match the running kernel?
Genearlly this is tough nut to crack. It's nearly impossible for headers
to actually match the running kernel in testing environments, since
quite often the testsuite is compiled beforehand and only retrieved,
since recompiling for each testrun is wasting too many cycles. I would
say that the best we can have is that UAPI headers shouldn't be newer
than running kernel.
--
Cyril Hrubis
chrubis@...e.cz
Powered by blists - more mailing lists