stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CKI <cki-project@redhat.com>
To: Linux Stable maillist <stable@vger.kernel.org>
Subject: Stable queue: queue-4.20
Date: Thu, 10 Jan 2019 11:43:28 -0500	[thread overview]
Message-ID: <cki.069C8341C9A3B201FAB798B0C7D44751E72B8251E4C475A2F6FFE5F29C3DC483.YX247DDEFIB5BR8G21FRNQJ3MZVO4KSAYZQEWU6O@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3313 bytes --]

Hello,

We ran automated tests on a patchset that was proposed for merging into this
kernel tree. The patches were applied to:

       Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
            Commit: 8c3f48e8c288 Linux 4.20.1

The results of these automated tests are provided below.

    Overall result: FAILED  (see details below)
       Patch merge: OK
           Compile: FAILED

We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:

  s390x:   FAILED (build log attached: build_s390.log.gz)
  powerpc64le: FAILED (build log attached: build_powerpc.log.gz)
  aarch64: FAILED (build log attached: build_arm64.log.gz)
  x86_64:  FAILED (build log attached: build_x86_64.log.gz)

We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.

Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.

        ,-.   ,-.
       ( C ) ( K )  Continuous
        `-',-.`-'   Kernel
          ( I )     Integration
           `-'
______________________________________________________________________________

Merge testing
-------------

We cloned this repository and checked out a ref:

  Repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
  Ref:  8c3f48e8c288 Linux 4.20.1

We then merged the following patches with `git am`:

  scsi-zfcp-fix-posting-too-many-status-read-buffers-leading-to-adapter-shutdown.patch
  scsi-lpfc-do-not-set-queue-page_count-to-0-if-pc_sli4_params.wqpcnt-is-invalid.patch
  fork-record-start_time-late.patch
  zram-fix-double-free-backing-device.patch
  hwpoison-memory_hotplug-allow-hwpoisoned-pages-to-be-offlined.patch
  mm-devm_memremap_pages-mark-devm_memremap_pages-export_symbol_gpl.patch
  mm-devm_memremap_pages-kill-mapping-system-ram-support.patch
  mm-devm_memremap_pages-fix-shutdown-handling.patch
  hugetlbfs-use-i_mmap_rwsem-for-more-pmd-sharing-synchronization.patch
  hugetlbfs-use-i_mmap_rwsem-to-fix-page-fault-truncate-race.patch
  memcg-oom-notify-on-oom-killer-invocation-from-the-charge-path.patch
  sunrpc-fix-cache_head-leak-due-to-queued-request.patch
  sunrpc-use-svc_net-in-svcauth_gss_-functions.patch
  sunrpc-use-after-free-in-svc_process_common.patch
  mm-devm_memremap_pages-add-memory_device_private-support.patch
  mm-hmm-use-devm-semantics-for-hmm_devmem_-add-remove.patch
  mm-hmm-replace-hmm_devmem_pages_create-with-devm_memremap_pages.patch
  mm-hmm-mark-hmm_devmem_-add-add_resource-export_symbol_gpl.patch
  mm-swap-fix-swapoff-with-ksm-pages.patch

Compile testing
---------------

We compiled the kernel for 4 architectures:

  s390x:
    make options: make INSTALL_MOD_STRIP=1 -j64 targz-pkg -j64
    configuration: 

  powerpc64le:
    make options: make INSTALL_MOD_STRIP=1 -j64 targz-pkg -j64
    configuration: 

  aarch64:
    make options: make INSTALL_MOD_STRIP=1 -j64 targz-pkg -j64
    configuration: 

  x86_64:
    make options: make INSTALL_MOD_STRIP=1 -j64 targz-pkg -j64
    configuration: 


Hardware testing
----------------

We booted each kernel and ran the following tests:

  s390:

  powerpc:

  arm64:

  x86_64:


[-- Attachment #2: build_s390.log.gz --]
[-- Type: application/octet-stream, Size: 32922 bytes --]

[-- Attachment #3: build_powerpc.log.gz --]
[-- Type: application/octet-stream, Size: 73251 bytes --]

[-- Attachment #4: build_arm64.log.gz --]
[-- Type: application/octet-stream, Size: 82647 bytes --]

[-- Attachment #5: build_x86_64.log.gz --]
[-- Type: application/octet-stream, Size: 87402 bytes --]

             reply	other threads:[~2019-01-10 16:43 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 16:43 CKI [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-07 21:21 Stable queue: queue-4.20 CKI
2019-03-03 23:14 CKI
2019-03-03 13:27 CKI
2019-03-03  6:10 CKI
2019-02-28 22:21 CKI
2019-02-27 12:19 CKI
2019-02-27  1:09 CKI
2019-02-26 13:33 CKI
2019-02-26  8:09 CKI
2019-02-26  7:10 CKI
2019-02-26  5:58 CKI
2019-02-25  1:19 CKI
2019-02-24 23:15 CKI
2019-02-18 19:49 CKI
2019-02-18 17:40 CKI
2019-02-18 10:50 CKI
2019-02-18  7:45 CKI
2019-02-15 23:42 CKI
2019-02-12 12:38 CKI
2019-02-11 21:27 CKI
2019-02-11 21:26 CKI
2019-02-11 18:42 CKI
2019-02-11 17:58 CKI
2019-02-10 17:20 CKI
2019-02-10 16:54 CKI
2019-02-10 15:40 CKI
2019-02-09 23:20 CKI
2019-02-04 11:34 CKI
2019-02-04  6:26 CKI
2019-02-04  7:24 ` Greg KH
2019-02-06  9:51   ` Nikolai Kondrashov
2019-02-02 19:20 CKI
2019-02-02 12:55 CKI
2019-01-31 22:12 CKI
2019-01-30  8:03 CKI
2019-01-30  8:16 ` Greg KH
2019-01-30  9:10   ` Major Hayden
2019-01-28 21:36 CKI
2019-01-29  7:41 ` Nikolai Kondrashov
2019-01-29  7:48   ` Nikolai Kondrashov
2019-01-28 21:36 CKI
2019-01-28 13:37 CKI
2019-01-27 22:47 CKI
2019-01-27 22:30 CKI
2019-01-26 21:50 CKI
2019-01-26 11:39 CKI
2019-01-25 14:32 CKI
2019-01-25  0:39 CKI
2019-01-24 22:37 CKI
2019-01-23 21:09 CKI
2019-01-21 23:18 CKI
2019-01-21 18:10 CKI
2019-01-21 14:22 CKI
2019-01-21 15:35 ` Major Hayden
2019-01-18 23:36 CKI
2019-01-18  6:09 CKI
2019-01-14 15:16 CKI
2019-01-14 16:22 ` Greg KH
2019-01-11 10:54 CKI
2019-01-11  3:16 CKI
2019-01-10 22:04 CKI
2019-01-10 20:51 CKI
2019-01-10 18:52 CKI
2019-01-08 22:31 CKI
2019-01-09 14:39 ` Greg KH
2019-01-09 14:48   ` Major Hayden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cki.069C8341C9A3B201FAB798B0C7D44751E72B8251E4C475A2F6FFE5F29C3DC483.YX247DDEFIB5BR8G21FRNQJ3MZVO4KSAYZQEWU6O@redhat.com \
    --to=cki-project@redhat.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).