* Re: linux-next: manual merge of the staging tree with the fbdev tree
From: Greg KH @ 2011-08-24 4:48 UTC (permalink / raw)
To: Stephen Rothwell
Cc: linux-next, linux-kernel, Aaro Koskinen, Laurent Pinchart,
Paul Mundt
In-Reply-To: <20110824144134.00bd3a688fb39b5d5563ff13@canb.auug.org.au>
On Wed, Aug 24, 2011 at 02:41:34PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in
> drivers/staging/xgifb/XGI_main_26.c between commit c42a3d543d2b
> ("staging: xgifb: use display information in info not in var for
> panning") from the fbdev tree and commit c39aada6926c ("staging: xgifb:
> eliminate #ifdef XGIFB_PAN") from the staging tree.
>
> Just context changes. I fixed it up (see below) and can carry the fix as
> necessary.
Wonderful, thanks for the fix.
greg k-h
^ permalink raw reply
* linux-next: manual merge of the moduleh tree with the staging tree
From: Stephen Rothwell @ 2011-08-24 5:00 UTC (permalink / raw)
To: Paul Gortmaker; +Cc: linux-next, linux-kernel, Jonathan Cameron, Greg KH
Hi Paul,
Today's linux-next merge of the moduleh tree got a conflict in
drivers/staging/iio/accel/adis16220_core.c between commit 7991029a55fa
("staging:iio:accel:adis16220 iio_chan_spec conversion") from the staging
tree and commit dcf6be043de1 ("staging: Add module.h to drivers/staging
users") from the moduleh tree.
Just context changes. I have fixed it up (see below) and can carry the
fix as necessary.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
diff --cc drivers/staging/iio/accel/adis16220_core.c
index 075e40f,e119874..0000000
--- a/drivers/staging/iio/accel/adis16220_core.c
+++ b/drivers/staging/iio/accel/adis16220_core.c
@@@ -13,6 -16,8 +13,7 @@@
#include <linux/spi/spi.h>
#include <linux/slab.h>
#include <linux/sysfs.h>
-#include <linux/list.h>
+ #include <linux/module.h>
#include "../iio.h"
#include "../sysfs.h"
^ permalink raw reply
* linux-next: build failure after merge of the final tree (staging tree related)
From: Stephen Rothwell @ 2011-08-24 5:47 UTC (permalink / raw)
To: Greg KH; +Cc: linux-next, linux-kernel, edwin_rong
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
Hi ,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/staging/rts5139/rts51x_scsi.c: In function 'inquiry':
drivers/staging/rts5139/rts51x_scsi.c:498:2: error: implicit declaration of function 'vmalloc'
drivers/staging/rts5139/xd.c: In function 'xd_init_l2p_tbl':
drivers/staging/rts5139/xd.c:745:2: error: implicit declaration of function 'vmalloc'
drivers/staging/rts5139/xd.c: In function 'free_zone':
drivers/staging/rts5139/xd.c:771:3: error: implicit declaration of function 'vfree'
drivers/staging/rts5139/ms.c: In function 'ms_init_l2p_tbl':
drivers/staging/rts5139/ms.c:2214:2: error: implicit declaration of function 'vmalloc'
drivers/staging/rts5139/ms.c:2257:3: error: implicit declaration of function 'vfree'
Caused by commit 1dac4186bcc6 ("Staging: add driver for Realtek RTS5139
cardreader").
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply
* linux-next: Tree for Aug 24
From: Stephen Rothwell @ 2011-08-24 6:04 UTC (permalink / raw)
To: linux-next; +Cc: LKML
[-- Attachment #1: Type: text/plain, Size: 16194 bytes --]
Hi all,
The powerpc allyesconfig build still fails today.
Changes since 20110823:
New tree: kvmtool
The security tree lost its build failure.
The ptrace tree gained a build failure (yeaterday) for which I have
reveretd a commit.
The tty tree gained a build failure so I used the version from
next-20110823.
The staging tree gained a conflict against the fbdev tree and a build
failure for which I reverted a commit.
The moduleh tree gained a conflict against the staging tree.
----------------------------------------------------------------------------
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 199 trees (counting Linus' and 28 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 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@canb.auug.org.au
$ git checkout master
$ git reset --hard stable
Merging origin/master
Merging fixes/fixes
Merging kbuild-current/rc-fixes
Merging arm-current/master
Merging m68k-current/for-linus
Merging powerpc-merge/merge
Merging 52xx-and-virtex-current/powerpc/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 driver-core.current/driver-core-linus
Merging tty.current/tty-linus
Merging usb.current/usb-linus
Merging staging.current/staging-linus
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 sh-current/sh-fixes-for-linus
Merging rmobile-current/rmobile-fixes-for-linus
Merging fbdev-current/fbdev-fixes-for-linus
Merging devicetree-current/devicetree/merge
Merging spi-current/spi/merge
Merging arm/for-next
Merging arm-lpae/for-next
CONFLICT (content): Merge conflict in arch/arm/include/asm/pgalloc.h
CONFLICT (content): Merge conflict in arch/arm/include/asm/pgtable.h
CONFLICT (content): Merge conflict in arch/arm/include/asm/tlb.h
Merging arm-soc/for-next
Merging at91/at91-next
Merging davinci/davinci-next
Merging i.MX/for-next
Merging linux-spec/for-next
Merging msm/for-next
CONFLICT (content): Merge conflict in arch/arm/mach-msm/io.c
Merging omap/for-next
Merging pxa/for-next
Merging samsung/next-samsung
Merging s5p/for-next
Merging tegra/for-next
Merging ux500-core/ux500-core
Merging xilinx/arm-next
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 openrisc/for-upstream
Merging parisc/for-next
Merging powerpc/next
Merging 4xx/next
Merging 52xx-and-virtex/powerpc/next
Merging galak/next
Merging s390/features
Merging sh/sh-latest
Merging rmobile/rmobile-latest
Merging sparc/master
Merging tile/master
Merging unicore32/unicore32
Merging xtensa/master
Merging ceph/for-next
Merging cifs/master
Merging configfs/linux-next
Merging ecryptfs/next
Merging ext3/for_next
Merging ext4/dev
Merging fatfs/master
Merging fuse/for-next
Merging gfs2/master
Merging hfsplus/for-next
Merging jfs/next
Merging logfs/master
Merging nfs/linux-next
Merging nfsd/nfsd-next
Merging nilfs2/for-next
Merging ocfs2/linux-next
Merging omfs/for-next
Merging squashfs/master
Merging udf/for_next
Merging v9fs/for-next
Merging ubifs/linux-next
Merging xfs/master
Merging vfs/for-next
Merging vfs-scale/vfs-scale-working
Merging pci/linux-next
Merging hid/for-next
Merging quilt/i2c
Merging bjdooks-i2c/next-i2c
Merging quilt/jdelvare-hwmon
Merging hwmon-staging/hwmon-next
Merging quilt/kernel-doc
Merging docs/docs-move
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 powertools/tools-test
Merging cpupowerutils/master
Merging ieee1394/for-next
Merging ubi/linux-next
Merging dlm/next
Merging swiotlb/master
Merging ibft/master
Merging scsi/master
Merging iscsi-target/for-next
Merging slave-dma/next
Merging async_tx/next
Merging net/master
CONFLICT (delete/modify): arch/powerpc/configs/40x/hcu4_defconfig deleted in HEAD and modified in net/master. Version net/master of arch/powerpc/configs/40x/hcu4_defconfig left in tree.
CONFLICT (content): Merge conflict in drivers/net/Kconfig
CONFLICT (content): Merge conflict in drivers/net/Makefile
$ git rm -f arch/powerpc/configs/40x/hcu4_defconfig
Applying: powerpc: update ppc64_defconfig for net device movement
Applying: sparc: update sparc32_defconfig for net device movement
Applying: sparc: update sparc64_defconfig for net device movement
Merging wireless/master
Merging bluetooth/master
Merging mtd/master
Merging l2-mtd/master
CONFLICT (content): Merge conflict in drivers/mtd/maps/lantiq-flash.c
Merging crypto/master
Merging sound/for-next
Merging sound-asoc/for-next
Merging cpufreq/next
Merging quilt/rr
Merging input/next
Merging input-mt/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
CONFLICT (content): Merge conflict in drivers/leds/Kconfig
Merging backlight/for-mm
Merging mmc/mmc-next
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
Merging fbdev/master
Merging viafb/viafb-next
Merging omap_dss2/for-next
Merging voltage/for-next
Merging security/next
CONFLICT (content): Merge conflict in fs/ocfs2/xattr.c
Merging selinux/master
Merging lblnet/master
Merging agp/agp-next
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 pm/linux-next
CONFLICT (content): Merge conflict in arch/s390/include/asm/thread_info.h
CONFLICT (content): Merge conflict in drivers/mfd/twl4030-irq.c
Merging apm/for-next
Merging fsnotify/for-next
Merging irda/for-next
Merging i7core_edac/linux_next
Merging i7300_edac/linux_next
CONFLICT (content): Merge conflict in arch/x86/kernel/cpu/mcheck/mce.c
Merging devicetree/devicetree/next
CONFLICT (content): Merge conflict in drivers/of/base.c
Merging spi/spi/next
Merging gpio/gpio/next
Merging tip/auto-latest
CONFLICT (content): Merge conflict in arch/x86/mm/fault.c
Merging rcu/rcu/next
Merging kvm/linux-next
Merging oprofile/for-next
Merging ptrace/ptrace
[master 12688b4] Revert "signal: Add block_sigmask() for adding sigmask to current->blocked"
Merging xen/upstream/xen
Merging xen-two/linux-next
Merging xen-pvhvm/linux-next
Merging edac-amd/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
Merging sysctl/master
Merging namespace/master
Merging regmap/for-next
Merging driver-core/driver-core-next
Merging tty/tty-next
$ git reset --hard HEAD^
Merging refs/next/20110823/tty
Merging usb/usb-next
Applying: usb: include module.h in the DesignWare USB3 DRD driver
Merging staging/staging-next
CONFLICT (content): Merge conflict in drivers/staging/xgifb/XGI_main_26.c
Merging bkl-config/config
Merging tmem/linux-next
Merging writeback/next
Merging arm-dt/devicetree/arm-next
Merging moduleh/module.h-split
CONFLICT (content): Merge conflict in drivers/staging/iio/accel/adis16220_core.c
CONFLICT (content): Merge conflict in include/linux/dmaengine.h
Applying: dm: use export.h instead of module.h where possible
Applying: block: bsg-lib.c needs export.h not module.h
Applying: PM: EXPORT_SYMBOL needs export.h
Merging kvmtool/master
CONFLICT (content): Merge conflict in include/net/9p/9p.h
Merging scsi-post-merge/merge-base:master
$ git checkout akpm
Applying: Expand root=PARTUUID=UUID syntax to support selecting a root partition by
Applying: This patch makes two changes:
Applying: On thread exit shm_exit_ns() is called, it uses shm_ids(ns).rw_mutex. It
Applying: Because of x86-implement-strict-user-copy-checks-for-x86_64.patch
Applying: When no floppy is found the module code can be released while a timer
Applying: The parameter's origin type is long. On an i386 architecture, it can
Applying: Add support for Aspire 1410 BIOS v1.3314. Fixes the following error:
Applying: This makes the iris driver use the platform API, so it is properly exposed
Applying: On x86_32 casting the unsigned int result of get_random_int() to long may
Applying: This new driver replaces the old PCEngines Alix 2/3 LED driver with a new
Applying: Cc: Ed Wildgoose <git@wildgooses.com>
Applying: Replace the bubble sort in sanitize_e820_map() with a call to the generic
Applying: The x86 timer interrupt handler is the only handler not traced in the
Applying: The current interrupt traces from irq_handler_entry and irq_handler_exit
Applying: Don't allow everybody to use a modem.
Applying: The address limit is already set in flush_old_exec() so this
Applying: A call to va_copy() should always be followed by a call to va_end() in the
Applying: Don't dereference em if it's NULL or an error pointer.
Applying: Some messing with error codes to return 0 on out id's and match
Applying: fb_set_suspend() must be called with the console semaphore held, which
Applying: hwmon was using an idr with a NULL pointer, so convert to an
Applying: A straightforward looking use of idr for a device id.
Applying: The address limit is already set in flush_old_exec() so this
Applying: The address limit is already set in flush_old_exec() so this
Applying: Add new check (assert_init) to make sure objects are initialized and
Applying: del_timer_sync() calls debug_object_assert_init() to assert that a timer
Applying: ext4_{set,clear}_bit() is defined as __test_and_{set,clear}_bit_le() for
Applying: The dqc_bitmap field of struct ocfs2_local_disk_chunk is 32-bit aligned,
Applying: The address limit is already set in flush_old_exec() so those calls to
Applying: When do pci remove/rescan on system that have more iommus, got
Applying: The current implementation of dmi_name_in_vendors() is an invitation to
Applying: For headers that get exported to userland and make use of u32 style
Applying: Fix sparse warnings of right shift bigger than source value size:
Applying: We leak in drivers/scsi/aacraid/commctrl.c::aac_send_raw_srb() :
Applying: Some mangling of errors was necessary to maintain current interface.
Applying: This does involve additional use of the spin lock in idr.c. Is this an
Applying: Instead of open coding this function use kstrtoul_from_user() directly.
Applying: brd_make_request() always returns 0, which doesn't make much sense.
Applying: The address limit is already set in flush_old_exec() so this assignment of
Applying: The basic idea behind cross memory attach is to allow MPI programs doing
Applying: - Add x86_64 specific wire up
Applying: acct_isolated of compaction uses page_lru_base_type which returns only
Applying: Change ISOLATE_XXX macro with bitwise isolate_mode_t type. Normally,
Applying: In async mode, compaction doesn't migrate dirty or writeback pages. So,
Applying: In __zone_reclaim case, we don't want to shrink mapped page. Nonetheless,
Applying: unmap_and_move() is one a big messy function. Clean it up.
Applying: radix_tree_tag_get()'s BUG (when it sees a tag after saw_unset_tag) was
Applying: per-task block plug can reduce block queue lock contention and increase
Applying: The tracing ring-buffer used this function briefly, but not anymore.
Applying: After selecting a task to kill, the oom killer iterates all processes and
Applying: Remove PageSwapBacked (!page_is_file_cache) cases from
Applying: Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Applying: The current implementation of the /dev/hpet driver couples opening the
Applying: smp_call_function() only lets all other CPUs execute a specific function,
Applying: auto_demotion_disable is called only for online CPUs. For hotplugged
Applying: Enabling DEBUG_STRICT_USER_COPY_CHECKS causes the following warning:
Applying: Strict user copy checks are only really supported on x86_32 even though
Applying: The help text for this config is duplicated across the x86, parisc, and
Applying: s/lib-/obj-/ for usercopy.o
Applying: After an "unexpected" reboot, I found this Oops in my logs:
Applying: In the move of the lis3 driver, the hp_accel.c file got dropped from the
Applying: Add axis correction for HP EliteBook 2730p.
Applying: Add axis correction for HP EliteBook 8540w.
Applying: Add axis correction for HP ProBook 6555b.
Applying: Adapt the help text for CONFIG_HP_ACCEL to the move of
Applying: Signed-off-by: Ilkka Koskinen <ilkka.koskinen@nokia.com>
Applying: Signed-off-by: Ilkka Koskinen <ilkka.koskinen@nokia.com>
Applying: Change exported functions to use the device given as parameter
Applying: Signed-off-by: Ilkka Koskinen <ilkka.koskinen@nokia.com>
Applying: Add V2 of the LED driver for a single timer channel for the TPU hardware
Applying: Add support for slice by 8 to existing crc32 algorithm. Also modify
Applying: don't include asm/msr.h
Applying: This is the one use of an ida that doesn't retry on receiving -EAGAIN.
Applying: One can get this information from minix/inode.c, but adding the
Applying: Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Applying: Force this on for -next/mm testing purposes.
Applying: Add a proc_dointvec_bool() sysctl handler for cases where the input value
Applying: Use the new proc_do_intvec_bool() handler for various boolean inputs.
Applying: Add a proc_dointvec_unsigned() sysctl handler for positive value cases.
Applying: Cc: Alexey Dobriyan <adobriyan@gmail.com>
Applying: Use the new proc_do_intvec_unsigned() handler for various unsigned inputs.
Applying: A default echo function has been provided so it is no longer an error when
Applying: This client driver allows you to use a GPIO pin as a source for PPS
Applying: remove unneeded cast of void*
Applying: Straightforward. As an aside, the ida_init calls are not needed as far as
Merging akpm
Applying: do_mounts: remove __init_data from root_wait
[master 9cba48a] Revert "Staging: add driver for Realtek RTS5139 cardreader"
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply
* Re: linux next: Native Linux KVM tool inclusion request
From: Avi Kivity @ 2011-08-24 8:31 UTC (permalink / raw)
To: Pekka Enberg
Cc: Christoph Hellwig, Sasha Levin, Stephen Rothwell, linux-kernel,
Ingo Molnar, Andrew Morton, Linus Torvalds, linux-next
In-Reply-To: <CAOJsxLEgm_-N6297kHqSjFLCtX-Vd204S=+4Q=+GW9HYiWj1eg@mail.gmail.com>
On 08/23/2011 08:08 AM, Pekka Enberg wrote:
> As for changes, we've implemented rootfs over 9p with "kvm run"
> booting to host filesystem "/bin/sh" by default.
Isn't this dangerous? Users expect virtualization to land them in
sandbox, but here an rm -rf / in the guest will happily junk the host
filesystem.
> It still needs some
> work and we hope to enable networking too. We also have patches to use
> overlayfs so that the guest is able to use host filesystem in
> copy-on-write manner.
>
Still dangerous (but just to the guest), since it's not a true
snapshot. If the host filesystem changes underneath the guest, it will
see partial and incoherent updates. Copy-on-write only works if the
host filesystem doesn't change.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
^ permalink raw reply
* Re: [PATCH -next v2] usb: fix dwc3 build when USB_GADGET_DWC3 is not enabled
From: Felipe Balbi @ 2011-08-24 8:51 UTC (permalink / raw)
To: Randy Dunlap
Cc: balbi, Stephen Rothwell, akpm, gregkh, linux-next, LKML,
linux-omap
In-Reply-To: <20110823125247.fbbf9636.rdunlap@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
Hi,
On Tue, Aug 23, 2011 at 12:52:47PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Fix build error when CONFIG_USB_GADGET_DWC3 is not enabled:
>
> ERROR: "dwc3_send_gadget_ep_cmd" [drivers/usb/dwc3/dwc3.ko] undefined!
>
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
Thanks Randy
Acked-by: Felipe Balbi <balbi@ti.com>
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply
* Re: linux next: Native Linux KVM tool inclusion request
From: Pekka Enberg @ 2011-08-24 9:19 UTC (permalink / raw)
To: Avi Kivity
Cc: Christoph Hellwig, Sasha Levin, Stephen Rothwell, linux-kernel,
Ingo Molnar, Andrew Morton, Linus Torvalds, linux-next
In-Reply-To: <4E54B6E2.2030203@redhat.com>
On 8/24/11 11:31 AM, Avi Kivity wrote:
> On 08/23/2011 08:08 AM, Pekka Enberg wrote:
>> As for changes, we've implemented rootfs over 9p with "kvm run"
>> booting to host filesystem "/bin/sh" by default.
>
> Isn't this dangerous? Users expect virtualization to land them in
> sandbox, but here an rm -rf / in the guest will happily junk the host
> filesystem.
Not really because I never run the tool as root. However, you're right that
we should not default to /bin/sh if you're root.
>> It still needs some
>> work and we hope to enable networking too. We also have patches to use
>> overlayfs so that the guest is able to use host filesystem in
>> copy-on-write manner.
>
> Still dangerous (but just to the guest), since it's not a true
> snapshot. If the host filesystem changes underneath the guest, it
> will see partial and incoherent updates. Copy-on-write only works if
> the host filesystem doesn't change.
That's a generic problem with overlayfs based solutions, isn't it? We're
planning
to use copy-on-write only on files that aren't supposed to change that
often -
like /usr and /lib. I suppose we should force shared files to be
read-only in
the guest.
Pekka
^ permalink raw reply
* Re: linux next: Native Linux KVM tool inclusion request
From: Avi Kivity @ 2011-08-24 9:33 UTC (permalink / raw)
To: Pekka Enberg
Cc: Christoph Hellwig, Sasha Levin, Stephen Rothwell, linux-kernel,
Ingo Molnar, Andrew Morton, Linus Torvalds, linux-next
In-Reply-To: <4E54C210.1030204@kernel.org>
On 08/24/2011 12:19 PM, Pekka Enberg wrote:
> On 8/24/11 11:31 AM, Avi Kivity wrote:
>> On 08/23/2011 08:08 AM, Pekka Enberg wrote:
>>> As for changes, we've implemented rootfs over 9p with "kvm run"
>>> booting to host filesystem "/bin/sh" by default.
>>
>> Isn't this dangerous? Users expect virtualization to land them in
>> sandbox, but here an rm -rf / in the guest will happily junk the host
>> filesystem.
>
> Not really because I never run the tool as root. However, you're right
> that
> we should not default to /bin/sh if you're root.
Well, just trashing /home/penberg would be bad too, no? (my recent
experience indicates it's not that catastrophic - anything important
sits on a server somewhere and the local data is just a cache).
>>
>> Still dangerous (but just to the guest), since it's not a true
>> snapshot. If the host filesystem changes underneath the guest, it
>> will see partial and incoherent updates. Copy-on-write only works if
>> the host filesystem doesn't change.
>
> That's a generic problem with overlayfs based solutions, isn't it?
> We're planning
> to use copy-on-write only on files that aren't supposed to change that
> often -
> like /usr and /lib.
So the guest won't see bad data that often?
Overlay works fine if the host tree is readonly. So if you have a
separate tree for guests, you can share it with any number of them.
Just don't share the host root.
Note this probably isn't a problem booting to /bin/bash, just booting a
full-featured guest with package management and other database-like apps
that expect exclusive control over their data.
> I suppose we should force shared files to be read-only in
> the guest.
>
Yes, that's safer.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
^ permalink raw reply
* Re: linux next: Native Linux KVM tool inclusion request
From: Pekka Enberg @ 2011-08-24 9:38 UTC (permalink / raw)
To: Avi Kivity
Cc: Christoph Hellwig, Sasha Levin, Stephen Rothwell, linux-kernel,
Ingo Molnar, Andrew Morton, Linus Torvalds, linux-next
In-Reply-To: <4E54C55A.7010109@redhat.com>
On 8/24/11 12:33 PM, Avi Kivity wrote:
> Well, just trashing /home/penberg would be bad too, no? (my recent
> experience indicates it's not that catastrophic - anything important
> sits on a server somewhere and the local data is just a cache).
Sure. We actually are planning something like this:
Private to guest:
/dev
/etc
/home
/proc
/sys
/var
Shared from host rootfs:
/bin
/lib
/sbin
/usr
Full host rootfs mounted at:
/host/
And no, we're not planning to boot full distro init. The only thing we
really want in addition to /bin/sh is to enable networking.
Pekka
^ permalink raw reply
* Re: linux-next: build warning after merge of the rcu tree
From: Paul E. McKenney @ 2011-08-24 12:27 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel
In-Reply-To: <20110824142337.78715e4d6f9db2de68d87fe4@canb.auug.org.au>
On Wed, Aug 24, 2011 at 02:23:37PM +1000, Stephen Rothwell wrote:
> Hi Paul,
>
> After merging the rcu tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> kernel/rtmutex.c: In function '__rt_mutex_slowlock':
> kernel/rtmutex.c:605:3: warning: suggest parentheses around assignment used as truth value
There actually already are parentheses around it, and the first pass
through the loop it is uninitialized at that point. But hey, that
is gcc for you! Does the patch below cure it?
> Introduced by commit 83841f021d4b ("rcu: Permit rt_mutex_unlock() with
> irqs disabled").
If it does, then I will fold into that commit.
Thanx, Paul
------------------------------------------------------------------------
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
diff --git a/kernel/rtmutex.c b/kernel/rtmutex.c
index 0222e34..2548f44 100644
--- a/kernel/rtmutex.c
+++ b/kernel/rtmutex.c
@@ -602,7 +602,8 @@ __rt_mutex_slowlock(struct rt_mutex *lock, int state,
raw_spin_unlock(&lock->wait_lock);
- if (was_disabled = irqs_disabled())
+ was_disabled = irqs_disabled();
+ if (was_disabled)
local_irq_enable();
debug_rt_mutex_print_deadlock(waiter);
^ permalink raw reply related
* linux-next tree addition request (fbdev)
From: Florian Tobias Schandinat @ 2011-08-24 13:40 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-fbdev@vger.kernel.org, Paul Mundt
Hi Stephen,
can you please add
git://github.com/schandinat/linux-2.6.git fbdev-next
to linux-next. It collects patches for the frame buffer subsystem.
Can you please add the linux-fbdev@vger.kernel.org mailing list as additional
contact for warnings/errors/problems?
You probably want to drop Paul's fbdev branches as they contain some outdated
patches that will conflict with the newer versions.
Thanks,
Florian Tobias Schandinat
^ permalink raw reply
* Re: linux-next tree addition request (fbdev)
From: Stephen Rothwell @ 2011-08-24 14:33 UTC (permalink / raw)
To: Florian Tobias Schandinat
Cc: linux-next, linux-fbdev@vger.kernel.org, Paul Mundt
In-Reply-To: <4E54FF5E.5050308@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
Hi Florian,
On Wed, 24 Aug 2011 13:40:46 +0000 Florian Tobias Schandinat <FlorianSchandinat@gmx.de> wrote:
>
> can you please add
>
> git://github.com/schandinat/linux-2.6.git fbdev-next
>
> to linux-next. It collects patches for the frame buffer subsystem.
> Can you please add the linux-fbdev@vger.kernel.org mailing list as additional
> contact for warnings/errors/problems?
>
> You probably want to drop Paul's fbdev branches as they contain some outdated
> patches that will conflict with the newer versions.
OK, Paul is still listed as the frame buffer subsystem maintainer, so I
will need an Ack from him. When I get that, I will replace his tree with
yours. I assume someone will update the MAINTAINERS file.
I also have another tree from Paul (called fbdev-current) that contained
fixes for Linus' current release. I also assume that that tree will be
dropped (unless you have a new version of that as well).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply
* Re: linux-next: build failure after merge of the final tree (ptrace tree related)
From: Oleg Nesterov @ 2011-08-24 15:16 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Tejun Heo, linux-next, linux-kernel, Matt Fleming, David Miller
In-Reply-To: <20110823160309.112ad0f4922be8605b61c8dd@canb.auug.org.au>
Hi Stephen,
sorry for delay.
On 08/23, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (sparc64 defconfig)
> failed like this:
>
> kernel/signal.c: In function 'block_sigmask':
> kernel/signal.c:2333:26: error: 'SA_NODEFER' undeclared (first use in this function)
>
> Caused by commit 932e5a25b9cf ("signal: Add block_sigmask() for adding
> sigmask to current->blocked").
Yes. My bad. I've reset this commit.
> Sparc seems to use SA_NOMASK in the
> equivalent bit of code and has no SA_NODEFER definition.
Yes, I'll push the updated patch(es).
Thanks!
Oleg.
^ permalink raw reply
* Re: linux-next: Tree for Aug 24 (dynamic_debug)
From: Randy Dunlap @ 2011-08-24 17:25 UTC (permalink / raw)
To: Stephen Rothwell, Jason Baron, Bart Van Assche; +Cc: linux-next, LKML
In-Reply-To: <20110824160404.ebad6370aee2cad82a990142@canb.auug.org.au>
On Wed, 24 Aug 2011 16:04:04 +1000 Stephen Rothwell wrote:
> Hi all,
When CONFIG_NET is not enabled (I see this on i386 builds):
lib/built-in.o: In function `__dynamic_netdev_dbg':
(.text+0x9fda): undefined reference to `__netdev_printk'
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
^ permalink raw reply
* Re: linux-next: Tree for Aug 24 (dynamic_debug)
From: Jason Baron @ 2011-08-24 19:32 UTC (permalink / raw)
To: Randy Dunlap; +Cc: Stephen Rothwell, Bart Van Assche, linux-next, LKML, greg
In-Reply-To: <20110824102551.8fc076b5.rdunlap@xenotime.net>
On Wed, Aug 24, 2011 at 10:25:51AM -0700, Randy Dunlap wrote:
> On Wed, 24 Aug 2011 16:04:04 +1000 Stephen Rothwell wrote:
>
> > Hi all,
>
> When CONFIG_NET is not enabled (I see this on i386 builds):
>
> lib/built-in.o: In function `__dynamic_netdev_dbg':
> (.text+0x9fda): undefined reference to `__netdev_printk'
>
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
Ok, we probably want something, like below, although something keeps
selecting CONFIG_NET, when I try to unset it, in my .config...so not yet
tested, but should work.
Thanks,
-Jason
diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
index ee3b9ba..e4760de 100644
--- a/lib/dynamic_debug.c
+++ b/lib/dynamic_debug.c
@@ -504,6 +504,8 @@ int __dynamic_dev_dbg(struct _ddebug *descriptor,
}
EXPORT_SYMBOL(__dynamic_dev_dbg);
+#ifdef CONFIG_NET
+
int __dynamic_netdev_dbg(struct _ddebug *descriptor,
const struct net_device *dev, const char *fmt, ...)
{
@@ -528,6 +530,8 @@ int __dynamic_netdev_dbg(struct _ddebug *descriptor,
}
EXPORT_SYMBOL(__dynamic_netdev_dbg);
+#endif
+
static __initdata char ddebug_setup_string[1024];
static __init int ddebug_setup_query(char *str)
{
^ permalink raw reply related
* Re: linux-next: Tree for Aug 24 (dynamic_debug)
From: Randy Dunlap @ 2011-08-24 19:42 UTC (permalink / raw)
To: Jason Baron; +Cc: Stephen Rothwell, Bart Van Assche, linux-next, LKML, greg
In-Reply-To: <20110824193244.GA2540@redhat.com>
On Wed, 24 Aug 2011 15:32:45 -0400 Jason Baron wrote:
> On Wed, Aug 24, 2011 at 10:25:51AM -0700, Randy Dunlap wrote:
> > On Wed, 24 Aug 2011 16:04:04 +1000 Stephen Rothwell wrote:
> >
> > > Hi all,
> >
> > When CONFIG_NET is not enabled (I see this on i386 builds):
> >
> > lib/built-in.o: In function `__dynamic_netdev_dbg':
> > (.text+0x9fda): undefined reference to `__netdev_printk'
> >
> > ---
> > ~Randy
> > *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> Ok, we probably want something, like below, although something keeps
> selecting CONFIG_NET, when I try to unset it, in my .config...so not yet
> tested, but should work.
Yes, that works. Thanks.
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
> Thanks,
>
> -Jason
>
>
> diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
> index ee3b9ba..e4760de 100644
> --- a/lib/dynamic_debug.c
> +++ b/lib/dynamic_debug.c
> @@ -504,6 +504,8 @@ int __dynamic_dev_dbg(struct _ddebug *descriptor,
> }
> EXPORT_SYMBOL(__dynamic_dev_dbg);
>
> +#ifdef CONFIG_NET
> +
> int __dynamic_netdev_dbg(struct _ddebug *descriptor,
> const struct net_device *dev, const char *fmt, ...)
> {
> @@ -528,6 +530,8 @@ int __dynamic_netdev_dbg(struct _ddebug *descriptor,
> }
> EXPORT_SYMBOL(__dynamic_netdev_dbg);
>
> +#endif
> +
> static __initdata char ddebug_setup_string[1024];
> static __init int ddebug_setup_query(char *str)
> {
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
^ permalink raw reply
* mmotm 2011-08-24-14-08 uploaded
From: akpm @ 2011-08-24 21:09 UTC (permalink / raw)
To: mm-commits, linux-kernel, linux-mm, linux-fsdevel, linux-next
The mm-of-the-moment snapshot 2011-08-24-14-08 has been uploaded to
http://userweb.kernel.org/~akpm/mmotm/
It contains the following patches against 3.1-rc3:
(patches marked "*" will be included in linux-next)
origin.patch
headers_check-is-broken.patch
samples-hidraw-is-busted.patch
* drivers-misc-ptic-add-missing-includes.patch
* alpha-unbreak-osf_setsysinfossi_nvpairs.patch
* alpha-unbreak-osf_setsysinfossi_nvpairs-checkpatch-fixes.patch
* w1-fix-for-loop-in-w1_f29_remove_slave.patch
* maintainers-evgeniy-has-moved.patch
* memcg-pin-execution-to-current-cpu-while-draining-stock.patch
* scripts-get_maintainerpl-update-linuss-git-repository.patch
* checkpatch-add-missing-warn-argument-for-min_t-and-max_t-tests.patch
* drivers-char-msm_smd_pktc-dont-use-is_err.patch
* mm-fix-a-vmscan-warning.patch
* maintainers-paul-menage-has-moved.patch
* kernel-printk-do-not-turn-off-bootconsole-in-printk_late_init-if-keep_bootcon.patch
* vmscan-clear-zone_congested-for-zone-with-good-watermark-resend.patch
* rapidio-fix-use-of-non-compatible-registers.patch
* drivers-video-backlight-ep93xx_blc-add-missing-include-of-linux-moduleh.patch
* leds-add-missing-include-of-linux-moduleh.patch
* memcg-make-oom_lock-0-and-1-based-rather-than-coutner.patch
* backlight-add-a-callback-notify_after-for-backlight-control.patch
* backlight-fix-module-alias-prefix-for-adp8870_bl.patch
* drivers-misc-fsa9480-fix-a-leak-of-the-irq-during-init-failure.patch
* drivers-misc-ab8500-pwmc-fix-modalias.patch
* cris-add-arch-cris-include-asm-serialh.patch
* drivers-leds-leds-bd2802c-bd2802_unregister_led_classdev-should-unregister-all-registered-leds.patch
linux-next.patch
i-need-old-gcc.patch
arch-alpha-kernel-systblss-remove-debug-check.patch
* mm-mempolicyc-make-copy_from_user-provably-correct.patch
* floppy-use-del_timer_sync-in-init-cleanup.patch
* drm-fix-kconfig-unmet-dependency-warning.patch
* sched-fix-a-memory-leak-in-__sdt_free.patch
* kernel-timec-change-jiffies_to_clock_t-input-parameters-type-to-unsigned-long.patch
* readlinkat-ensure-we-return-enoent-for-the-empty-pathname-for-normal-lookups.patch
* acerhdf-add-support-for-aspire-1410-bios-v13314.patch
* arch-x86-platform-iris-irisc-register-a-platform-device-and-a-platform-driver.patch
* x86-fix-mmap-random-address-range.patch
* leds-new-pcengines-alix-system-driver-enables-leds-via-gpio-interface.patch
* leds-new-pcengines-alix-system-driver-enables-leds-via-gpio-interface-fix.patch
* arch-x86-kernel-e820c-eliminate-bubble-sort-from-sanitize_e820_map.patch
* tracex86-add-tracepoint-to-x86-timer-interrupt-handler.patch
* tracex86-add-x86-irq-vector-entry-exit-tracepoints.patch
* arch-arm-mach-ux500-mbox-db5500c-world-writable-sysfs-fifo-file.patch
* arm-exec-remove-redundant-set_fsuser_ds.patch
* audit-always-follow-va_copy-with-va_end.patch
* btrfs-dont-dereference-extent_mapping-if-null.patch
* fsl-rio-correct-iecsr-register-clear-value.patch
* drm-vmwgfx-use-ida_simple_get-for-id-allocation.patch
* drivers-gpu-vga-vgaarbc-add-missing-kfree.patch
* fb-fix-potential-deadlock-between-lock_fb_info-and-console_lock.patch
cyber2000fb-avoid-palette-corruption-at-higher-clocks.patch
* hwmon-convert-idr-to-ida-and-use-ida_simple-interface.patch
* drivers-hwmon-hwmonc-convert-idr-to-ida-and-use-ida_simple_get.patch
* cputime-clean-up-cputime_to_usecs-and-usecs_to_cputime-macros.patch
* tick-fix-update_ts_time_stat-idle-accounting.patch
* nohz-do-not-update-idle-iowait-counters-from-get_cpu_idleiowait_time_us-if-not-asked.patch
* proc-consider-no_hz-when-printing-idle-and-iowait-times.patch
* ia64-exec-remove-redundant-set_fsuser_ds.patch
* unicore32-exec-remove-redundant-set_fsuser_ds.patch
btusb-patch-add_apple_macbookpro62.patch
* debugobjects-extend-debugobjects-to-assert-that-an-object-is-initialized.patch
* kernel-timerc-use-debugobjects-to-catch-deletion-of-uninitialized-timers.patch
* ext4-use-proper-little-endian-bitops.patch
* ocfs2-avoid-unaligned-access-to-dqc_bitmap.patch
* parisc-exec-remove-redundant-set_fsuser_ds.patch
* pci-dmar-update-dmar-units-devices-list-during-hotplug.patch
* drivers-firmware-dmi_scanc-make-dmi_name_in_vendors-more-focused.patch
* kernel-rtmutexc-fix-warning-improve-coding-style.patch
* scsi-fix-a-header-to-include-linux-typesh.patch
* drivers-scsi-megaraidc-fix-sparse-warnings.patch
* drivers-scsi-aacraid-commctrlc-fix-mem-leak-in-aac_send_raw_srb.patch
* drivers-scsi-sdc-use-ida_simple_get-and-ida_simple_remove-in-place-of-boilerplate-code.patch
* drivers-scsi-osd-osd_uldc-use-ida_simple_get-to-handle-id.patch
* drivers-scsi-sgc-convert-to-kstrtoul_from_user.patch
* drivers-block-brdc-make-brd_make_request-return-error-code.patch
drivers-block-loopc-emit-uevent-on-auto-release.patch
* sparc-exec-remove-redundant-addr_limit-assignment.patch
* drivers-staging-rts5139-rts51x_scsic-needs-vmalloch.patch
* drivers-staging-rts5139-xdc-needs-vmalloch.patch
* drivers-staging-rts5139-msc-needs-vmalloch.patch
* slab-add-taint-flag-outputting-to-debug-paths.patch
* slub-add-taint-flag-outputting-to-debug-paths.patch
mm.patch
* cross-memory-attach-v3.patch
* cross-memory-attach-update.patch
* cross-memory-attach-v4.patch
* mm-compaction-trivial-clean-up-in-acct_isolated.patch
* mm-change-isolate-mode-from-define-to-bitwise-type.patch
* mm-compaction-make-isolate_lru_page-filter-aware.patch
* mm-zone_reclaim-make-isolate_lru_page-filter-aware.patch
* mm-migration-clean-up-unmap_and_move.patch
* radix_tree-clean-away-saw_unset_tag-leftovers.patch
* vmscan-add-block-plug-for-page-reclaim.patch
* mm-page-writebackc-make-determine_dirtyable_memory-static-again.patch
* oom-avoid-killing-kthreads-if-they-assume-the-oom-killed-threads-mm.patch
* tmpfs-add-tmpfs-to-the-kconfig-prompt-to-make-it-obvious.patch
* mm-output-a-list-of-loaded-modules-when-we-hit-bad_page.patch
* mm-vmscan-fix-force-scanning-small-targets-without-swap.patch
* mm-vmscan-fix-force-scanning-small-targets-without-swap-fix.patch
* mm-vmscan-drop-nr_force_scan-from-get_scan_count.patch
* mm-distinguish-between-mlocked-and-pinned-pages.patch
* mm-add-comments-to-explain-mm_struct-fields.patch
* mm-add-comments-to-explain-mm_struct-fields-fix.patch
* mm-vmscan-do-not-writeback-filesystem-pages-in-direct-reclaim.patch
* mm-vmscan-remove-dead-code-related-to-lumpy-reclaim-waiting-on-pages-under-writeback.patch
* xfs-warn-if-direct-reclaim-tries-to-writeback-pages.patch
* ext4-warn-if-direct-reclaim-tries-to-writeback-pages.patch
* mm-vmscan-do-not-writeback-filesystem-pages-in-kswapd-except-in-high-priority.patch
* mm-vmscan-throttle-reclaim-if-encountering-too-many-dirty-pages-under-writeback.patch
* mm-vmscan-immediately-reclaim-end-of-lru-dirty-pages-when-writeback-completes.patch
* vmscan-count-pages-into-balanced-for-zone-with-good-watermark.patch
* mm-debug-pageallocc-use-plain-__ratelimit-instead-of-printk_ratelimit.patch
* lib-stringc-introduce-memchr_inv.patch
* mm-debug-pageallocc-use-memchr_inv.patch
* vmscan-fix-initial-shrinker-size-handling.patch
* vmscan-use-atomic-long-for-shrinker-batching.patch
* vmscan-use-atomic-long-for-shrinker-batching-fix.patch
* mm-avoid-null-pointer-access-in-vm_struct-via-proc-vmallocinfo.patch
* vmscan-promote-shared-file-mapped-pages.patch
* vmscan-activate-executable-pages-after-first-usage.patch
* memblock-add-memblock_start_of_dram.patch
* memblock-add-no_bootmem-config-symbol.patch
* mremap-check-for-overflow-using-deltas.patch
* mremap-avoid-sending-one-ipi-per-page.patch
* thp-mremap-support-and-tlb-optimization.patch
* thp-mremap-support-and-tlb-optimization-fix.patch
* thp-mremap-support-and-tlb-optimization-fix-fix.patch
* thp-mremap-support-and-tlb-optimization-fix-fix-fix.patch
* drivers-base-inodec-let-vmstat_text-be-optional.patch
* drivers-base-inodec-let-vmstat_text-be-optional-fix.patch
* selinuxfs-remove-custome-hex_to_bin.patch
* include-linux-securityh-fix-security_inode_init_security-arg.patch
frv-duplicate-output_buffer-of-e03.patch
frv-duplicate-output_buffer-of-e03-checkpatch-fixes.patch
* hpet-factor-timer-allocate-from-open.patch
* intel_idle-fix-api-misuse.patch
* intel_idle-disable-auto_demotion-for-hotplugged-cpus.patch
* kprobes-silence-debug_strict_user_copy_checks=y-warning.patch
* x86-implement-strict-user-copy-checks-for-x86_64.patch
* consolidate-config_debug_strict_user_copy_checks.patch
* consolidate-config_debug_strict_user_copy_checks-fix.patch
* lis3lv02d-avoid-divide-by-zero-due-to-unchecked.patch
* lis3-update-maintainer-information.patch
* lis3-add-support-for-hp-elitebook-2730p.patch
* lis3-add-support-for-hp-elitebook-8540w.patch
* hp_accel-add-hp-probook-655x.patch
* config_hp_accel-fix-help-text.patch
* lis3-free-regulators-if-probe-fails.patch
* lis3-change-naming-to-consistent.patch
* lis3-change-exported-function-to-use-given.patch
* lis3-remove-the-references-to-the-global-variable-in-core-driver.patch
* printk-add-module-parameter-ignore_loglevel-to-control-ignore_loglevel.patch
* printk-add-module-parameter-ignore_loglevel-to-control-ignore_loglevel-fix.patch
* printk-add-console_suspend-module-parameter.patch
* fs-nameic-remove-unused-getname_flags.patch
fcntlf_setfl-allow-setting-of-o_sync.patch
* leds-renesas-tpu-led-driver-v2.patch
* leds-renesas-tpu-led-driver-v2-fix.patch
* drivers-leds-led-triggersc-fix-memory-leak.patch
leds-route-kbd-leds-through-the-generic-leds-layer.patch
leds-route-kbd-leds-through-the-generic-leds-layer-fix.patch
* lib-kstrtox-common-code-between-kstrto-and-simple_strto-functions.patch
* lib-crc-add-slice-by-8-algorithm-to-crc32c.patch
* lib-crc-add-slice-by-8-algorithm-to-crc32c-fix.patch
* epoll-fix-spurious-lockdep-warnings.patch
lib-hexdumpc-make-hex2bin-return-the-updated-src-address.patch
fs-binfmt_miscc-use-kernels-hex_to_bin-method.patch
fs-binfmt_miscc-use-kernels-hex_to_bin-method-fix.patch
fs-binfmt_miscc-use-kernels-hex_to_bin-method-fix-fix.patch
* oprofilefs-handle-zero-length-writes.patch
* drivers-rtc-classc-convert-idr-to-ida-and-use-ida_simple_get.patch
* minix-describe-usage-of-different-magic-numbers.patch
* memcg-rename-mem-variable-to-memcg.patch
* memcg-fix-oom-schedule_timeout.patch
* memcg-use-vzalloc-instead-of-vmalloc.patch
* memcg-replace-ss-id_lock-with-a-rwlock.patch
* memcg-do-not-expose-uninitialized-mem_cgroup_per_node-to-world.patch
* memcg-remove-unneeded-preempt_disable.patch
* procfs-report-eisdir-when-reading-sysctl-dirs-in-proc.patch
* ipc-introduce-shm_rmid_forced-sysctl-testing.patch
* init-add-root=partuuid=uuid-partnroff=%d-support.patch
* init-add-root=partuuid=uuid-partnroff=%d-support-fix.patch
* drivers-rapidio-rio-scanc-use-discovered-bit-to-test-if-enumeration-is-complete.patch
* rapidio-add-mport-driver-for-tsi721-bridge.patch
* sysctl-make-config_sysctl_syscall-default-to-n.patch
* nbd-use-task_pid_nr-to-get-current-pid.patch
* nbd-replace-sysfs_create_file-with-device_create_file.patch
* nbd-replace-printk-kern_err-with-dev_err.patch
* nbd-lower-the-loglevel-of-an-error-message.patch
* nbd-replace-some-printk-with-dev_warn-and-dev_info.patch
* nbd-replace-some-printk-with-dev_warn-and-dev_info-checkpatch-fixes.patch
* pps-default-echo-function.patch
* pps-new-client-driver-using-gpio.patch
* pps-new-client-driver-using-gpio-fix.patch
scatterlist-new-helper-functions.patch
scatterlist-new-helper-functions-update.patch
scatterlist-new-helper-functions-update-fix.patch
memstick-add-support-for-legacy-memorysticks.patch
memstick-add-support-for-legacy-memorysticks-fix.patch
memstick-add-support-for-legacy-memorysticks-update-2.patch
* w1-ds2760-and-ds2780-use-ida-for-id-and-ida_simple_get-to-get-it.patch
* drivers-power-ds2780_batteryc-create-central-point-for-calling-w1-interface.patch
* drivers-power-ds2780_batteryc-add-a-nolock-function-to-w1-interface.patch
* drivers-power-ds2780_batteryc-fix-deadlock-upon-insertion-and-removal.patch
kexec-remove-kmsg_dump_kexec.patch
make-sure-nobodys-leaking-resources.patch
journal_add_journal_head-debug.patch
releasing-resources-with-children.patch
make-frame_pointer-default=y.patch
mutex-subsystem-synchro-test-module.patch
mutex-subsystem-synchro-test-module-fix.patch
slab-leaks3-default-y.patch
put_bh-debug.patch
add-debugging-aid-for-memory-initialisation-problems.patch
workaround-for-a-pci-restoring-bug.patch
prio_tree-debugging-patch.patch
single_open-seq_release-leak-diagnostics.patch
add-a-refcount-check-in-dput.patch
memblock-add-input-size-checking-to-memblock_find_region.patch
memblock-add-input-size-checking-to-memblock_find_region-fix.patch
^ permalink raw reply
* Re: linux-next: build failure after merge of the final tree (staging tree related)
From: Greg KH @ 2011-08-24 21:16 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel, edwin_rong
In-Reply-To: <20110824154741.3cbe03b403b646e2a99d63a2@canb.auug.org.au>
On Wed, Aug 24, 2011 at 03:47:41PM +1000, Stephen Rothwell wrote:
> Hi ,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/staging/rts5139/rts51x_scsi.c: In function 'inquiry':
> drivers/staging/rts5139/rts51x_scsi.c:498:2: error: implicit declaration of function 'vmalloc'
> drivers/staging/rts5139/xd.c: In function 'xd_init_l2p_tbl':
> drivers/staging/rts5139/xd.c:745:2: error: implicit declaration of function 'vmalloc'
> drivers/staging/rts5139/xd.c: In function 'free_zone':
> drivers/staging/rts5139/xd.c:771:3: error: implicit declaration of function 'vfree'
> drivers/staging/rts5139/ms.c: In function 'ms_init_l2p_tbl':
> drivers/staging/rts5139/ms.c:2214:2: error: implicit declaration of function 'vmalloc'
> drivers/staging/rts5139/ms.c:2257:3: error: implicit declaration of function 'vfree'
>
> Caused by commit 1dac4186bcc6 ("Staging: add driver for Realtek RTS5139
> cardreader").
>
> I have reverted that commit for today.
To fix it, all we have to do is include linux/vmalloc.h, right? Or is
ppc "special" in some other way regarding this call?
thanks,
greg k-h
^ permalink raw reply
* Re: linux-next: Tree for Aug 24 (dynamic_debug)
From: Greg KH @ 2011-08-24 21:09 UTC (permalink / raw)
To: Randy Dunlap
Cc: Jason Baron, Stephen Rothwell, Bart Van Assche, linux-next, LKML
In-Reply-To: <20110824124248.13aa3ed4.rdunlap@xenotime.net>
On Wed, Aug 24, 2011 at 12:42:48PM -0700, Randy Dunlap wrote:
> On Wed, 24 Aug 2011 15:32:45 -0400 Jason Baron wrote:
>
> > On Wed, Aug 24, 2011 at 10:25:51AM -0700, Randy Dunlap wrote:
> > > On Wed, 24 Aug 2011 16:04:04 +1000 Stephen Rothwell wrote:
> > >
> > > > Hi all,
> > >
> > > When CONFIG_NET is not enabled (I see this on i386 builds):
> > >
> > > lib/built-in.o: In function `__dynamic_netdev_dbg':
> > > (.text+0x9fda): undefined reference to `__netdev_printk'
> > >
> > > ---
> > > ~Randy
> > > *** Remember to use Documentation/SubmitChecklist when testing your code ***
> >
> > Ok, we probably want something, like below, although something keeps
> > selecting CONFIG_NET, when I try to unset it, in my .config...so not yet
> > tested, but should work.
>
> Yes, that works. Thanks.
>
> Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Nice.
Jason, care to resend this, with a proper signed-off-by, so that I can
apply it to fix this build error?
thanks
greg k-h
^ permalink raw reply
* Re: mmotm 2011-08-24-14-08 uploaded
From: Randy Dunlap @ 2011-08-24 22:04 UTC (permalink / raw)
To: akpm; +Cc: linux-kernel, linux-mm, linux-fsdevel, linux-next
In-Reply-To: <201108242148.p7OLm1lt009191@imap1.linux-foundation.org>
On Wed, 24 Aug 2011 14:09:05 -0700 akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2011-08-24-14-08 has been uploaded to
>
> http://userweb.kernel.org/~akpm/mmotm/
>
> It contains the following patches against 3.1-rc3:
> (patches marked "*" will be included in linux-next)
Hi Andrew,
Am I supposed to apply this to linux-next?
I don't get a clean patch(1) against 3.1-rc3.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
^ permalink raw reply
* Re: mmotm 2011-08-24-14-08 uploaded
From: Randy Dunlap @ 2011-08-24 22:08 UTC (permalink / raw)
To: Randy Dunlap; +Cc: akpm, linux-kernel, linux-mm, linux-fsdevel, linux-next
In-Reply-To: <20110824150433.70e140a6.rdunlap@xenotime.net>
On Wed, 24 Aug 2011 15:04:33 -0700 Randy Dunlap wrote:
> On Wed, 24 Aug 2011 14:09:05 -0700 akpm@linux-foundation.org wrote:
>
> > The mm-of-the-moment snapshot 2011-08-24-14-08 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
> >
> > It contains the following patches against 3.1-rc3:
> > (patches marked "*" will be included in linux-next)
>
> Hi Andrew,
>
> Am I supposed to apply this to linux-next?
> I don't get a clean patch(1) against 3.1-rc3.
My bad. Sorry for the noise.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
^ permalink raw reply
* Re: mmotm 2011-08-24-14-08 uploaded
From: Andrew Morton @ 2011-08-24 22:11 UTC (permalink / raw)
To: Randy Dunlap; +Cc: linux-kernel, linux-mm, linux-fsdevel, linux-next
In-Reply-To: <20110824150433.70e140a6.rdunlap@xenotime.net>
On Wed, 24 Aug 2011 15:04:33 -0700
Randy Dunlap <rdunlap@xenotime.net> wrote:
> On Wed, 24 Aug 2011 14:09:05 -0700 akpm@linux-foundation.org wrote:
>
> > The mm-of-the-moment snapshot 2011-08-24-14-08 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
> >
> > It contains the following patches against 3.1-rc3:
> > (patches marked "*" will be included in linux-next)
>
> Hi Andrew,
>
> Am I supposed to apply this to linux-next?
Nope. The full series is based on 3.1-rc3. It includes origin.patch
which takes it up to current -linus. And linux-next.patch which takes
it up to today's linux-next.
> I don't get a clean patch(1) against 3.1-rc3.
hm. What broke?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply
* Re: linux-next: build failure after merge of the final tree (staging tree related)
From: Stephen Rothwell @ 2011-08-24 22:54 UTC (permalink / raw)
To: Greg KH; +Cc: linux-next, linux-kernel, edwin_rong
In-Reply-To: <20110824211646.GB9707@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Hi Greg,
On Wed, 24 Aug 2011 14:16:46 -0700 Greg KH <greg@kroah.com> wrote:
>
> To fix it, all we have to do is include linux/vmalloc.h, right? Or is
I would assume so.
> ppc "special" in some other way regarding this call?
I assume it happens just because vmalloc.h is implicitly included by some
other header file on x86 and not on ppc.
This is why we have "Rule 1" in Documentation/SubmitChecklist. Relying
on the implicit inclusion of header files is bound to trip us up on some
architecture or platform or combination of CONFIG options.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply
* Re: linux-next: build failure after merge of the final tree (staging tree related)
From: Greg KH @ 2011-08-24 22:57 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel, edwin_rong
In-Reply-To: <20110825085420.521cc24fddadc7753dc67199@canb.auug.org.au>
On Thu, Aug 25, 2011 at 08:54:20AM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> On Wed, 24 Aug 2011 14:16:46 -0700 Greg KH <greg@kroah.com> wrote:
> >
> > To fix it, all we have to do is include linux/vmalloc.h, right? Or is
>
> I would assume so.
>
> > ppc "special" in some other way regarding this call?
>
> I assume it happens just because vmalloc.h is implicitly included by some
> other header file on x86 and not on ppc.
>
> This is why we have "Rule 1" in Documentation/SubmitChecklist. Relying
> on the implicit inclusion of header files is bound to trip us up on some
> architecture or platform or combination of CONFIG options.
Fair enough, I've made this fix in my tree, so it should be good now.
thanks,
greg k-h
^ permalink raw reply
* Re: linux-next: build warning after merge of the mips tree
From: Stephen Rothwell @ 2011-08-24 23:18 UTC (permalink / raw)
To: Ralf Baechle; +Cc: linux-next, linux-kernel
In-Reply-To: <20110822104809.451b0e8d7b231d70d73aa256@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
Hi Ralf,
On Mon, 22 Aug 2011 10:48:09 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Sun, 21 Aug 2011 09:43:02 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > The mips tree today seems like a complete mess. It seem to be some
> > historical tree including commits with commit dates going back to 1994
> > and v1.1.68! Please fix it up as it is unusable in its current form.
>
> Since it hasn't been fixed yet, I have reset the mips tree to be what it
> was in next-20110819.
Still not fixed :-(
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox