public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Michal Hocko <mhocko@suse.com>
Cc: James Hogan <jhogan@kernel.org>,
	linux-metag@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: metag build error in -next due to 'fs, elf: drop MAP_FIXED usage from elf_map'
Date: Sat, 6 Jan 2018 17:07:33 -0800	[thread overview]
Message-ID: <20180107010733.GA317@roeck-us.net> (raw)

The following build error is seen when building metag:meta2_defconfig
or metag:tz1090_defconfig.

arch/metag/kernel/process.c: In function '__metag_elf_map':
arch/metag/kernel/process.c:421: error: 'tsk' undeclared

Bisect results attached.

Guenter

---
# bad: [990b6a07d18cb30a66db3d18ab7d953806237e6a] Add linux-next specific files for 20180105
# good: [30a7acd573899fd8b8ac39236eff6468b195ac7d] Linux 4.15-rc6
git bisect start 'HEAD' 'v4.15-rc6'
# good: [4411e1d8bfc93afafc74548669d772750432e0b7] Merge remote-tracking branch 'crypto/master'
git bisect good 4411e1d8bfc93afafc74548669d772750432e0b7
# good: [fcdad798ac60727fc0a90c36815d19b1629e45a4] Merge remote-tracking branch 'devicetree/for-next'
git bisect good fcdad798ac60727fc0a90c36815d19b1629e45a4
# good: [fe14c29e6d6772e5fc7bb8dc7a7568ce6a887a8e] Merge remote-tracking branch 'staging/staging-next'
git bisect good fe14c29e6d6772e5fc7bb8dc7a7568ce6a887a8e
# good: [b8be2479df7dda35d0d73fafa3f1d9c95c6a89b6] Merge remote-tracking branch 'gpio/for-next'
git bisect good b8be2479df7dda35d0d73fafa3f1d9c95c6a89b6
# bad: [76248405844bf17c0620aea2f0e5bb751fc680b3] lib/stackdepot.c: use a non-instrumented version of memcmp()
git bisect bad 76248405844bf17c0620aea2f0e5bb751fc680b3
# good: [b852120f0251533f414c35396f151d2ddd4d3bde] mm: get 7% more pages in a pagevec
git bisect good b852120f0251533f414c35396f151d2ddd4d3bde
# bad: [2b7030305a472bd15268818282e37818eec2386b] userfaultfd: convert to use anon_inode_getfd()
git bisect bad 2b7030305a472bd15268818282e37818eec2386b
# bad: [b7ebb7ed4b3c8ed9fac1ccb0f32ff3e94e697176] mm, mmu_notifier: annotate mmu notifiers with blockable invalidate callbacks
git bisect bad b7ebb7ed4b3c8ed9fac1ccb0f32ff3e94e697176
# good: [d37faf4a02f9bda96fe637e50fdf880e789f8468] mm: do not lose dirty and accessed bits in pmdp_invalidate()
git bisect good d37faf4a02f9bda96fe637e50fdf880e789f8468
# bad: [b8093f6e4db920936a51e161c2c208e7327c073f] mm: don't use the same value for MAP_FIXED_NOREPLACE and MAP_SYNC
git bisect bad b8093f6e4db920936a51e161c2c208e7327c073f
# good: [d3d42f1481dd877a66577c4c406c18d386ea55f0] mm: introduce MAP_FIXED_NOREPLACE
git bisect good d3d42f1481dd877a66577c4c406c18d386ea55f0
# bad: [7847968573148a5645d53a73ea26c0f4b168d7bb] fs, elf: drop MAP_FIXED usage from elf_map
git bisect bad 7847968573148a5645d53a73ea26c0f4b168d7bb
# good: [cea5c2e4296daaf5d9eec338382a85159d1d4a7f] mm-introduce-map_fixed_safe-fix
git bisect good cea5c2e4296daaf5d9eec338382a85159d1d4a7f
# first bad commit: [7847968573148a5645d53a73ea26c0f4b168d7bb] fs, elf: drop MAP_FIXED usage from elf_map

             reply	other threads:[~2018-01-07  1:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07  1:07 Guenter Roeck [this message]
2018-01-07  8:50 ` metag build error in -next due to 'fs, elf: drop MAP_FIXED usage from elf_map' Michal Hocko
2018-01-08  4:12   ` Guenter Roeck
2018-01-09 11:39     ` James Hogan

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=20180107010733.GA317@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jhogan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-metag@vger.kernel.org \
    --cc=mhocko@suse.com \
    /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