Re: linux-next: Tree for Oct 14 (insn_decoder_test)
Hi,
On Mon, 14 Oct 2019 08:30:02 -0700
Randy Dunlap wrote:
> On 10/13/19 11:47 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20191011:
> >
>
> on x86_64:
>
> HOSTCC arch/x86/tools/insn_decoder_test
> HOSTCC arch/x86/tools/insn_sanity
> TESTposttest
> arch/x86/tools/insn_decoder_test: warning: Found an x86 instruction decoder
> bug, please report this.
> arch/x86/tools/insn_decoder_test: warning: 81000bf1: f7 0b 00 01 08
> 00 testl $0x80100,(%rbx)
> arch/x86/tools/insn_decoder_test: warning: objdump says 6 bytes, but
> insn_get_length() says 2
> arch/x86/tools/insn_decoder_test: warning: Decoded and checked 11913894
> instructions with 1 failures
> TESTposttest
> arch/x86/tools/insn_sanity: Success: decoded and checked 100 random
> instructions with 0 errors (seed:0x871ce29c)
Hmm, curious.
x86-opcode-map.txt said,
f7: Grp3_2 Ev (1A)
and "0x0b" is 1011b, Group encoding bits are 5,4,3 (reg field),
so group index is 001.
GrpTable: Grp3_2
0: TEST Ev,Iz
1:
Hmm, "f7 0b" is not assigned to any instruction... (testl should be f7 03)
I've checked Intel SDM May 2019 version(*), but the Opcode Map (Table A-6.
Opecode
Extensions for One- and Two-byte Opecodes by Group Number) showed the group
index
001 is still blank. I've also checked that Table B-13 (General Purpose
Instruction
Formats and Encodings for Non-64-Bit Modes (Note that this has no REX prefix))
but
I couldn't find "f7 0b".
At last, I found that on AMD64 Architecture Programmer's Manual Volume 3,
Appendix A.2
Table A-6. ModRM.reg Extensions for the Primary Opcode Map(**), which shows
that both
f7 + reg=000 and f7 + reg=001 are same. So only on AMD64, it is officially
available
instruction.
(*)
https://software.intel.com/sites/default/files/managed/a4/60/325383-sdm-vol-2abcd.pdf
(**) https://www.amd.com/system/files/TechDocs/24594.pdf
OK, so this should be fixed with below patch.
--
>From b3f45b86df25be59fcf417730ab4c69c6310eaad Mon Sep 17 00:00:00 2001
From: Masami Hiramatsu
Date: Wed, 23 Oct 2019 14:45:35 +0900
Subject: [PATCH] x86/decoder: Add TEST opcode to Group3-2
Add TEST opcode to Group3-2 reg=001b as same as Group3-1 does.
Commit 12a78d43de76 ("x86/decoder: Add new TEST instruction pattern")
added a TEST opcode assignment to f6 XX/001/XXX (Group 3-1), but not
added f7 XX/001/XXX (Group 3-2). Actually these TEST opcode is not
described in Intel SDM Vol2, but described in AMD64 Architecture
Programmer's Manual Vol.3, Appendix A.2 Table A-6. ModRM.reg
Extensions for the Primary Opcode Map.
Without this fix, Randy found a warning by insn_decoder_test related
to this issue as below.
HOSTCC arch/x86/tools/insn_decoder_test
HOSTCC arch/x86/tools/insn_sanity
TESTposttest
arch/x86/tools/insn_decoder_test: warning: Found an x86 instruction decoder
bug, please report this.
arch/x86/tools/insn_decoder_test: warning: 81000bf1:f7 0b 00 01 08
00 testl $0x80100,(%rbx)
arch/x86/tools/insn_decoder_test: warning: objdump says 6 bytes, but
insn_get_length() says 2
arch/x86/tools/insn_decoder_test: warning: Decoded and checked 11913894
instructions with 1 failures
TESTposttest
arch/x86/tools/insn_sanity: Success: decoded and checked 100 random
instructions with 0 errors (seed:0x871ce29c)
To fix this error, add TEST opcode according to AMD64 APM Vol.3.
Reported-by: Randy Dunlap
Signed-off-by: Masami Hiramatsu
---
arch/x86/lib/x86-opcode-map.txt | 2 +-
tools/arch/x86/lib/x86-opcode-map.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/lib/x86-opcode-map.txt b/arch/x86/lib/x86-opcode-map.txt
index e0b85930dd77..4635ce298d1d 100644
--- a/arch/x86/lib/x86-opcode-map.txt
+++ b/arch/x86/lib/x86-opcode-map.txt
@@ -907,7 +907,7 @@ EndTable
GrpTable: Grp3_2
0: TEST Ev,Iz
-1:
+1: TEST Ev,Iz
2: NOT Ev
3: NEG Ev
4: MUL rAX,Ev
diff --git a/tools/arch/x86/lib/x86-opcode-map.txt
b/tools/arch/x86/lib/x86-opcode-map.txt
index e0b85930dd77..4635ce298d1d 100644
--- a/tools/arch/x86/lib/x86-opcode-map.txt
+++ b/tools/arch/x86/lib/x86-opcode-map.txt
@@ -907,7 +907,7 @@ EndTable
GrpTable: Grp3_2
0: TEST Ev,Iz
-1:
+1: TEST Ev,Iz
2: NOT Ev
3: NEG Ev
4: MUL rAX,Ev
--
2.20.1
--
Masami Hiramatsu
Re: linux-next: Tree for Oct 14 (insn_decoder_test)
On 10/13/19 11:47 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20191011: > on x86_64: HOSTCC arch/x86/tools/insn_decoder_test HOSTCC arch/x86/tools/insn_sanity TESTposttest arch/x86/tools/insn_decoder_test: warning: Found an x86 instruction decoder bug, please report this. arch/x86/tools/insn_decoder_test: warning: 81000bf1:f7 0b 00 01 08 00 testl $0x80100,(%rbx) arch/x86/tools/insn_decoder_test: warning: objdump says 6 bytes, but insn_get_length() says 2 arch/x86/tools/insn_decoder_test: warning: Decoded and checked 11913894 instructions with 1 failures TESTposttest arch/x86/tools/insn_sanity: Success: decoded and checked 100 random instructions with 0 errors (seed:0x871ce29c) -- ~Randy
Re: linux-next: Tree for Oct 14 (sound/soc/sof/)
On 10/13/19 11:47 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20191011:
>
on i386:
ld: sound/soc/sof/control.o: in function `snd_sof_switch_put':
control.c:(.text+0x49a): undefined reference to `ledtrig_audio_set'
ld: control.c:(.text+0x4d1): undefined reference to `ledtrig_audio_set'
when
CONFIG_LEDS_TRIGGER_AUDIO=m
CONFIG_SND_SOC_SOF=y
This code in does not handle the config combo above:
#if IS_ENABLED(CONFIG_LEDS_TRIGGER_AUDIO)
enum led_brightness ledtrig_audio_get(enum led_audio type);
void ledtrig_audio_set(enum led_audio type, enum led_brightness state);
#else
static inline enum led_brightness ledtrig_audio_get(enum led_audio type)
{
return LED_OFF;
}
static inline void ledtrig_audio_set(enum led_audio type,
enum led_brightness state)
{
}
#endif
--
~Randy
linux-next: Tree for Oct 14
Hi all, Changes since 20191011: The net-next tree gained a conflict against the net tree. The bpf-next tree gained conflicts against the net tree. The akpm tree lost a patch taht turned up elsewhere. Non-merge commits (relative to Linus' tree): 3676 3784 files changed, 128699 insertions(+), 61502 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc and sparc64 defconfig. And finally, a simple boot test of the powerpc pseries_le_defconfig kernel in qemu (with and without kvm enabled). Below is a summary of the state of the merge. I am currently merging 313 trees (counting Linus' and 78 trees of bug fix patches pending for the current merge release). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (2581efa9a47d Merge tag 'hwmon-for-v5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging) Merging fixes/master (54ecb8f7028c Linux 5.4-rc1) Merging kbuild-current/fixes (b8d5e105ebbf scripts: setlocalversion: fix a bashism) Merging arc-current/for-curr (41277ba7eb4e ARC: mm: tlb flush optim: elide redundant uTLB invalidates for MMUv3) Merging arm-current/fixes (4c0742f65b4e ARM: 8914/1: NOMMU: Fix exc_ret for XIP) Merging arm-soc-fixes/arm/fixes (dd163ca3fb49 Merge tag 'mvebu-fixes-5.4-1' of git://git.infradead.org/linux-mvebu into arm/fixes) Merging arm64-fixes/for-next/fixes (86109a691a45 arm64: Fix kcore macros after 52-bit virtual addressing fallout) Merging m68k-current/for-linus (0f1979b402df m68k: Remove ioremap_fullcache()) Merging powerpc-fixes/fixes (2272905a4580 spufs: fix a crash in spufs_create_root()) Merging s390-fixes/fixes (062795fcdcb2 s390/uaccess: avoid (false positive) compiler warnings) Merging sparc/master (038029c03e21 sparc: remove unneeded uapi/asm/statfs.h) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (33902b4a4227 netdevsim: Fix error handling in nsim_fib_init and nsim_fib_exit) Merging bpf/master (8caf8a91f34d Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf) Merging ipsec/master (68ce6688a5ba net: sched: taprio: Fix potential integer overflow in taprio_set_picos_per_byte) Merging netfilter/master (503c9addef61 ptp: fix typo of "mechanism" in Kconfig help text) Merging ipvs/master (503c9addef61 ptp: fix typo of "mechanism" in Kconfig help text) Merging wireless-drivers/master (3aed88373bda Merge tag 'iwlwifi-for-kalle-2019-10-09' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes) Merging mac80211/master (82ad862115c2 Merge branch 'smc-fixes') Merging rdma-fixes/for-rc (0417791536ae RDMA/mlx5: Add missing synchronize_srcu() for MW cases) Merging sound-current/for-linus (130bce3afbbb ALSA: hdac: clear link output stream mapping) Merging sound-asoc-fixes/for-linus (3e722e0e81ca Merge branch 'asoc-5.4' into asoc-linus) Merging regmap-fixes/for-linus (da0c9ea146cb Linux 5.4-rc2) Merging regulator-fixes/for-linus (ca32f845a865 Merge branch 'regulator-5.4' into regulator-linus) Merging spi-fixes/for-linus (f4192468460d Merge branch 'spi-5.4' into spi-linus) Merging pci-current/for-linus (54ecb8f7028c Linux 5.4-rc1) Merging driver-core.current/driver-core-linus (82af5b660967 sysfs: Fixes __BIN_ATTR_WO() macro) Merging tty.current/tty-linus (da94001239cc Merge tag 'char-misc-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc) Merging usb.current/usb-linus (da94001239cc Merge tag 'char-misc-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc) Merging usb-gadget-fixes/fixes (4a56a478a525 usb: gadget: mas
linux-next: Tree for Oct 14
Hi all, Please do *not* add any v4.10 material to your linux-next included trees until v4.9-rc1 has been released i.e. the merge window closes. Changes since 20161013: The akpm-current tree still had its build failures for which I applied 2 patches. The akpm tree gained a conflict against the net tree. Non-merge commits (relative to Linus' tree): 1011 1608 files changed, 50455 insertions(+), 13490 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig (with CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig (this fails its final link) and pseries_le_defconfig and i386, sparc and sparc64 defconfig. Below is a summary of the state of the merge. I am currently merging 243 trees (counting Linus' and 34 trees of patches pending for Linus' tree). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (b67be92feb48 Merge tag 'pwm/for-4.9-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm) Merging fixes/master (30066ce675d3 Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6) Merging kbuild-current/rc-fixes (d3e2773c4ede builddeb: Skip gcc-plugins when not configured) Merging arc-current/for-curr (8df0cc75f530 ARC: [build] Support gz, lzma compressed uImage) Merging arm-current/fixes (fb833b1fbb68 ARM: fix delays) Merging m68k-current/for-linus (6736e65effc3 m68k: Migrate exception table users off module.h and onto extable.h) Merging metag-fixes/fixes (35d04077ad96 metag: Only define atomic_dec_if_positive conditionally) Merging powerpc-fixes/fixes (b79331a5eb9f powerpc/powernv/pci: Fix m64 checks for SR-IOV and window alignment) Merging sparc/master (4c1fad64eff4 Merge tag 'for-f2fs-4.9' of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs) Merging net/master (4eb6753c3324 net: bridge: add the multicast_flood flag attribute to brport_attrs) Merging ipsec/master (7f92083eb58f vti6: flush x-netns xfrm cache when vti interface is removed) Merging netfilter/master (6d3a4c404648 strparser: Propagate correct error code in strp_recv()) Merging ipvs/master (ea43f860d984 Merge branch 'ethoc-fixes') Merging wireless-drivers/master (1ea2643961b0 ath6kl: add Dell OEM SDIO I/O for the Venue 8 Pro) Merging mac80211/master (1d4de2e222b4 mac80211: fix CMD_FRAME for AP_VLAN) Merging sound-current/for-linus (fdd8218d7d1b ALSA: line6: fix a crash in line6_hwdep_write()) Merging pci-current/for-linus (035ee288ae7a PCI: Fix bridge_d3 update on device removal) Merging driver-core.current/driver-core-linus (b66484cd7470 Merge branch 'akpm' (patches from Andrew)) Merging tty.current/tty-linus (b66484cd7470 Merge branch 'akpm' (patches from Andrew)) Merging usb.current/usb-linus (b66484cd7470 Merge branch 'akpm' (patches from Andrew)) Merging usb-gadget-fixes/fixes (d8a4100ddc75 usb: gadget: udc: atmel: fix endpoint name) Merging usb-serial-fixes/usb-linus (f190fd92458d USB: serial: simple: add support for another Infineon flashloader) Merging usb-chipidea-fixes/ci-for-usb-stable (6b7f456e67a1 usb: chipidea: host: fix NULL ptr dereference during shutdown) Merging staging.current/staging-linus (b67be92feb48 Merge tag 'pwm/for-4.9-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm) Merging char-misc.current/char-misc-linus (b66484cd7470 Merge branch 'akpm' (patches from Andrew)) Merging input-current/for-linus (c758f96a8c34 Merge branch 'next' into for-linus) Merging crypto-current/master (c3afafa47898 Merge git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6) Merging ide/master (797cee982eef Merge branch 'stable-4.8' of git://git.infradead.org
linux-next: Tree for Oct 14
Hi all, Please do not add any material intended for v3.19 to your linux-next included trees until after v3.18-rc1 has been released. Changes since 20141013: Removed trees: powernv-cpuidle, signal-cleanup Non-merge commits (relative to Linus' tree): 2254 2093 files changed, 71407 insertions(+), 27705 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig for x86_64 and a multi_v7_defconfig for arm. After the final fixups (if any), it is also built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and allyesconfig (this fails its final link) and i386, sparc, sparc64 and arm defconfig. Below is a summary of the state of the merge. I am currently merging 224 trees (counting Linus' and 32 trees of patches pending for Linus' tree). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwells...@canb.auug.org.au $ git checkout master $ git reset --hard stable Merging origin/master (f1d0d14120a8 Merge branch 'x86-cpu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip) Merging fixes/master (b94d525e58dc Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net) Merging kbuild-current/rc-fixes (7d1311b93e58 Linux 3.17-rc1) Merging arc-current/for-curr (2ce7598c9a45 Linux 3.17-rc4) Merging arm-current/fixes (ad684dce87fa ARM: 8179/1: kprobes-test: Fix compile error "bad immediate value for offset") Merging m68k-current/for-linus (24cae7934cf1 m68k: Reformat arch/m68k/mm/hwtest.c) Merging metag-fixes/fixes (ffe6902b66aa asm-generic: remove _STK_LIM_MAX) Merging mips-fixes/mips-fixes (1795cd9b3a91 Linux 3.16-rc5) Merging powerpc-merge/merge (396a34340cdf powerpc: Fix endianness of flash_block_list in rtas_flash) Merging powerpc-merge-mpe/for-linus (d53ba6b3bba3 cxl: Fix afu_read() not doing finish_wait() on signal or non-blocking) Merging sparc/master (bdcf81b658eb sparc64: Fix lockdep warnings on reboot on Ultra-5) Merging net/master (01d2d484e49e Merge branch 'bcmgenet_systemport') Merging ipsec/master (b8c203b2d2fc xfrm: Generate queueing routes only from route lookup functions) Merging sound-current/for-linus (3f4032861cfb ALSA: bebob: Fix failure to detect source of clock for Terratec Phase 88) Merging pci-current/for-linus (7cbeb9f90db8 PCI: pciehp: Fix pcie_wait_cmd() timeout) Merging wireless/master (f8adaf0ae978 brcmfmac: Fix off by one bug in brcmf_count_20mhz_channels()) Merging driver-core.current/driver-core-linus (5e40d331bd72 Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security) Merging tty.current/tty-linus (9e82bf014195 Linux 3.17-rc5) Merging usb.current/usb-linus (0f33be009b89 Linux 3.17-rc6) Merging usb-gadget-fixes/fixes (0b93a4c838fa usb: dwc3: fix TRB completion when multiple TRBs are started) Merging usb-serial-fixes/usb-linus (dee80ad12d2b USB: cp210x: add support for Seluxit USB dongle) Merging staging.current/staging-linus (80213c03c415 Merge tag 'pci-v3.18-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci) Merging char-misc.current/char-misc-linus (9e82bf014195 Linux 3.17-rc5) Merging input-current/for-linus (447a8b858e4b Merge branch 'next' into for-linus) Merging md-current/for-linus (d47648fcf061 raid5: avoid finding "discard" stripe) Merging crypto-current/master (be34c4ef693f crypto: sha - Handle unaligned input data in generic sha256 and sha512.) Merging ide/master (a53dae49b2fe ide: use module_platform_driver()) Merging dwmw2/master (5950f0803ca9 pcmcia: remove RPX board stuff) Merging devicetree-current/devicetree/merge (e66c98c7a0ea of: Fix NULL dereference in selftest removal code) Merging rr-fixes/fixes (f49819560f53 virtio-rng: skip reading when we start to remove the device) Merging vfio-fixes/for-linus (239a87020b26 Merge branch 'for-joerg/arm-smmu/fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/will/linux into for-linus) Merging kselftest-fixes/fixes (ce6a144a0d01 selftests
Re: linux-next: Tree for Oct 14 (bcache)
On Tue, Oct 15, 2013 at 10:46:32AM +0200, Thierry Reding wrote: > Oh wait, they were applied right after the merges that broke. I hadn't > checked for that. Yeah, it's because I've been doing incremental build checks - the builds fail at the point the tree gets merged in. signature.asc Description: Digital signature
Re: linux-next: Tree for Oct 14 (bcache)
On Mon, Oct 14, 2013 at 09:27:23PM +0100, Mark Brown wrote: > On Mon, Oct 14, 2013 at 11:58:10AM -0700, Randy Dunlap wrote: > > On 10/14/13 07:48, Thierry Reding wrote: > > > > Gained a few conflicts, but nothing too exciting. x86 and ARM default > > > configurations build fine. There were some build failures unrelated to > > > Maybe you could build allmodconfig instead of a default config > > for more better coverage? I am seeing lots of build problems. > > I'd say in addition - if you look at the last tree I did it's got fixes > for all these tihngs I think. Strange, I didn't see any build fixes in it. Oh wait, they were applied right after the merges that broke. I hadn't checked for that. Thierry pgpwXh2n6atR3.pgp Description: PGP signature
Re: linux-next: Tree for Oct 14 (bcache)
On Mon, Oct 14, 2013 at 11:58:10AM -0700, Randy Dunlap wrote: > On 10/14/13 07:48, Thierry Reding wrote: > > Hi all, > > > > I've uploaded today's linux-next tree to the master branch of the > > repository below: > > > > git://gitorious.org/thierryreding/linux-next.git > > > > A next-20131014 tag is also provided for convenience. > > > > Gained a few conflicts, but nothing too exciting. x86 and ARM default > > configurations build fine. There were some build failures unrelated to > > Maybe you could build allmodconfig instead of a default config > for more better coverage? I am seeing lots of build problems. Ideally I'd be able to run allmodconfig for each merge, but I have neither the computing power nor the time to do that. I can add allmodconfig to the set of configurations that I build after the final merge, but I don't know how much good that is if I don't actually have any time to fix them up. Furthermore I'm beginning to think that perhaps we should create some infrastructure around this that would make it easier to submit requests for build coverage. Quite a few people seem to run autobuilders, so if all those could be harnessed to build linux-next (perhaps even on a per merge basis) that would give great coverage. > > the merge, most of which I fixed and added as patches on top of the > > final merge. > > > on x86_64: > > drivers/md/bcache/request.c: In function 'cached_dev_write': > drivers/md/bcache/request.c:1076:8: error: 'struct btree_op' has no member > named 'cache_bio' It's quite possible that I messed that up during the merge. The bcache conflicts weren't very trivial. This one in particular seems to be caused by a commit that went into 3.12-rc5 and one in the block tree's linux-next branch. Thierry pgpIEmUSuAB3C.pgp Description: PGP signature
Re: linux-next: Tree for Oct 14 (ceph)
On 10/14/13 07:48, Thierry Reding wrote: > Hi all, > > I've uploaded today's linux-next tree to the master branch of the > repository below: > > git://gitorious.org/thierryreding/linux-next.git > > A next-20131014 tag is also provided for convenience. > > Gained a few conflicts, but nothing too exciting. x86 and ARM default > configurations build fine. There were some build failures unrelated to > the merge, most of which I fixed and added as patches on top of the > final merge. on i386: fs/ceph/file.c: In function 'ceph_sync_read': fs/ceph/file.c:437:25: error: 'struct iov_iter' has no member named 'iov' fs/ceph/file.c:438:18: error: 'struct iov_iter' has no member named 'iov' fs/ceph/file.c:470:26: error: 'struct iov_iter' has no member named 'iov' fs/ceph/file.c:472:9: error: 'struct iov_iter' has no member named 'iov' fs/ceph/file.c:472:9: error: 'struct iov_iter' has no member named 'iov' fs/ceph/file.c:472:9: warning: comparison of distinct pointer types lacks a cast [enabled by default] fs/ceph/file.c: In function 'ceph_sync_direct_write': fs/ceph/file.c:586:24: error: 'struct iov_iter' has no member named 'iov' fs/ceph/file.c:587:14: error: 'struct iov_iter' has no member named 'iov' fs/ceph/file.c: In function 'ceph_sync_write': fs/ceph/file.c:737:18: warning: comparison of distinct pointer types lacks a cast [enabled by default] -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 14 (bcache)
On Mon, Oct 14, 2013 at 11:58:10AM -0700, Randy Dunlap wrote: > On 10/14/13 07:48, Thierry Reding wrote: > > Gained a few conflicts, but nothing too exciting. x86 and ARM default > > configurations build fine. There were some build failures unrelated to > Maybe you could build allmodconfig instead of a default config > for more better coverage? I am seeing lots of build problems. I'd say in addition - if you look at the last tree I did it's got fixes for all these tihngs I think. signature.asc Description: Digital signature
Re: linux-next: Tree for Oct 14 (bcache)
On 10/14/13 07:48, Thierry Reding wrote: > Hi all, > > I've uploaded today's linux-next tree to the master branch of the > repository below: > > git://gitorious.org/thierryreding/linux-next.git > > A next-20131014 tag is also provided for convenience. > > Gained a few conflicts, but nothing too exciting. x86 and ARM default > configurations build fine. There were some build failures unrelated to Maybe you could build allmodconfig instead of a default config for more better coverage? I am seeing lots of build problems. > the merge, most of which I fixed and added as patches on top of the > final merge. on x86_64: drivers/md/bcache/request.c: In function 'cached_dev_write': drivers/md/bcache/request.c:1076:8: error: 'struct btree_op' has no member named 'cache_bio' -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
linux-next: Tree for Oct 14
Hi all, I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131014 tag is also provided for convenience. Gained a few conflicts, but nothing too exciting. x86 and ARM default configurations build fine. There were some build failures unrelated to the merge, most of which I fixed and added as patches on top of the final merge. Thierry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
