lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 15 Sep 2020 21:05:11 -0700
From:   Dmitry Torokhov <>
To:     Boqun Feng <>
        "K. Y. Srinivasan" <>,
        Haiyang Zhang <>,
        Stephen Hemminger <>,
        Wei Liu <>, Jiri Kosina <>,
        Benjamin Tissoires <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,
        "James E.J. Bottomley" <>,
        "Martin K. Petersen" <>,
        Michael Kelley <>,,,,,,
Subject: Re: [PATCH v4 08/11] Input: hyperv-keyboard: Use VMBUS_RING_SIZE()
 for ringbuffer sizes

On Wed, Sep 16, 2020 at 11:48:14AM +0800, Boqun Feng wrote:
> For a Hyper-V vmbus, the size of the ringbuffer has two requirements:
> 1)	it has to take one PAGE_SIZE for the header
> 2)	it has to be PAGE_SIZE aligned so that double-mapping can work
> VMBUS_RING_SIZE() could calculate a correct ringbuffer size which
> fulfills both requirements, therefore use it to make sure vmbus work
> Note that since the argument for VMBUS_RING_SIZE() is the size of
> payload (data part), so it will be minus 4k (the size of header when
> PAGE_SIZE = 4k) than the original value to keep the ringbuffer total
> size unchanged when PAGE_SIZE = 4k.
> Signed-off-by: Boqun Feng <>
> Cc: Michael Kelley <>
> Cc: Dmitry Torokhov <>

Acked-by: Dmitry Torokhov <>

Please feel free to merge through whatever tree the rest of the patches
will go.



Powered by blists - more mailing lists