linux-kernel - linux-next: manual merge of the rcu tree with the kbuild tree

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200701113448.3119f64f@canb.auug.org.au>
Date:   Wed, 1 Jul 2020 11:34:48 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     "Paul E. McKenney" <paulmck@...nel.org>,
        Masahiro Yamada <masahiroy@...nel.org>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Marco Elver <elver@...gle.com>
Subject: linux-next: manual merge of the rcu tree with the kbuild tree

Hi all,

Today's linux-next merge of the rcu tree got a conflict in:

  kernel/kcsan/Makefile

between commit:

  f7c28e224da6 ("kbuild: remove cc-option test of -fno-stack-protector")

from the kbuild tree and commits:

  2839a232071f ("kcsan: Simplify compiler flags")
  61d56d7aa5ec ("kcsan: Disable branch tracing in core runtime")

from the rcu tree.

I fixed it up (I just used the rcu tree version) and can carry the fix
as necessary. This is now fixed as far as linux-next is concerned, but
any non trivial conflicts should be mentioned to your upstream maintainer
when your tree is submitted for merging.  You may also want to consider
cooperating with the maintainer of the conflicting tree to minimise any
particularly complex conflicts.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped