Prev: warning from gcc version 4.6.0 20100416
Next: Watchdog: Adding support for ARM Primecell SP805 Watchdog
From: Stephen Rothwell on 11 Jun 2010 00:20
Hi all,

Changes since 20100610:

My fixes tree contains:
v4l-dvb: update gfp/slab.h includes
arm: update gfp/slab.h includes
davinci: update gfp/slab.h includes
ocfs2: update gfp/slab.h includes
acpi: update gfp/slab.h includes

The kbuild-current tree lost its build failure.

----------------------------------------------------------------------------

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/v2.6/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" as mentioned in the FAQ on the wiki
(see below).

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. After the
final fixups (if any), it is also built with powerpc allnoconfig (32 and
64 bit), ppc44x_defconfig and allyesconfig (minus
CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc
and sparc64 defconfig. These builds also have
CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and
CONFIG_DEBUG_INFO disabled when necessary.

Below is a summary of the state of the merge.

We are up to 164 trees (counting Linus' and 22 trees of patches pending
for Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.

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 Jan Dittmer for adding the linux-next tree to his build tests
at http://l4x.org/k/ , the guys at http://test.kernel.org/ and Randy
Dunlap for doing many randconfig builds.

There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel.

--
Cheers,
Stephen Rothwell sfr(a)canb.auug.org.au

$ git checkout master
$ git reset --hard stable
Merging origin/master
Merging fixes/fixes
Merging arm-current/master
Merging m68k-current/for-linus
Merging powerpc-merge/merge
Merging sparc-current/master
Merging scsi-rc-fixes/master
Merging net-current/master
Merging sound-current/for-linus
Merging pci-current/for-linus
Merging wireless-current/master
Merging kbuild-current/for-linus
Merging quilt/driver-core.current
Merging quilt/tty.current
Merging quilt/usb.current
Merging quilt/staging.current
Merging cpufreq-current/fixes
Merging input-current/for-linus
Merging md-current/for-linus
Merging audit-current/for-linus
Merging crypto-current/master
Merging ide-curent/master
Merging dwmw2/master
Merging gcl-current/merge
Merging arm/devel
Merging davinci/davinci-next
Merging i.MX/for-next
Merging msm/for-next
Merging omap/for-next
Merging pxa/for-next
Merging samsung/next-samsung
Merging avr32/avr32-arch
Merging blackfin/for-linus
Merging cris/for-next
Merging ia64/test
Merging m68k/for-next
Merging m68knommu/for-next
Merging microblaze/next
Merging mips/mips-for-linux-next
Merging parisc/next
Merging powerpc/next
Merging 4xx/next
Merging 52xx-and-virtex/next
CONFLICT (content): Merge conflict in drivers/serial/mpc52xx_uart.c
Merging galak/next
Merging s390/features
Merging sh/master
Merging genesis/master
CONFLICT (content): Merge conflict in include/linux/serial_sci.h
Merging sparc/master
Merging tile/master
Merging xtensa/master
Merging ceph/for-next
Merging cifs/master
Merging configfs/linux-next
Merging ecryptfs/next
CONFLICT (content): Merge conflict in fs/ecryptfs/main.c
Merging ext3/for_next
Merging ext4/next
Merging fatfs/master
Merging fuse/for-next
Merging gfs2/master
Merging jfs/next
Merging logfs/master
CONFLICT (content): Merge conflict in fs/logfs/logfs.h
Merging nfs/linux-next
Merging nfsd/nfsd-next
Merging nilfs2/for-next
Merging ocfs2/linux-next
Merging squashfs/master
Merging udf/for_next
Merging v9fs/for-next
Merging ubifs/linux-next
Merging xfs/master
Merging vfs/for-next
Merging pci/linux-next
Merging hid/for-next
Merging quilt/i2c
Merging bjdooks-i2c/next-i2c
CONFLICT (content): Merge conflict in arch/arm/plat-omap/i2c.c
CONFLICT (content): Merge conflict in drivers/i2c/busses/i2c-cpm.c
CONFLICT (content): Merge conflict in drivers/i2c/busses/i2c-mpc.c
Merging quilt/jdelvare-hwmon
Merging quilt/kernel-doc
Merging v4l-dvb/master
Merging kbuild/for-next
Merging kconfig/for-next
Merging ide/master
Merging libata/NEXT
Merging infiniband/for-next
Merging acpi/test
Merging idle-test/idle-test
Merging ieee1394/for-next
Merging ubi/linux-next
Merging kvm/linux-next
Merging dlm/next
Merging ibft/master
Merging swiotlb/master
Merging scsi/master
Merging async_tx/next
Merging net/master
Merging wireless/master
CONFLICT (content): Merge conflict in drivers/net/wireless/wl12xx/wl1271.h
CONFLICT (content): Merge conflict in drivers/net/wireless/wl12xx/wl1271_cmd.h
Merging mtd/master
Merging crypto/master
Merging sound/for-next
Merging cpufreq/next
Merging quilt/rr
CONFLICT (content): Merge conflict in kernel/module.c
Merging mmc/next
Merging input/next
Merging lsm/for-next
Merging block/for-next
Merging quilt/device-mapper
Merging embedded/master
Merging firmware/master
Merging pcmcia/master
Merging battery/master
Merging leds/for-mm
Merging backlight/for-mm
Merging kgdb/kgdb-next
Merging slab/for-next
Merging uclinux/for-next
Merging md/for-next
Merging mfd/for-next
Merging hdlc/hdlc-next
Merging drm/drm-next
CONFLICT (content): Merge conflict in drivers/gpu/drm/radeon/evergreen.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/radeon/r600.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/radeon/radeon_combios..c
CONFLICT (content): Merge conflict in drivers/gpu/drm/radeon/radeon_pm.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/radeon/rv770.c
Merging viafb/viafb-next
Merging voltage/for-next
Merging security-testing/next
Merging lblnet/master
Merging agp/agp-next
Merging uwb/for-upstream
Merging watchdog/master
Merging bdev/master
Merging dwmw2-iommu/master
Merging cputime/cputime
Merging osd/linux-next
Merging jc_docs/docs-next
Merging nommu/master
Merging trivial/for-next
Merging audit/for-next
Merging quilt/aoe
Merging suspend/linux-next
Merging bluetooth/master
Merging fsnotify/for-next
CONFLICT (delete/modify): fs/notify/inotify/inotify.c deleted in fsnotify/for-next and modified in HEAD. Version HEAD of fs/notify/inotify/inotify.c left in tree.
$ git rm -f fs/notify/inotify/inotify.c
Applying: fsnotify: update gfp/slab.h includes
Merging irda/for-next
CONFLICT (content): Merge conflict in drivers/net/irda/irda-usb.c
Merging drbd/for-jens
CONFLICT (content): Merge conflict in fs/fs-writeback.c
CONFLICT (content): Merge conflict in include/linux/drbd.h
Merging catalin/for-next
Merging alacrity/linux-next
Merging i7core_edac/linux_next
Merging devicetree/next-devicetree
Merging spi/next-spi
Merging omap_dss2/for-next
Merging tip/auto-latest
Merging edac-amd/for-next
Merging oprofile/for-next
Merging percpu/for-next
Merging workqueues/for-next
Merging sfi/sfi-test
Merging asm-generic/next
Merging drivers-x86/linux-next
Merging hwpoison/hwpoison
CONFLICT (content): Merge conflict in mm/memory-failure.c
Merging sysctl/master
Merging bkl-core/bkl/core
Merging bkl-procfs/bkl/procfs
Merging bkl-ioctl/bkl/ioctl
Merging quilt/driver-core
Merging quilt/tty
Merging quilt/usb
Merging staging-next/staging-next
Merging slabh/slabh
Merging scsi-post-merge/master
From: Andrew Morton on 11 Jun 2010 19:40
On Fri, 11 Jun 2010 14:17:38 +1000
Stephen Rothwell <sfr(a)canb.auug.org.au> wrote:

> 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/v2.6/next/ ).

Rusty broke your kernel!

oops: http://userweb.kernel.org/~akpm/IMG_20100611_155611.jpg

config: http://userweb.kernel.org/~akpm/stuff/config-akpm2-small.txt

(gdb) l *0xffffffff8105f9fb
0xffffffff8105f9fb is in get_ksymbol (kernel/module.c:2784).
2779 if (mod->symtab[i].st_shndx == SHN_UNDEF)
2780 continue;
2781
2782 /* We ignore unnamed symbols: they're uninformative
2783 * and inserted at a whim. */
2784 if (mod->symtab[i].st_value <= addr
2785 && mod->symtab[i].st_value > mod->symtab[best].st_value
2786 && *(mod->strtab + mod->symtab[i].st_name) != '\0'
2787 && !is_arm_mapping_symbol(mod->strtab + mod->symtab[i].st_name))
2788 best = i;

Current mainline is OK.

<someone broke netconsole too, I think...>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Rusty Russell on 15 Jun 2010 05:30
On Sat, 12 Jun 2010 09:01:24 am Andrew Morton wrote:
> On Fri, 11 Jun 2010 14:17:38 +1000
> Stephen Rothwell <sfr(a)canb.auug.org.au> wrote:
>
> > 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/v2.6/next/ ).
>
> Rusty broke your kernel!
>
> oops: http://userweb.kernel.org/~akpm/IMG_20100611_155611.jpg
>
> config: http://userweb.kernel.org/~akpm/stuff/config-akpm2-small.txt
>
> (gdb) l *0xffffffff8105f9fb
> 0xffffffff8105f9fb is in get_ksymbol (kernel/module.c:2784).
> 2779 if (mod->symtab[i].st_shndx == SHN_UNDEF)
> 2780 continue;
> 2781
> 2782 /* We ignore unnamed symbols: they're uninformative
> 2783 * and inserted at a whim. */
> 2784 if (mod->symtab[i].st_value <= addr
> 2785 && mod->symtab[i].st_value > mod->symtab[best].st_value
> 2786 && *(mod->strtab + mod->symtab[i].st_name) != '\0'
> 2787 && !is_arm_mapping_symbol(mod->strtab + mod->symtab[i].st_name))
> 2788 best = i;

Hmm, I can't reproduce this :( I'm only 32 bit here, have to dig out my
64-bit machine tomorrow.

One wonders why we're in get_ksymbol at all. Has something already gone
horribly wrong?

Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Andrew Morton on 15 Jun 2010 05:40
On Tue, 15 Jun 2010 18:56:37 +0930 Rusty Russell <rusty(a)rustcorp.com.au> wrote:

> On Sat, 12 Jun 2010 09:01:24 am Andrew Morton wrote:
> > On Fri, 11 Jun 2010 14:17:38 +1000
> > Stephen Rothwell <sfr(a)canb.auug.org.au> wrote:
> >
> > > 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/v2.6/next/ ).
> >
> > Rusty broke your kernel!
> >
> > oops: http://userweb.kernel.org/~akpm/IMG_20100611_155611.jpg
> >
> > config: http://userweb.kernel.org/~akpm/stuff/config-akpm2-small.txt
> >
> > (gdb) l *0xffffffff8105f9fb
> > 0xffffffff8105f9fb is in get_ksymbol (kernel/module.c:2784).
> > 2779 if (mod->symtab[i].st_shndx == SHN_UNDEF)
> > 2780 continue;
> > 2781
> > 2782 /* We ignore unnamed symbols: they're uninformative
> > 2783 * and inserted at a whim. */
> > 2784 if (mod->symtab[i].st_value <= addr
> > 2785 && mod->symtab[i].st_value > mod->symtab[best].st_value
> > 2786 && *(mod->strtab + mod->symtab[i].st_name) != '\0'
> > 2787 && !is_arm_mapping_symbol(mod->strtab + mod->symtab[i].st_name))
> > 2788 best = i;
>
> Hmm, I can't reproduce this :(

I haven't seen any reports from any other linux-next users either, so
I'm special.

> I'm only 32 bit here, have to dig out my
> 64-bit machine tomorrow.
>
> One wonders why we're in get_ksymbol at all. Has something already gone
> horribly wrong?

Nothing that I'm aware of. I guess I won't be getting a very good
trace if the trace uses get_ksymbol().

If it's still happening I'll debug it a bit. Need to find out why
netconsole went awol.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Andrew Morton on 23 Jun 2010 19:00
On Tue, 15 Jun 2010 18:56:37 +0930
Rusty Russell <rusty(a)rustcorp.com.au> wrote:

> On Sat, 12 Jun 2010 09:01:24 am Andrew Morton wrote:
> > On Fri, 11 Jun 2010 14:17:38 +1000
> > Stephen Rothwell <sfr(a)canb.auug.org.au> wrote:
> >
> > > 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/v2.6/next/ ).
> >
> > Rusty broke your kernel!
> >
> > oops: http://userweb.kernel.org/~akpm/IMG_20100611_155611.jpg
> >
> > config: http://userweb.kernel.org/~akpm/stuff/config-akpm2-small.txt
> >
> > (gdb) l *0xffffffff8105f9fb
> > 0xffffffff8105f9fb is in get_ksymbol (kernel/module.c:2784).
> > 2779 if (mod->symtab[i].st_shndx == SHN_UNDEF)
> > 2780 continue;
> > 2781
> > 2782 /* We ignore unnamed symbols: they're uninformative
> > 2783 * and inserted at a whim. */
> > 2784 if (mod->symtab[i].st_value <= addr
> > 2785 && mod->symtab[i].st_value > mod->symtab[best].st_value
> > 2786 && *(mod->strtab + mod->symtab[i].st_name) != '\0'
> > 2787 && !is_arm_mapping_symbol(mod->strtab + mod->symtab[i].st_name))
> > 2788 best = i;
>
> Hmm, I can't reproduce this :( I'm only 32 bit here, have to dig out my
> 64-bit machine tomorrow.
>
> One wonders why we're in get_ksymbol at all. Has something already gone
> horribly wrong?

Dunno - maybe it got into get_ksymbol() because something oopsed, and
oops tracing uses get_ksymbol(). There's no stack trace because stack
tracing uses get_ksymbol().

Anyway I retested next-20100623 and the verdict is ... you still suck!

I bisected it down to 4624469822455b4accc886557f6c997ccdd59066
("module: kallsyms functions take struct load_info"). I couldn't see
anything obviously wrong with it, but there's something screwy in
there..

<mooches off to bisect Yet Another Hang>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 |  Next  |  Last
Pages: 1 2
Prev: warning from gcc version 4.6.0 20100416
Next: Watchdog: Adding support for ARM Primecell SP805 Watchdog