>>> On 04.03.16 at 09:21, wrote:
> In the course of backporting other XSA fixes to very old trees I had
> noticed that the XSA-155 had shrunk to just the change to
> xen/include/public/io/ring.h at some point, which didn't seem right.
> Clearly up to 4.5 the situation of blktap1 is the same as tha
>>> On 04.03.16 at 15:09, wrote:
> On Fri, Mar 04, 2016 at 01:21:19AM -0700, Jan Beulich wrote:
>> In the course of backporting other XSA fixes to very old trees I had
>> noticed that the XSA-155 had shrunk to just the change to
>> xen/include/public/io/ring.h at some point, which didn't seem righ
On Fri, Mar 04, 2016 at 01:21:19AM -0700, Jan Beulich wrote:
> In the course of backporting other XSA fixes to very old trees I had
> noticed that the XSA-155 had shrunk to just the change to
> xen/include/public/io/ring.h at some point, which didn't seem right.
> Clearly up to 4.5 the situation of
In the course of backporting other XSA fixes to very old trees I had
noticed that the XSA-155 had shrunk to just the change to
xen/include/public/io/ring.h at some point, which didn't seem right.
Clearly up to 4.5 the situation of blktap1 is the same as that of
blktap2, i.e. one would think it also
