If the network configuration strings are passed as a combination of IPv and
IPv6 addresses, the current KVP daemon doesnot handle it for the keyfile
configuration format.
With these changes, the keyfile config generation logic scans through the
list twice to generate IPv4 and IPv6 sections for the
On Tue, 12 Mar 2024, Shradha Gupta wrote:
> If the network configuration strings are passed as a combination of IPv and
> IPv6 addresses, the current KVP daemon doesnot handle it for the keyfile
> configuration format.
> With these changes, the keyfile config generation logic scans through the
On Mon, Mar 11, 2024 at 09:15:53AM -0700, mhkelle...@gmail.com wrote:
> From: Michael Kelley
> Michael Kelley (1):
> Drivers: hv: vmbus: Don't free ring buffers that couldn't be
> re-encrypted
>
> Rick Edgecombe (4):
> Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails
> Dri
On 3/11/24 9:15 AM, mhkelle...@gmail.com wrote:
> From: Michael Kelley
>
> In CoCo VMs it is possible for the untrusted host to cause
> set_memory_encrypted() or set_memory_decrypted() to fail such that an
> error is returned and the resulting memory is shared. Callers need to
> take care to han
On 3/11/24 11:07 PM, Michael Kelley wrote:
> From: Kuppuswamy Sathyanarayanan
>> On 3/11/24 9:15 AM, mhkelle...@gmail.com wrote:
>>> From: Rick Edgecombe
>>>
>>> In CoCo VMs it is possible for the untrusted host to cause
>>> set_memory_encrypted() or set_memory_decrypted() to fail such that an
On 3/12/2024 5:38 AM, Shradha Gupta wrote:
> If the network configuration strings are passed as a combination of IPv and
*IPv4*
> IPv6 addresses, the current KVP daemon doesnot handle it for the keyfile
> Subject: [PATCH 1/6] Drivers: hv: vmbus: Add utility function for querying
> ring size
>
> Add a function to query for the preferred ring buffer size of VMBus device.
Patch looks good to me. It will be helpful if you can document the ring sizes
for each device and put it in the comment. (e.g
> Subject: [PATCH 3/6] uio_hv_generic: Enable interrupt for low speed VMBus
> devices
>
> Hyper-V is adding some "specialty" synthetic devices. Instead of writing new
> kernel-level VMBus drivers for these devices, the devices will be presented to
> user space via this existing Hyper-V generic UIO
Rename HV_REGISTER_GUEST_OSID to HV_REGISTER_GUEST_OS_ID. This matches
the existing HV_X64_MSR_GUEST_OS_ID.
Rename HV_REGISTER_CRASH_* to HV_REGISTER_GUEST_CRASH_*. Including
GUEST_ is consistent with other #defines such as
HV_FEATURE_GUEST_CRASH_MSR_AVAILABLE. The new names also match the TLFS
do
> +void __init ms_hyperv_late_init(void)
> +{
> + struct acpi_table_header *header;
> + acpi_status status;
> + u8 *randomdata;
> + u32 length, i;
> +
> + /*
> +* Seed the Linux random number generator with entropy provided by
> +* the Hyper-V host in A
On Tue, Mar 12, 2024 at 08:09:03PM +0530, Ani Sinha wrote:
>
>
> On Tue, 12 Mar 2024, Shradha Gupta wrote:
>
> > If the network configuration strings are passed as a combination of IPv and
> > IPv6 addresses, the current KVP daemon doesnot handle it for the keyfile
> > configuration format.
> >
On Tue, Mar 12, 2024 at 09:58:03AM -0700, Easwar Hariharan wrote:
> On 3/12/2024 5:38 AM, Shradha Gupta wrote:
> > If the network configuration strings are passed as a combination of IPv and
>
> *IPv4*
>
> > IPv6 addresses, the
From: Long Li Sent: Tuesday, March 12, 2024 9:51 PM
>
> > +void __init ms_hyperv_late_init(void)
> > +{
> > + struct acpi_table_header *header;
> > + acpi_status status;
> > + u8 *randomdata;
> > + u32 length, i;
> > +
> > + /*
> > +* Seed the Linux random nu
13 matches
Mail list logo
