Commit-ID: 5aed9d24934be5b7fec1b66cc2a5f29fab4ec11e
Gitweb: http://git.kernel.org/tip/5aed9d24934be5b7fec1b66cc2a5f29fab4ec11e
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:35 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
-invalidatepage() aop now accepts range to invalidate so we can make
use of it in reiserfs_invalidatepage()
Signed-off-by: Lukas Czerner lczer...@redhat.com
---
fs/reiserfs/inode.c |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/reiserfs/inode.c
This commit changes truncate_inode_pages_range() so it can handle non
page aligned regions of the truncate. Currently we can hit BUG_ON when
the end of the range is not page aligned, but we can handle unaligned
start of the range.
Being able to handle non page aligned regions of the page can help
-Original Message-
From: Alex Williamson [mailto:alex.william...@redhat.com]
Sent: Tuesday, January 29, 2013 5:25 AM
To: Pandarathil, Vijaymohan R
Cc: Gleb Natapov; Bjorn Helgaas; Blue Swirl; Ortiz, Lance E;
k...@vger.kernel.org; qemu-de...@nongnu.org; linux-...@vger.kernel.org;
The head removal branch in the condition is never used in any code
path in ext4 since the function only caller ext4_ext_rm_leaf() will make
sure that the extent is properly split before removing blocks. Note that
there is a bug in this branch anyway.
This commit removes the unused code completely
We're doing to get rid of ext4_discard_partial_page_buffers() since it is
duplicating some code and also partially duplicating work of
truncate_pagecache_range(), moreover the old implementation was much
clearer.
Now when the truncate_inode_pages_range() can handle truncating non page
aligned
Commit-ID: 843985e953ddcc3d57a62641b377c8d3222859e2
Gitweb: http://git.kernel.org/tip/843985e953ddcc3d57a62641b377c8d3222859e2
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:36 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie oliv...@sobrie.be
commit 6ea45886865c1abb01bb861f7f6bdd5d0f398cb3 upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie oliv...@sobrie.be
commit 71088c4bd9b8f8cbffb0e66f2abc14297e4b2ca8 upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Cong Ding ding...@gmail.com
commit 10b8c7dff5d3633b69e77f57d404dab54ead3787 upstream.
When it goes to error through line 144, the memory allocated to *devname is
not freed, and the caller
Commit-ID: 5b9e2146ec4f8c6d436f9f7043a0409a4296a705
Gitweb: http://git.kernel.org/tip/5b9e2146ec4f8c6d436f9f7043a0409a4296a705
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:37 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Szymon Janc szymon.j...@tieto.com
commit dbccd791a3fbbdac12c33834b73beff3984988e9 upstream.
After sending reset command wait for its command complete event before
sending next command. Some
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau n...@openwrt.org
commit 1adb2e2b5f85023d17eb4f95386a57029df27c88 upstream.
When the next beacon is sent, the ath_buf from the previous run is reused.
If getting a new beacon from
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Clemens Ladisch clem...@ladisch.de
commit d56268fb108c7c21e19933588ca4d94652585183 upstream.
Commit 23caaf19b11e (ALSA: usb-mixer: Add support for Audio Class v2.0)
forgot to adjust the length
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter dan.carpen...@oracle.com
commit 8024c4c0b1057d1cd811fc9c3f88f81de9729fcd upstream.
We're testing for -show but calling -store().
Signed-off-by: Dan Carpenter
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Anderson Lizardo anderson.liza...@openbossa.org
commit 0a9ab9bdb3e891762553f667066190c1d22ad62b upstream.
The length parameter should be sizeof(req-name) - 1 because there is no
guarantee that
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie oliv...@sobrie.be
commit ee50e135aeb048b90fab662e661c58b67341830b upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Cox a...@linux.intel.com
commit c903f0456bc69176912dee6dd25c6a66ee1aed00 upstream.
At the moment the MSR driver only relies upon file system
checks. This means that anything as root with
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nathan Zimmer nzim...@sgi.com
commit b8f2c21db390273c3eaf0e5308faeaeb1e233840 upstream.
Update efi_call_phys_prelog to install an identity mapping of all available
memory. This corrects a bug
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: H. Peter Anvin h...@linux.intel.com
commit e43b3cec711a61edf047adf6204d542f3a659ef8 upstream.
early_pci_allowed() and read_pci_config_16() are only available if
CONFIG_PCI is defined.
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Wang YanQing udkni...@gmail.com
commit f44310b98ddb7f0d06550d73ed67df5865e3eda5 upstream.
I get the following warning every day with v3.7, once or
twice a day:
[ 2235.186027] WARNING: at
This is the start of the stable review cycle for the 3.4.29 release.
There are 33 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Feb 3 10:47:08 UTC 2013.
Anything
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie oliv...@sobrie.be
commit 71088c4bd9b8f8cbffb0e66f2abc14297e4b2ca8 upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
Commit-ID: 897014603c4786ef33450e675e02a5e74dc63785
Gitweb: http://git.kernel.org/tip/897014603c4786ef33450e675e02a5e74dc63785
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:38 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie oliv...@sobrie.be
commit 6ea45886865c1abb01bb861f7f6bdd5d0f398cb3 upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
On Thu, Jan 31, 2013 at 06:37:47PM -0600, Kim Phillips wrote:
+#if GCC_VERSION = 40600
+#define __HAVE_BUILTIN_BSWAP32__
+#define __HAVE_BUILTIN_BSWAP64__
You really aren't listening to anything that's been said to you.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King rmk+ker...@arm.linux.org.uk
commit 15653371c67c3fbe359ae37b720639dd4c7b42c5 upstream.
Subhash Jadavani reported this partial backtrace:
Now consider this call stack from MMC
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
commit 36224d0fe0f34cdde66a381708853ebadeac799c upstream.
Make BGA as the default version as we are supposed to just have
to specify when
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Szymon Janc szymon.j...@tieto.com
commit dbccd791a3fbbdac12c33834b73beff3984988e9 upstream.
After sending reset command wait for its command complete event before
sending next command. Some
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jerome Glisse jgli...@redhat.com
commit e521a29014794d139cca46396d1af8faf1295a26 upstream.
Aruba and newer gpu does not need the avivo cursor work around,
quite the opposite this work around
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: xueminsu xuemin...@intel.com
commit b2f4b03f8a378cd626d2ea67d19e7470c050a098 upstream.
drm_mode_addfb() expects fb_create return error code
instead of NULL.
Signed-off-by: xueminsu
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Suravee Suthikulpanit suravee.suthikulpa...@amd.com
commit 318fe782539c4150d1b8e4e6c9dc3a896512cb8a upstream.
The IOMMU may stop processing page translations due to a perceived lack
of credits
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie oliv...@sobrie.be
commit ee50e135aeb048b90fab662e661c58b67341830b upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka sgrus...@redhat.com
commit fa4cffcba9e13798ed7c6b8526b91b1631ecb53e upstream.
We do not correctly change interface type when switching from
IBSS mode to STA mode, that results
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg johannes.b...@intel.com
commit 1626e0fa740dec8665a973cf2349405cdfeb46dc upstream.
During FT roaming, wpa_supplicant attempts to set the
key before association. This used to be
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sujith Manoharan c_man...@qca.qualcomm.com
commit 0981c3b24ef664f5611008a6e6d0622fac6d892b upstream.
SKBs that are allocated in the HTC layer do not have callbacks
registered and hence ended up
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau n...@openwrt.org
commit a3dc48e82bb146ef11cf75676c8410c1df29b0c4 upstream.
On AR9300 the rx FIFO needs to be empty during reset to ensure that no
further DMA activity is
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau n...@openwrt.org
commit 1adb2e2b5f85023d17eb4f95386a57029df27c88 upstream.
When the next beacon is sent, the ath_buf from the previous run is reused.
If getting a new beacon from
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara j...@suse.cz
commit 4b05d09c18d9aa62d2e7fb4b057f54e5a38963f5 upstream.
Running AIO is pinning inode in memory using file reference. Once AIO
is completed using aio_complete(), file
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter dan.carpen...@oracle.com
commit 8024c4c0b1057d1cd811fc9c3f88f81de9729fcd upstream.
We're testing for -show but calling -store().
Signed-off-by: Dan Carpenter
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Rattray cratt...@opensource.wolfsonmicro.com
commit a80cc734282805e15b5e023751a4d02f7ffbcc91 upstream.
Signed-off-by: Chris Rattray cratt...@opensource.wolfsonmicro.com
Signed-off-by:
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Anderson Lizardo anderson.liza...@openbossa.org
commit 0a9ab9bdb3e891762553f667066190c1d22ad62b upstream.
The length parameter should be sizeof(req-name) - 1 because there is no
guarantee that
On Fri, 1 Feb 2013, Linus Torvalds wrote:
On Fri, Feb 1, 2013 at 9:44 AM, Thomas Gleixner t...@linutronix.de wrote:
Just face it. The current hotplug maze has 100+ states which are
completely undocumented. They are asymetric vs. startup and
teardown. They just exists and work somehow
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust trond.mykleb...@netapp.com
commit ab225417825963b6dc66be7ea80f94ac1378dfdf upstream.
Ensure that any setattr and getattr requests for junctions and/or
mountpoints are sent to
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Cox a...@linux.intel.com
commit c903f0456bc69176912dee6dd25c6a66ee1aed00 upstream.
At the moment the MSR driver only relies upon file system
checks. This means that anything as root with
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai ti...@suse.de
commit 0712eea349d8e2b6d0e44b94a752d999319027fb upstream.
A Packard-Bell desktop machine gives no proper pin configuration from
BIOS. It's almost equivalent with the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: H. Peter Anvin h...@linux.intel.com
commit e43b3cec711a61edf047adf6204d542f3a659ef8 upstream.
early_pci_allowed() and read_pci_config_16() are only available if
CONFIG_PCI is defined.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Fleming matt.flem...@intel.com
commit 712ba9e9afc4b3d3d6fa81565ca36fe518915c01 upstream.
efi.runtime_version is erroneously being set to the value of the
vendor's firmware revision instead
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nathan Zimmer nzim...@sgi.com
commit b8f2c21db390273c3eaf0e5308faeaeb1e233840 upstream.
Update efi_call_phys_prelog to install an identity mapping of all available
memory. This corrects a bug
On Thu, Jan 31, 2013 at 12:22:52PM +0100, Ingo Molnar wrote:
* Yuanhan Liu yuanhan@linux.intel.com wrote:
or whether the lock hold times could be reduced drastically
I also found one, but it doesn't sound like the one will
reduce lock hold times drastically:
31.01.2013 18:46, Don Zickus пишет:
I also attached another patch as suggested by Andrew to add a
touch_softlockup_watchdog in the unlzma routine. Probably makes things
run a little slower. Compiled tested only.
In my case (3.2.32) it cannot compile:
LD
Commit-ID: 34b9564373a9e1d8c33d07824fae228a381d1803
Gitweb: http://git.kernel.org/tip/34b9564373a9e1d8c33d07824fae228a381d1803
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:42 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Bellinger n...@linux-iscsi.org
This is to fix a regression that only affect the stable (not for the mainline)
that the stable commit fdf9d86 was incorrectly placed dev-dev_link_magic
Commit-ID: fc24d7c25c9d880ae012548d522fe13caee556ed
Gitweb: http://git.kernel.org/tip/fc24d7c25c9d880ae012548d522fe13caee556ed
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:43 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Wang YanQing udkni...@gmail.com
commit f44310b98ddb7f0d06550d73ed67df5865e3eda5 upstream.
I get the following warning every day with v3.7, once or
twice a day:
[ 2235.186027] WARNING: at
Commit-ID: cb16008bcc6ea53617ca06c9eb4ab0ecafe04585
Gitweb: http://git.kernel.org/tip/cb16008bcc6ea53617ca06c9eb4ab0ecafe04585
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:40 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka sgrus...@redhat.com
commit aacde9ee45225f7e0b90960f479aef83c66bfdc0 upstream.
Since:
commit b23b025fe246f3acc2988eb6d400df34c27cb8ae
Author: Ben Greear
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Piotr Haber pha...@broadcom.com
commit a1fe52801a992e590cdaee2fb47a94bac9b5da90 upstream.
On hardware reintialization reference count of
already existing timers would be increased again.
This
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Clemens Ladisch clem...@ladisch.de
commit d56268fb108c7c21e19933588ca4d94652585183 upstream.
Commit 23caaf19b11e (ALSA: usb-mixer: Add support for Audio Class v2.0)
forgot to adjust the length
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Vetter daniel.vet...@ffwll.ch
commit 9452618e7462181ed9755236803b6719298a13ce upstream.
DMAR support on g4x/gm45 integrated gpus seems to be totally busted.
So don't bother, but instead
Commit-ID: 717e263fc354d53d0961e952b779d14a42c8ea66
Gitweb: http://git.kernel.org/tip/717e263fc354d53d0961e952b779d14a42c8ea66
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:44 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
Commit-ID: 371d8c402e8c3562e913c7fda95094f42fbcf0ef
Gitweb: http://git.kernel.org/tip/371d8c402e8c3562e913c7fda95094f42fbcf0ef
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:39 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
Commit-ID: 01d14f1615dfe1c6d040541501445967ac716009
Gitweb: http://git.kernel.org/tip/01d14f1615dfe1c6d040541501445967ac716009
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:45 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
Commit-ID: 00c7e1f10c6b8ae8a031f5c6a58ecd15d20c52cb
Gitweb: http://git.kernel.org/tip/00c7e1f10c6b8ae8a031f5c6a58ecd15d20c52cb
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:46 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Avinash Patil pat...@marvell.com
commit 83f0c6d1f502bd75bb4a9e31e8d64e59c6894ad1 upstream.
Add missing ! as we are supposed to check !card-adapter
in PCIe suspend handler.
Signed-off-by:
We(Linux Kernel Performance project) found a regression introduced by
commit 5a50508, which just convert all mutex lock to rwsem write lock.
The semantics is same, but the results is quite huge in some cases.
After investigation, we found the root cause: mutex support lock
stealing. Here is the
Commit-ID: e6ab07d027d47e55d8a5c0f33b16dfdd3e18c96f
Gitweb: http://git.kernel.org/tip/e6ab07d027d47e55d8a5c0f33b16dfdd3e18c96f
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:47 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stephen Boyd sb...@codeaurora.org
commit 568dca15aa2a0f4ddee255894ec393a159f13147 upstream.
Patrik Kluba reports that the preempt count becomes invalid due
to the preempt_enable() call being
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Cong Ding ding...@gmail.com
commit 10b8c7dff5d3633b69e77f57d404dab54ead3787 upstream.
When it goes to error through line 144, the memory allocated to *devname is
not freed, and the caller
Commit-ID: bbdc7aa442630a84feae45f4ca2dd7ed01abc868
Gitweb: http://git.kernel.org/tip/bbdc7aa442630a84feae45f4ca2dd7ed01abc868
Author: Sukadev Bhattiprolu suka...@linux.vnet.ibm.com
AuthorDate: Tue, 22 Jan 2013 22:23:53 -0800
Committer: Arnaldo Carvalho de Melo a...@redhat.com
Commit-ID: 2663960c159f23cbfb8e196c96e9fc9f3b5f1a8d
Gitweb: http://git.kernel.org/tip/2663960c159f23cbfb8e196c96e9fc9f3b5f1a8d
Author: Sukadev Bhattiprolu suka...@linux.vnet.ibm.com
AuthorDate: Tue, 22 Jan 2013 22:24:23 -0800
Committer: Arnaldo Carvalho de Melo a...@redhat.com
-invalidatepage() aop now accepts range to invalidate so we can make
use of it in gfs2_invalidatepage().
Signed-off-by: Lukas Czerner lczer...@redhat.com
---
fs/gfs2/aops.c |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/gfs2/aops.c b/fs/gfs2/aops.c
index
-invalidatepage() aop now accepts range to invalidate so we can make
use of it in ceph_invalidatepage().
Signed-off-by: Lukas Czerner lczer...@redhat.com
---
fs/ceph/addr.c | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/fs/ceph/addr.c b/fs/ceph/addr.c
index
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King rmk+ker...@arm.linux.org.uk
commit 15653371c67c3fbe359ae37b720639dd4c7b42c5 upstream.
Subhash Jadavani reported this partial backtrace:
Now consider this call stack from MMC
On Fri, Feb 1, 2013 at 9:04 AM, Namhyung Kim namhy...@kernel.org wrote:
Hi Stephane,
On Fri, 1 Feb 2013 00:51:51 +0100, Stephane Eranian wrote:
Hi,
Looks like perf annotate in pipe mode is totally broken nowadays.
I tried this from tip.git:
$ perf record -o - noploop 5 perf.data
$ perf
Commit-ID: 1c53a270724df91276d28d66f8e5a302fc6a5d74
Gitweb: http://git.kernel.org/tip/1c53a270724df91276d28d66f8e5a302fc6a5d74
Author: Sukadev Bhattiprolu suka...@linux.vnet.ibm.com
AuthorDate: Tue, 22 Jan 2013 22:24:54 -0800
Committer: Arnaldo Carvalho de Melo a...@redhat.com
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Sujith Manoharan c_man...@qca.qualcomm.com
commit 0981c3b24ef664f5611008a6e6d0622fac6d892b upstream.
SKBs that are allocated in the HTC layer do not have callbacks
registered and hence ended up
Commit-ID: 886c3b2d677fe248cce8101fa66a1b3e05c3ba16
Gitweb: http://git.kernel.org/tip/886c3b2d677fe248cce8101fa66a1b3e05c3ba16
Author: Sukadev Bhattiprolu suka...@linux.vnet.ibm.com
AuthorDate: Tue, 22 Jan 2013 22:25:29 -0800
Committer: Arnaldo Carvalho de Melo a...@redhat.com
This reverts commit 189e868fa8fdca702eb9db9d8afc46b5cb9144c9.
This commit reintroduces the use of ext4_block_truncate_page() in ext4
truncate operation instead of ext4_discard_partial_page_buffers().
The statement in the commit description that the truncate operation only
zero block unaligned
This reverts commit ccb4d7af914e0fe9b2f1022f8ea6c300463fd5e6.
This commit reintroduces functions ext4_block_truncate_page() and
ext4_block_zero_page_range() which has been previously removed in favour
of ext4_discard_partial_page_buffers().
In future commits we want to reintroduce those function
Commit-ID: 2ac3634a7e1c8eedc961030c87c5c36ebd5bbf8e
Gitweb: http://git.kernel.org/tip/2ac3634a7e1c8eedc961030c87c5c36ebd5bbf8e
Author: Sukadev Bhattiprolu suka...@linux.vnet.ibm.com
AuthorDate: Tue, 22 Jan 2013 22:26:45 -0800
Committer: Arnaldo Carvalho de Melo a...@redhat.com
Commit-ID: 4fb71074a570aab9ba8a30b7a756a3c637a14c03
Gitweb: http://git.kernel.org/tip/4fb71074a570aab9ba8a30b7a756a3c637a14c03
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:34 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
Currently there is no way to truncate partial page where the end
truncate point is not at the end of the page. This is because it was not
needed and the functionality was enough for file system truncate
operation to work properly. However more file systems now support punch
hole feature and it can
-invalidatepage() aop now accepts range to invalidate so we can make
use of it in ocfs2_invalidatepage().
Signed-off-by: Lukas Czerner lczer...@redhat.com
---
fs/ocfs2/aops.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/fs/ocfs2/aops.c b/fs/ocfs2/aops.c
index
-invalidatepage() aop now accepts range to invalidate so we can make
use of it in xfs_vm_invalidatepage()
Signed-off-by: Lukas Czerner lczer...@redhat.com
Cc: x...@oss.sgi.com
---
fs/xfs/xfs_aops.c |5 +++--
fs/xfs/xfs_trace.h | 41 -
2 files
-invalidatepage() aop now accepts range to invalidate so we can make
use of it in journal_invalidatepage() and all the users in ext3 file
system. Also update ext3 trace point to print out length argument.
Signed-off-by: Lukas Czerner lczer...@redhat.com
---
fs/ext3/inode.c |6
invalidatepage now accepts range to invalidate and there are two file
system using jbd2 also implementing punch hole feature which can benefit
from this. We need to implement the same thing for jbd2 layer in order to
allow those file system take benefit of this functionality.
This commit adds
On 02/01/2013 06:07 PM, Bryn M. Reeves wrote:
On 02/01/2013 09:59 AM, Tao Ma wrote:
yes, but the result is the same. It will do some IO first which will
cause this command hang.
You seem to have a problem with either the device/adapter or in the
driver. The backtrace you posted shows that
On Fri, Feb 1, 2013 at 4:33 PM, Yasuaki Ishimatsu
isimatu.yasu...@jp.fujitsu.com wrote:
At least, you should use release_partitions() instead of kfree() here.
Good catch, thank you for pointing it out, and I will post v1 later
with the update.
Thanks,
--
Ming Lei
--
To unsubscribe from this
Philip == Philip Avinash avinashphi...@ti.com writes:
Philip DT field of interrupts was mentioned wrongly as interrupt in SPI
Philip node. This went unnoticed as spi-omap2 driver not making use of
Philip interrupt. Fixes the typo.
Philip Signed-off-by: Philip Avinash avinashphi...@ti.com
On Fri, Feb 01, 2013 at 03:37:56PM +0530, Sachin Kamat wrote:
Use the newly introduced devm_ioremap_resource() instead of
devm_request_and_ioremap() which provides more consistent error handling.
devm_ioremap_resource() provides its own error messages; so all explicit
error messages can be
On Fri, Feb 01, 2013 at 03:37:57PM +0530, Sachin Kamat wrote:
Use the newly introduced devm_ioremap_resource() instead of
devm_request_and_ioremap() which provides more consistent error handling.
devm_ioremap_resource() provides its own error messages; so all explicit
error messages can be
After NFS (SUNRPC + NFSd actually) containerization work some basic
principles of SUNRPC service initialization and deinitialization has been
changed: now one service can be shared between different network namespaces
and network resources can be attached or detached from the running service.
This
Per-cpu semaphores are desired to be used by NFS kernel server.
As Bruce Fields suggested:
The server rpc code goes to some care not to write to any global
structure, to prevent server threads running on multiple cores from
bouncing cache lines between them.
But
There could be a service transport, which is processed by service thread and
racing in the same time with per-net service shutdown like listed below:
CPU#0:CPU#1:
svc_recvsvc_close_net
svc_get_next_xprt (list_del_init(xpt_ready))
Using the attached program I can trigger the following WARNING
reliably as a normal user. This happens at least both in 3.8-rc6
and 3.7.5.
The kernel is tainted by proprietary NVIDIA module, but I don't
thinks it matters in this case.
[ 4390.882323] [ cut here ]
[
Hi Sedat,
On Fri, 1 Feb 2013 09:12:10 +0100 Sedat Dilek sedat.di...@gmail.com wrote:
any reason why there is only next-20130128 the last and only release
for this week?
In the release note for next-20130128, I said:
The linux-next release may be a bit sporadic over the next few days as I
Hi Derek,
On 12/21/2012 12:35 PM, Derek Basehore wrote:
We no longer wait for the disk to spin up in sd_resume. It now enters the
request to spinup the disk into the elevator and returns.
A function is scheduled under the scsi_sd_probe_domain to wait for the command
to spinup the disk to
On Fri, Feb 01, 2013 at 08:01:41AM +0200, Luciano Coelho wrote:
On Thu, 2013-01-31 at 16:42 -0500, Matt Porter wrote:
On Thu, Jan 31, 2013 at 08:58:39PM +, Arnd Bergmann wrote:
On Thursday 31 January 2013, Matt Porter wrote:
On Wed, Jan 30, 2013 at 09:32:58AM +, Arnd Bergmann
metag_cache_probe() is only called from setup_arch(), so add the __init
attribute to it.
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/mm/cache.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/metag/mm/cache.c b/arch/metag/mm/cache.c
index
101 - 200 of 1300 matches
Mail list logo