kernel-packages team mailing list archive

[Andy Whitcroft <apw@xxxxxxxxxxxxx>]

@Mark -- of the 41 unique patches listed above a goodly portion seem to
be already applied.  There seem to be some 20 which are applicable,
though I would argue a number of these are code prettyness and not
functional:

commit 4675b0f4137b44af01b20c2f5043a35d8d386adb
Author: Lad, Prabhakar <prabhakar.csengg@xxxxxxxxx>
Date:   Thu Feb 5 15:06:33 2015 +0000

    hyperv: fix sparse warnings
    
    this patch fixes following sparse warnings:
    
    netvsc.c:688:5: warning: symbol 'netvsc_copy_to_send_buf' was not declared. Should it be static?
    rndis_filter.c:627:5: warning: symbol 'rndis_filter_set_offload_params' was not declared. Should it be static?
    rndis_filter.c:702:5: warning: symbol 'rndis_filter_set_rss_param' was not declared. Should it be static?
    
    Signed-off-by: Lad, Prabhakar <prabhakar.csengg@xxxxxxxxx>
    Signed-off-by: Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>
    Signed-off-by: David S. Miller <davem@xxxxxxxxxxxxx>
    (cherry picked from commit da19fcd0d85f36420f578fe6dfe7a2a581b4fa6e)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 08a6c6fff1cd85d354c81477b0839f7d127f3677
Author: Nicholas Mc Guire <der.herr@xxxxxxx>
Date:   Sun Jan 25 15:46:31 2015 +0100

    hyperv: netvsc.c: match wait_for_completion_timeout return type
    
    Signed-off-by: Nicholas Mc Guire <der.herr@xxxxxxx>
    Signed-off-by: David S. Miller <davem@xxxxxxxxxxxxx>
    (cherry picked from commit 7390fe9c9a7ffdb0947add66efe7dedbe6b1cb6f)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 4fb9d6200a772fbba36492816713d44519c18011
Author: kbuild test robot <fengguang.wu@xxxxxxxxx>
Date:   Mon Jan 26 01:17:54 2015 +0800

    Drivers: hv: vmbus: hv_process_timer_expiration() can be static
    
    drivers/hv/vmbus_drv.c:582:6: sparse: symbol 'hv_process_timer_expiration' was not declared. Should it be static?
    
    Signed-off-by: Fengguang Wu <fengguang.wu@xxxxxxxxx>
    Cc: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
    Cc: "K. Y. Srinivasan" <kys@xxxxxxxxxxxxx>
    Cc: Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit d8a60e000c951f845d9a5fb3e67853e0e63a5659)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 880bbd9b213da54767df2261f94568e797c34365
Author: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
Date:   Tue Jan 20 16:45:06 2015 +0100

    Drivers: hv: vmbus: serialize Offer and Rescind offer
    
    Commit 4b2f9abea52a ("staging: hv: convert channel_mgmt.c to not call
    osd_schedule_callback")' was written under an assumption that we never receive
    Rescind offer while we're still processing the initial Offer request. However,
    the issue we fixed in 04a258c162a8 could be caused by this assumption not
    always being true.
    
    In particular, we need to protect against the following:
    1) Receiving a Rescind offer after we do queue_work() for processing an Offer
       request and before we actually enter vmbus_process_offer(). work.func points
       to vmbus_process_offer() at this moment and in vmbus_onoffer_rescind() we do
       another queue_work() without a check so we'll enter vmbus_process_offer()
       twice.
    2) Receiving a Rescind offer after we enter vmbus_process_offer() and
       especially after we set >state = CHANNEL_OPEN_STATE. Many things can go
       wrong in that case, e.g. we can call free_channel() while we're still using
       it.
    
    Implement the required protection by changing work->func at the very end of
    vmbus_process_offer() and checking work->func in vmbus_onoffer_rescind(). In
    case we receive rescind offer during or before vmbus_process_offer() is done
    we set rescind flag to true and we check it at the end of vmbus_process_offer()
    so such offer will not get lost.
    
    Suggested-by: Radim Krčmář <rkrcmar@xxxxxxxxxx>
    Signed-off-by: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
    Acked-by: Jason Wang <jasowang@xxxxxxxxxx>
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit d7f2fbafb4f84306436277664cf28042beaf252a)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit baa7b78f7b43b01048314ca70fe151e12cccae75
Author: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
Date:   Tue Jan 20 16:45:05 2015 +0100

    Drivers: hv: rename sc_lock to the more generic lock
    
    sc_lock spinlock in struct vmbus_channel is being used to not only protect the
    sc_list field, e.g. vmbus_open() function uses it to implement test-and-set
    access to the state field. Rename it to the more generic 'lock' and add the
    description.
    
    Signed-off-by: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Acked-by: Jason Wang <jasowang@xxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit 67fae053bfc6e84144150e4c6c62670abb215c33)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 4dff4c4336795cf79f1fe4fdae3a5391da89a3d8
Author: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
Date:   Tue Jan 20 16:45:04 2015 +0100

    Drivers: hv: check vmbus_device_create() return value in vmbus_process_offer()
    
    vmbus_device_create() result is not being checked in vmbus_process_offer() and
    it can fail if kzalloc() fails. Add the check and do minor cleanup to avoid
    additional duplication of "free_channel(); return;" block.
    
    Reported-by: Jason Wang <jasowang@xxxxxxxxxx>
    Signed-off-by: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Acked-by: Jason Wang <jasowang@xxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit 9c3a6f7e476fc4961297fc66b1177f9f8c8dd238)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit f797ee97213a5a8fcf5653d513e71ef6ffa3ced5
Author: Dexuan Cui <decui@xxxxxxxxxxxxx>
Date:   Wed Jan 14 01:55:10 2015 -0800

    hv: hv_fcopy: drop the obsolete message on transfer failure
    
    In the case the user-space daemon crashes, hangs or is killed, we
    need to down the semaphore, otherwise, after the daemon starts next
    time, the obsolete data in fcopy_transaction.message or
    fcopy_transaction.fcopy_msg will be used immediately.
    
    Cc: Jason Wang <jasowang@xxxxxxxxxx>
    Cc: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
    Signed-off-by: Dexuan Cui <decui@xxxxxxxxxxxxx>
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit d9b1652947c695d247b5e4603a16213ec55661ed)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 0539cdcfa11119de9b67fbb91195cde9b9b4c004
Author: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
Date:   Fri Jan 9 23:54:34 2015 -0800

    Drivers: hv: vmbus: Support a vmbus API for efficiently sending page arrays
    
    Currently, the API for sending a multi-page buffer over VMBUS is limited to
    a maximum pfn array of MAX_MULTIPAGE_BUFFER_COUNT. This limitation is
    not imposed by the host and unnecessarily limits the maximum payload
    that can be sent. Implement an API that does not have this restriction.
    
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit d61031ee8df6214d58371a1cc36a0591e242fba0)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 4e3ba449a3ecb7a03becd8afe11890ed06b1d2ca
Author: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
Date:   Fri Jan 9 23:54:33 2015 -0800

    Drivers: hv: vmbus: Fix a bug in vmbus_establish_gpadl()
    
    Correctly compute the local (gpadl) handle.
    I would like to thank Michael Brown <mcb30@xxxxxxxx> for seeing this bug.
    
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Reported-by: Michael Brown <mcb30@xxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit 9f52a1630922bcdab75fc72e59ed58db8e164314)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit d183d4fef5cad98e442a94e52c6e5e74af96c0b4
Author: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
Date:   Fri Jan 9 23:54:32 2015 -0800

    Drivers: hv: vmbus: Implement a clockevent device
    
    Implement a clockevent device based on the timer support available on
    Hyper-V.
    In this version of the patch I have addressed Jason's review comments.
    
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Reviewed-by: Jason Wang <jasowang@xxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit 4061ed9e2aaac31daef44f06e9b83143c78b24b2)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 5c0d41d971d0c8927b96b63d5302953073f46511
Author: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
Date:   Fri Jan 9 23:54:31 2015 -0800

    Drivers: hv: hv_balloon: Don't post pressure status from interrupt context
    
    We currently release memory (balloon down) in the interrupt context and we also
    post memory status while releasing memory. Rather than posting the status
    in the interrupt context, wakeup the status posting thread to post the status.
    This will address the inconsistent lock state that Sitsofe Wheeler <sitsofe@xxxxxxxxx>
    reported:
    
    http://lkml.iu.edu/hypermail/linux/kernel/1411.1/00075.html
    
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Reported-by: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit ab3de22bb4a3d4bda2d0ec8bebcb76a40f1cbf9b)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit dfe6f04504706366b7ab5a3965f9f3fa4120402b
Author: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
Date:   Fri Jan 9 23:54:30 2015 -0800

    Drivers: hv: hv_balloon: Fix a locking bug in the balloon driver
    
    We support memory hot-add in the Hyper-V balloon driver by hot adding an appropriately
    sized and aligned region and controlling the on-lining of pages within that region
    based on the pages that the host wants us to online. We do this because the
    granularity and alignment requirements in Linux are different from what Windows
    expects. The state to manage the onlining of pages needs to be correctly
    protected. Fix this bug.
    
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit 22f88475b62ac826acae2f77c3e1bd9543e87b2a)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 6bbc11a6fc3f1a0e37099e9a0e1db4108e793d92
Author: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
Date:   Fri Jan 9 23:54:29 2015 -0800

    Drivers: hv: hv_balloon: Make adjustments in computing the floor
    
    Make adjustments in computing the balloon floor. The current computation
    of the balloon floor was not appropriate for virtual machines with more than
    10 GB of assigned memory - we would get into situations where the host would
    agressively balloon down the guest and leave the guest in an unusable state.
    This patch fixes the issue by raising the floor.
    
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit 79208c57da5311860f165b613c89b3f647e357cd)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit a656cded0f068c4d67a1a741a62d6118b762d798
Author: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
Date:   Fri Jan 9 22:18:55 2015 -0800

    Tools: hv: do not add redundant '/' in hv_start_fcopy()
    
    We don't need to add additional '/' to smsg->path_name as snprintf("%s/%s")
    does the right thing. Without the patch we get doubled '//' in the log message.
    
    Signed-off-by: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit c1136da62170465920eea1ae9ba9ce2234091f77)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 88182e068f9eb76330c14cb30f081bb1b11b1bea
Author: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
Date:   Fri Jan 9 22:18:54 2015 -0800

    Tools: hv: address compiler warnings for hv_fcopy_daemon.c
    
    This patch addresses two types of compiler warnings:
    ... warning: unused variable .fd. [-Wunused-variable]
    and
    ... warning: format .%s. expects argument of type .char *., but argument 5 has type .__u16 *. [-Wformat=]
    
    Signed-off-by: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit aba474b8185d60ca8cdbf3049fe6d655aa761e23)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 34bc731aa30f8a2fd07dacc83b41adf7875638ec
Author: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
Date:   Sun Dec 14 23:34:51 2014 -0800

    Drivers: hv: vmbus: Use get_cpu() to get the current CPU
    
    Replace calls for smp_processor_id() to get_cpu() to get the CPU ID of
    the current CPU. In these instances, there is no correctness issue with
    regards to preemption, we just need the current CPU ID.
    
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    (cherry picked from commit 87712bf81dd092821c406ea3fb47a07222484a64)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit f52045e291e756cdd0c5439065bb7e4f14235c3e
Author: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
Date:   Tue Dec 16 13:21:44 2014 -0800

    storvsc: fix a bug in storvsc limits
    
    Commit 4cd83ecdac20d30725b4f96e5d7814a1e290bc7e changed the limits to
    reflect the values on the host. It turns out that WS2008R2 cannot
    correctly handle these new limits. Fix this bug by setting the limits
    based on the host.
    
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Reviewed-by: Long Li <longli@xxxxxxxxxxxxx>
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    (cherry picked from commit 0fb8db29f2a02e8451e4e56d364c706f70a9ef00)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 7d0f77d13baab025ca2039b8e023834c675b3ada
Author: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
Date:   Tue Dec 16 13:21:43 2014 -0800

    storvsc: force discovery of LUNs that may have been removed.
    
    The host asks the guest to scan when a LUN is removed or added.
    The only way a guest can identify the removed LUN is when an I/O is
    attempted on a removed LUN - the SRB status code indicates that the LUN
    is invalid. We currently handle this SRB status and remove the device.
    
    Rather than waiting for an I/O to remove the device, force the discovery of
    LUNs that may have been removed prior to discovering LUNs that may have
    been added.
    
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Reviewed-by: Long Li <longli@xxxxxxxxxxxxx>
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    (cherry picked from commit 34a716bc345ba06c34aa33d09536fcb607523818)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit 97b1c07f25568b4b2ce777adbd1f73407a791000
Author: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
Date:   Tue Dec 16 13:21:42 2014 -0800

    storvsc: in responce to a scan event, scan the host
    
    The virtual HBA that storvsc implements can support multiple channels and
    targets. So, scan the host when the host notifies that a scan is needed.
    
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Reviewed-by: Long Li <longli@xxxxxxxxxxxxx>
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    (cherry picked from commit 2a09ed3d97ff8b5b377f86da9b9afd9ebd97b362)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

commit df24dbad9a7e4419aba43c608a030f2f3824b60b
Author: Christoph Hellwig <hch@xxxxxx>
Date:   Mon Dec 29 20:05:09 2014 -0800

    storvsc: use cmd_size to allocate per-command data
    
    STORVSC uses its own momory pool to manage device request data.  However,
    the SCSI layer already has a mechanisim for allocating additional memory
    for each command issued to device driver. This patch removes the memory
    pool in STORVSC and makes it use SCSI layer to allocate memory for device
    request data.
    
    Reviewed-by: Long Li <longli@xxxxxxxxxxxxx>
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    (cherry picked from commit ead3700d893654d440edcb66fb3767a0c0db54cf)
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1423343

Title:
  [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following patches are missing from ubuntu vivid 15.04 compared to
  latest upstream (linux-next) , please include them in ubuntu vivid ,
  all the patches listed here are already upstream .

  /arch/x86/include/uapi/asm/hyperv.h

  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e7827b5ea4ca93b4d864bc07c0fafb838d496b1

  /drivers/hv/hyperv_vmbus.h
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2

  drivers/hv/vmbus_drv.c
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=a45de93eb10ae44446aec2c73d722562ab46092a
  2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d8a60e000c951f845d9a5fb3e67853e0e63a5659
  3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=90f3453585479d5beb75058da46eb573ced0e6ac
  5. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=302a3c0f2757ae1a3e7df3f9fa1f20e2214ab945
  6. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b0209501dc7586cbfbf6d023f2dd3ce4621aff2c

  /drivers/hv/hv_snapshot.c
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4
  2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=649142074d86afebe0505431a93957505d244dd6

  /drivers/hv/hv_kvp.c
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4

  /drivers/hv/hv_fcopy.c
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d9b1652947c695d247b5e4603a16213ec55661ed

  /drivers/hv/channel.c
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d61031ee8df6214d58371a1cc36a0591e242fba0
  3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9f52a1630922bcdab75fc72e59ed58db8e164314

  /drivers/hv/channel_mgmt.c
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d7f2fbafb4f84306436277664cf28042beaf252a
  2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9c3a6f7e476fc4961297fc66b1177f9f8c8dd238
  4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=87712bf81dd092821c406ea3fb47a07222484a64
  5. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c3582a2c4d0baf1fa3955c8b3d3d61308df474c7

  /drivers/hv/hv_balloon.c
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ab3de22bb4a3d4bda2d0ec8bebcb76a40f1cbf9b
  2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=22f88475b62ac826acae2f77c3e1bd9543e87b2a
  3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=79208c57da5311860f165b613c89b3f647e357cd
  4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=f6712238471a8afdbfcea482483fc121281292d8

  /tools/hv/hv_vss_daemon.c
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e5db05aae4657c7ade34ccc4b93f27ab647498e
  2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=7a401744d517864f8f2f2afba589e58a71d03aa6
  3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=170f4bea2008054e5098f99359e29823a7b4b1b9
  4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4f689190bb55d171d2f6614f8a6cbd4b868e48bd

  /tools/hv/hv_fcopy_daemon.c
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c1136da62170465920eea1ae9ba9ce2234091f77
  2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=aba474b8185d60ca8cdbf3049fe6d655aa761e23

  /drivers/net/hyperv/netvsc.c
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=da19fcd0d85f36420f578fe6dfe7a2a581b4fa6e
  2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d953ca4ddf71aa91a4596b2ff7ff1598f6ad4708
  3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=7390fe9c9a7ffdb0947add66efe7dedbe6b1cb6f
  4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c51ed18257e731e15541324cd58bd3761d9d3b1c
  5. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=aa99c47933d2c9a7622440d1b08ebb46ad8bd741
  6. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4d3c9d37f77566b04216dfc9a6513082002d7a1f

  /drivers/scsi/storvsc_drv.c
  1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b0a93d96b2814c725161f91a4e35d0c29ec0f95b
  2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=0fb8db29f2a02e8451e4e56d364c706f70a9ef00
  3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=34a716bc345ba06c34aa33d09536fcb607523818
  4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=2a09ed3d97ff8b5b377f86da9b9afd9ebd97b362
  5. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ead3700d893654d440edcb66fb3767a0c0db54cf
  6. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=db5ed4dfd5dd0142ec36ff7b335e0ec3b836b3e6
  7. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c8b09f6fb67df7fc1b51ced1037fa9b677428149
  8. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d811b848ebb78a1135658aa20a80e31994df47f7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423343/+subscriptions