On Fri, Jun 14, 2013 at 10:33:45AM -0600, Shuah Khan wrote:
Change __device_suspend() path to include driver name and the ops that
get run for a device. This additional information helps associate driver
and the type of pm_ops the device uses in suspend path very quickly and
aid in debugging
Hello,
Because I've become a request which made me slightly more optimistic about
the RFC patches, I've spend some more time on the patches doing cosmetic.
I know think the quickly done is gone and they might be ready for
submission.
The whole series consists more or less of 3 mini-series.
The
There is no real reason to not support 16 or 32 bit values too.
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
drivers/rtc/rtc-hid-sensor-time.c | 59 +--
1 file changed, 32 insertions(+), 27 deletions(-)
diff --git
The draft for HID-sensors (HUTRR39) currently doesn't define the range
for the attribute year. Asking one of the authors revealed that full years
(e.g. 2013 instead of just 13) were meant.
So we now allow both, 8 bit and 16 bit values for the attribute year and
assuming full years when the value
On 14.06.2013 20:08, Christoph Lameter wrote:
On Fri, 14 Jun 2013, Roman Gushchin wrote:
But there is an actual problem, that this patch solves.
Sometimes I saw the following issue on some machines:
all CPUs are performing compaction, system time is about 80%,
system is completely unreliable.
rtc_device_register() might want to read the clock which doesn't work
before the hid device is registered. Therefor we delay the registration of
the rtc driver by moving it to a work.
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
drivers/rtc/rtc-hid-sensor-time.c | 66
On Fri, Jun 14, 2013 at 08:57:44AM -0700, Dave Hansen wrote:
On 06/14/2013 07:09 AM, Zheng Liu wrote:
- INIT_LIST_HEAD(scanned);
-
spin_lock(sbi-s_es_lru_lock);
+ list_sort(NULL, sbi-s_es_lru, ext4_inode_touch_time_cmp);
list_for_each_safe(cur, tmp, sbi-s_es_lru) {
How
hctosys= specifies the driver (RTC) name which sets the system clock at
boot, if and only if userspace hasn't set the time before the driver will
be loaded.
If hctosys will not be specified, the first available hardware clock
with a valid time will be used (again, if and only if ...).
If you
In order to let an RTC set the time at boot without the problem that a
second RTC overwrites it, the flag systime_was_set is introduced.
systime_was_set will be true, if a persistent clock sets the time at boot,
or if do_settimeofday() is called (e.g. by the RTC subsystem or userspace).
Some RTCs offer a higher resolution than seconds. To support reading such
high resolution timestamps from inside the kernel implement
rtc_read_timeval() and add a read_timeval to the rtc-ops.
This is done to support high precision read-only clocks (like radio- or
GPS-clocks) from inside the
On 06/14/2013 10:45 AM, Greg KH wrote:
On Fri, Jun 14, 2013 at 10:33:45AM -0600, Shuah Khan wrote:
Change __device_suspend() path to include driver name and the ops that
get run for a device. This additional information helps associate driver
and the type of pm_ops the device uses in suspend
Those config options don't make sense anymore with the new hctosys
mechanism introduced with the previous patch.
That means two things:
- If a (hardware) clock is available it will be used to set the time at
boot. This was already the case for system which have a persistent
clock, e.g. most
On 06/14/2013 10:11 AM, Zheng Liu wrote:
On Fri, Jun 14, 2013 at 08:57:44AM -0700, Dave Hansen wrote:
On 06/14/2013 07:09 AM, Zheng Liu wrote:
- INIT_LIST_HEAD(scanned);
-
spin_lock(sbi-s_es_lru_lock);
+ list_sort(NULL, sbi-s_es_lru, ext4_inode_touch_time_cmp);
Some RTCs do provide a higher precision than seconds. Add support for them
by trying rtc_read_timeval() before using rtc_read_time() to get the time
in the hctosys mechanism.
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
drivers/rtc/class.c | 35 ---
1
Some HID clocks do provide milliseconds. Make it possible to read a high
precision timestamp by supporting rtc_read_timeval().
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
drivers/rtc/rtc-hid-sensor-time.c | 74 +++
include/linux/hid-sensor-ids.h
On Fri, Jun 14, 2013 at 9:33 AM, Bjorn Helgaas bhelg...@google.com wrote:
On Fri, Jun 14, 2013 at 10:17 AM, Yinghai Lu ying...@kernel.org wrote:
Can you please refer to specific function names? I can't read your mind.
You might be referring to quirk_disable_aspm_l0s(). This is a
On Fri, Jun 14, 2013 at 10:30 PM, Bjorn Helgaas bhelg...@google.com wrote:
[+cc Ming, Hayes, Francois, r8169 list]
On Fri, Jun 14, 2013 at 6:49 AM, nirinA raseliarison
nirina.raseliari...@gmail.com wrote:
hello there,
i have this ethernet controler:
Realtek Semiconductor Co., Ltd.
On 06/14, Steven Rostedt wrote:
On Fri, 2013-06-14 at 18:04 +0200, Oleg Nesterov wrote:
But the main problem is, synchronize_sched() is slow and it is called
under the global event_mutex.
But is that really an issue? event_mutex is used to add or remove
events, and this happens only
on Fri, 14 Jun 2013 18:45:48 +0300, Guenter Roeck li...@roeck-us.net
wrote:
On Fri, Jun 14, 2013 at 08:30:29AM -0600, Bjorn Helgaas wrote:
[+cc Ming, Hayes, Francois, r8169 list]
On Fri, Jun 14, 2013 at 6:49 AM, nirinA raseliarison
nirina.raseliari...@gmail.com wrote:
hello there,
i have
On Thu, Jun 13, 2013 at 4:29 PM, Rafael J. Wysocki r...@sisk.pl wrote:
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Make acpi_pci_set_power_state() print the name of the ACPI device
power state the device has been actually put into instead of printing
the name of the requested PCI
On Mon, Jun 10, 2013 at 05:12:08AM +0100, Rob Herring wrote:
On 06/04/2013 05:21 AM, Russell King - ARM Linux wrote:
On Mon, Jun 03, 2013 at 06:51:59PM -0700, Stephen Boyd wrote:
On 06/03/13 15:12, Russell King - ARM Linux wrote:
If you have a 56-bit clock which ticks at a period of 1ns,
Hello,
I've just tested some things with 3.10-rc5+ and discovered that
rtc_device_unregister is broken. This is most likely because of the
switch to devm*. As 3.10 is already at -rc5, I'm posting this without
having had a deeper look at the problem and writing a patch. Maybe
someone is
On 06/14/2013 09:40 AM, Javier Martinez Canillas wrote:
Use irq_get_trigger_type() to get the IRQ trigger type flags
instead calling irqd_get_trigger_type(irq_desc_get_irq_data(irq))
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Acked-by: David Daney
On 06/14/2013 09:52 AM, Alexander Holler wrote:
Some RTCs offer a higher resolution than seconds. To support reading such
high resolution timestamps from inside the kernel implement
rtc_read_timeval() and add a read_timeval to the rtc-ops.
So I like the direction this patch is going. But if
On Fri, Jun 14, 2013 at 12:33:27PM -0400, Steven Rostedt wrote:
On Fri, 2013-06-14 at 09:21 -0700, Paul E. McKenney wrote:
@@ -548,15 +556,35 @@ static void uprobe_trace_print(struct
trace_uprobe *tu,
/* uprobe handler */
static int uprobe_trace_func(struct trace_uprobe
On 06/14/2013 09:52 AM, Alexander Holler wrote:
Hello,
Because I've become a request which made me slightly more optimistic about
the RFC patches, I've spend some more time on the patches doing cosmetic.
I know think the quickly done is gone and they might be ready for
submission.
The whole
On 06/14/2013 09:52 AM, Alexander Holler wrote:
Some RTCs offer a higher resolution than seconds. To support reading such
high resolution timestamps from inside the kernel implement
rtc_read_timeval() and add a read_timeval to the rtc-ops.
This is done to support high precision read-only clocks
On Fri, 2013-06-14 at 14:47 +0800, Aaron Lu wrote:
What about a priority based solution? We can introduce a new field named
priority to backlight_device and instead of calling another module's
function like the unregister one here(which cause unnecessary module
dependency), we only need to
On 06/14/2013 09:52 AM, Alexander Holler wrote:
In order to let an RTC set the time at boot without the problem that a
second RTC overwrites it, the flag systime_was_set is introduced.
systime_was_set will be true, if a persistent clock sets the time at boot,
or if do_settimeofday() is called
Am 14.06.2013 19:23, schrieb John Stultz:
On 06/14/2013 09:52 AM, Alexander Holler wrote:
Some RTCs offer a higher resolution than seconds. To support reading such
high resolution timestamps from inside the kernel implement
rtc_read_timeval() and add a read_timeval to the rtc-ops.
So I like
On Friday 14 June 2013 09:41:36 Olof Johansson wrote:
I sort of presumed that there might be need for _some_ platform code
later on, just not quite yet, so I didn't want to be quite that
drastic. I suppose leaving it with the trivial file for now is OK, and
we can make a sweeping change down
On Fri, Jun 14, 2013 at 10:57 AM, Yinghai Lu ying...@kernel.org wrote:
On Fri, Jun 14, 2013 at 9:33 AM, Bjorn Helgaas bhelg...@google.com wrote:
On Fri, Jun 14, 2013 at 10:17 AM, Yinghai Lu ying...@kernel.org wrote:
Can you please refer to specific function names? I can't read your mind.
On Fri, Jun 14, 2013 at 02:04:00PM +0100, Pawel Moll wrote:
On Thu, 2013-06-13 at 23:52 +0100, Olof Johansson wrote:
+ reg = 0 0x7FFF 0 0x1000;
#size-cells 2 on the parent bus? That's somewhat unusual.
LPAE == 40 bit physical addresses == potential 32 bit sizes (memory
The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.git
tags/msm-cleanup-for-3.11
for you to fetch changes up to
The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.git
tags/msm-fix-for-3.11
for you to fetch changes up to
The following three pull requests are for the MSM tree for 3.11. In
addition to cleanups and fixes, there is starting to be some work
toward getting full clock support in the MSM tree.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.git
tags/msm-fix-for-3.11
for you to fetch changes up to
On Fri, Jun 14, 2013 at 03:30:37PM +0800, Wanpeng Li wrote:
After commit 839a8e86(writeback: replace custom worker pool implementation
with unbound workqueue), there is no bdi forker thread any more. This patch
rename WB_REASON_FORKER_THREAD to WB_REASON_WORKER_THREAD since works are
done by
On 06/14, Stephen Boyd wrote:
On 06/14, Rob Herring wrote:
On 06/12/2013 12:21 PM, Stephen Boyd wrote:
On 06/11, Rob Herring wrote:
Can you use vm_reserve_area_early here or perhaps just call
iotable_init instead of create_mapping directly? I don't recall if
there was some reason I
On Sat, Jun 15, 2013 at 01:00:28AM +0800, Zheng Liu wrote:
I have a suggestion for how to address this: Keep a timestamp of when
the list last has been sorted in struct ext4_super_info. When
iterating over the list, looking for a candidate inode, if inode's
i_touch_when is greater than
Tony promised me to test those patches on his box, so we'll know for sure
in a while.
Tested this series - and the box boots just fine with no unexpected messages.
But I should note that this box doesn't have anything that is hot pluggable, so
I
couldn't test hotplug (which seems to be deeply
Am 14.06.2013 19:41, schrieb John Stultz:
On 06/14/2013 09:52 AM, Alexander Holler wrote:
In order to let an RTC set the time at boot without the problem that a
second RTC overwrites it, the flag systime_was_set is introduced.
systime_was_set will be true, if a persistent clock sets the time
On Tue, Jun 11, 2013 at 01:08:14AM +0800, Jiang Liu wrote:
On Tue 11 Jun 2013 12:58:01 AM CST, Konrad Rzeszutek Wilk wrote:
On Mon, Jun 10, 2013 at 12:50:46AM +0800, Jiang Liu wrote:
On Sat 08 Jun 2013 01:07:06 AM CST, Konrad Rzeszutek Wilk wrote:
On Sat, Jun 08, 2013 at 12:50:31AM +0800,
Hi,
On Wed, Mar 6, 2013 at 7:37 AM, Matt Porter mpor...@ti.com wrote:
On Tue, Mar 05, 2013 at 09:26:01PM +, Arnd Bergmann wrote:
On Tuesday 05 March 2013, Matt Porter wrote:
Changes since v1:
- rebase to 3.9-rc1, previous dependencies upstream
This series adds DT DMA Engine
Hi Maxime,
El 09/06/13 13:36, Maxime Ripard escribió:
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts | 75
1 file changed, 75 insertions(+)
create mode 100644
Resending on Matt's new email, thanks.
On Fri, Jun 14, 2013 at 1:10 PM, Joel A Fernandes agnel.j...@gmail.com wrote:
Hi,
On Wed, Mar 6, 2013 at 7:37 AM, Matt Porter mpor...@ti.com wrote:
On Tue, Mar 05, 2013 at 09:26:01PM +, Arnd Bergmann wrote:
On Tuesday 05 March 2013, Matt Porter
From: David Daney david.da...@cavium.com
Thanks to commit f91eb62f71b (init: scream bloody murder if interrupts
are enabled too early), bloody murder is now being screamed.
With a MIPS OCTEON config, we use on_each_cpu() in our
irq_chip.irq_bus_sync_unlock() function. This gets called in early
On 06/14/2013 11:37 AM, Linus Torvalds wrote:
On Fri, Jun 14, 2013 at 8:00 AM, Waiman Longwaiman.l...@hp.com wrote:
On 06/12/2013 08:59 PM, Linus Torvalds wrote:
Ho humm.. interesting. I was talking about wanting to mix atomics and
spinlocks earlier in this thread due to space constraints,
HEST for corrected machine checks
Here's a patch that implements this technique. If the firmware advertises
support for firmware first mode in the CMC structure, we disable CMCI and
polling for all the MCA banks listed in the CMC structure.
- Naveen
Signed-off-by: Naveen N. Rao
On Fri, Jun 14, 2013 at 10:44 AM, Bjorn Helgaas bhelg...@google.com wrote:
On Fri, Jun 14, 2013 at 10:57 AM, Yinghai Lu ying...@kernel.org wrote:
On Fri, Jun 14, 2013 at 9:33 AM, Bjorn Helgaas bhelg...@google.com wrote:
On Fri, Jun 14, 2013 at 10:17 AM, Yinghai Lu ying...@kernel.org wrote:
On 06/14/2013 11:05 AM, Alexander Holler wrote:
Am 14.06.2013 19:41, schrieb John Stultz:
On 06/14/2013 09:52 AM, Alexander Holler wrote:
In order to let an RTC set the time at boot without the problem that a
second RTC overwrites it, the flag systime_was_set is introduced.
systime_was_set
on Fri, 14 Jun 2013 20:02:25 +0300, Ming Lei ming@canonical.com
wrote:
On Fri, Jun 14, 2013 at 10:30 PM, Bjorn Helgaas bhelg...@google.com
wrote:
[+cc Ming, Hayes, Francois, r8169 list]
On Fri, Jun 14, 2013 at 6:49 AM, nirinA raseliarison
nirina.raseliari...@gmail.com wrote:
hello
On Fri, Jun 14, 2013 at 06:40:47PM +0200, Javier Martinez Canillas wrote:
Use irq_get_trigger_type() to get the IRQ trigger type flags
instead calling irqd_get_trigger_type(irq_get_irq_data(irq))
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
On Fri, Jun 14, 2013 at 06:40:44PM +0200, Javier Martinez Canillas wrote:
Use irq_get_trigger_type() to get the IRQ trigger type flags
instead calling irqd_get_trigger_type(irq_get_irq_data(irq))
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
I am not sure I understand why this patch is needed. When a new card
is inserted/removed and the upper levels gets notification about the
new card, triggering the mounting/un-mounting of the file system, why
should it be the lowest layer (mmc) that prevents the platform from
enter
On Fri, Jun 07, 2013 at 06:55:57PM +0200, Michael Holzheu wrote:
[..]
@@ -935,10 +967,17 @@ static int __init vmcore_init(void)
{
int rc = 0;
- /* If elfcorehdr= has been passed in cmdline, then capture the dump.*/
- if (!(is_vmcore_usable()))
- return rc;
+
Signed-off-by: Andreas Gruenbacher agr...@linbit.com
Signed-off-by: Philipp Reisner philipp.reis...@linbit.com
---
drivers/block/drbd/drbd_int.h |7 ++-
drivers/block/drbd/drbd_nl.c | 20 ++--
drivers/block/drbd/drbd_receiver.c |6 +++---
3 files changed,
From 48bbf44a96676ce6f520a408378730c976e9a11e Mon Sep 17 00:00:00 2001
From: James Bottomley jbottom...@parallels.com
Date: Wed, 8 May 2013 14:05:34 -0700
Subject: [PATCH] [PARISC] fix WARNING: at kernel/cpu/idle.c:96
On PA-RISC (and presumably any other arch that doesn't implement its own
On Fri, Jun 07, 2013 at 06:55:56PM +0200, Michael Holzheu wrote:
[..]
In this patch series I did not include the discussed ELF header swap trick
patch because with the ELF header read functions this patch currently is
not necessary.
Michael,
Would be good to this change atleast in a separate
In case the connection was established and lost again before
the a fence-peer handler returns, ignore the exit code of this
instance. (And use the exit code of the later started instance)
Signed-off-by: Andreas Gruenbacher agr...@linbit.com
Signed-off-by: Philipp Reisner
From: Andreas Gruenbacher agr...@linbit.com
Signed-off-by: Andreas Gruenbacher agr...@linbit.com
Signed-off-by: Philipp Reisner philipp.reis...@linbit.com
---
drivers/block/drbd/drbd_nl.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Fix to return a negative error code from the error handling
case instead of 0, as returned elsewhere in this function.
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
Signed-off-by: Lars Ellenberg lars.ellenb...@linbit.com
Signed-off-by:
Allow to change the AL layout with an resize operation. For that
the reisze command gets two new fields: al_stripes and al_stripe_size.
In order to make the operation crash save:
1) Lock out all IO and MD-IO
2) Write the super block with MDF_PRIMARY_IND clear
3) write the bitmap to the new
The first 4 patches are obvious fixes. The last patch adds
the capability to change the activity log layout online.
(al-stripes and al-stripe-size)
Andreas Gruenbacher (2):
drbd: Do not sleep inside rcu
drbd: Fix rcu_read_lock balance on error path
Philipp Reisner (3):
drbd: Ignore the
From: Andreas Gruenbacher agr...@linbit.com
Signed-off-by: Andreas Gruenbacher agr...@linbit.com
Signed-off-by: Philipp Reisner philipp.reis...@linbit.com
---
drivers/block/drbd/drbd_receiver.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Fri, Jun 14, 2013 at 10:29:09AM +0300, Andy Shevchenko wrote:
On Tue, Jun 11, 2013 at 8:11 PM, Bin Gao bin@linux.intel.com wrote:
On Sun, Jun 09, 2013 at 10:53:35PM +0300, Andy Shevchenko wrote:
Please, try to avoid top posting in the future emails.
On Fri, Jun 7, 2013 at 12:26 AM,
On Fri, 2013-06-14 at 17:38 +0200, Manfred Spraul wrote:
Hi all,
On 06/10/2013 07:16 PM, Manfred Spraul wrote:
Hi Andrew,
I have cleaned up/improved my updates to sysv sem.
Could you replace my patches in -akpm with this series?
- 1: cacheline align output from ipc_rcu_alloc
-
On 06/14/2013 09:52 AM, Alexander Holler wrote:
Those config options don't make sense anymore with the new hctosys
mechanism introduced with the previous patch.
That means two things:
- If a (hardware) clock is available it will be used to set the time at
boot. This was already the case for
On 06/14/2013 11:55 AM, James Bottomley wrote:
From 48bbf44a96676ce6f520a408378730c976e9a11e Mon Sep 17 00:00:00 2001
From: James Bottomley jbottom...@parallels.com
Date: Wed, 8 May 2013 14:05:34 -0700
Subject: [PATCH] [PARISC] fix WARNING: at kernel/cpu/idle.c:96
On PA-RISC (and presumably
On Fri, 2013-06-14 at 12:11 -0700, David Daney wrote:
On 06/14/2013 11:55 AM, James Bottomley wrote:
From 48bbf44a96676ce6f520a408378730c976e9a11e Mon Sep 17 00:00:00 2001
From: James Bottomley jbottom...@parallels.com
Date: Wed, 8 May 2013 14:05:34 -0700
Subject: [PATCH] [PARISC] fix
Andrew,
These 2 patches are completely orthogonal, and either patch can
fix the problem reported by Andrey. However, I think they both
make sense.
The 2nd patch was already acked by Eric/Andrey. However it is
not as trivial as it looks.
The 1st one looks more straightforward, and perhaps it is
fput() assumes that it can't be called after exit_task_work() but
this is not true, for example free_ipc_ns()-shm_destroy() can do
this. In this case fput() silently leaks the file.
Change it to fallback to delayed_fput_work if task_work_add() fails.
The patch looks complicated but it is not, it
exit_notify() does exit_task_namespaces() after
forget_original_parent(). This was needed to ensure that -nsproxy
can't be cleared prematurely, an exiting child we are going to
reparent can do do_notify_parent() and use the parent's (ours) pid_ns.
However, after 32084504 pidns: use
On Fri, Jun 07, 2013 at 06:55:58PM +0200, Michael Holzheu wrote:
[..]
/*
- * Create kdump ELF core header in new kernel, if it has not been passed via
- * the elfcorehdr kernel parameter
+ * Free ELF core header (new kernel)
*/
-static int setup_kdump_elfcorehdr(void)
+void
On 06/14/2013 10:43 AM, Alexander Holler wrote:
Am 14.06.2013 19:23, schrieb John Stultz:
On 06/14/2013 09:52 AM, Alexander Holler wrote:
Some RTCs offer a higher resolution than seconds. To support reading
such
high resolution timestamps from inside the kernel implement
rtc_read_timeval()
On 06/14/2013 09:52 AM, Alexander Holler wrote:
Some RTCs do provide a higher precision than seconds. Add support for them
by trying rtc_read_timeval() before using rtc_read_time() to get the time
in the hctosys mechanism.
[snip]
+ rc = rtc_read_timeval(rtc, tv);
+ if (rc ||
From: Randy Dunlap rdun...@infradead.org
Add Fast User Mutexes (futexes) to kernel-locking docbook.
Signed-off-by: Randy Dunlap rdun...@infradead.org
---
Documentation/DocBook/kernel-locking.tmpl |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
---
On 06/14/2013 09:52 AM, Alexander Holler wrote:
hctosys= specifies the driver (RTC) name which sets the system clock at
boot, if and only if userspace hasn't set the time before the driver will
be loaded.
If hctosys will not be specified, the first available hardware clock
with a valid time
btrfs_file_llseek() and ocfs2_file_llseek() are extremely similar and
consequently, contain many of the same flaws. Li Dongyang filed a pull request
with ZFSOnLinux for SEEK_HOLE/SEEK_DATA support that included a custom llseek
function that appears to have been modelled after the one in ocfs2. The
There are multiple issues with the custom llseek implemented in ocfs2 for
implementing SEEK_HOLE/SEEK_DATA.
1. It takes the inode-i_mutex lock before calling generic_file_llseek(), which
is unnecessary.
2. It fails to take the filp-f_lock spinlock before modifying filp-f_pos and
filp-f_version,
There are multiple issues with the custom llseek implemented in btrfs
for implementing SEEK_HOLE/SEEK_DATA.
1. It takes the inode-i_mutex lock before calling
generic_file_llseek(), which is unnecessary.
2. It fails to take the filp-f_lock spinlock before modifying
filp-f_pos and filp-f_version,
Alexey Brodkin alexey.brod...@synopsys.com :
On 06/14/2013 02:20 AM, Francois Romieu wrote:
[...]
+struct arc_emac_priv {
+ struct net_device_stats stats;
+ unsigned int clock_frequency;
+ unsigned int max_speed;
+
+ /* Pointers to BD rings - CPU side */
+ struct arc_emac_bd_t
This patch adds maintainer information for zswap and zbud
into the MAINTAINERS file.
Signed-off-by: Seth Jennings sjenn...@linux.vnet.ibm.com
---
MAINTAINERS | 13 +
1 file changed, 13 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8bdd7a7..8c5897e 100644
---
Dear RT Folks,
I'm pleased to announce the 3.8.13-rt11 release.
changes since v3.8.13-rt10:
- use wakeup_timer_waiters() in wake_up() so we do nothing on nort
kernel. Sent by Zhao Hongjiang
- a fix for a cpu down problem. If kthread is pinned to the same CPU
which is going down we will spin
This is a preparation for next patch to avoid breaking bisecting.
If next patch is applied without this one, it will cause deadlock
as below:
Case 1:
[ 31.015593] Possible unsafe locking scenario:
[ 31.018350]CPU0CPU1
[ 31.019691]
Changeset 3b63aaa70e1 PCI: acpiphp: Do not use ACPI PCI subdriver
mechanism causes a regression which breaks ACPI dock support,
please refer to https://bugzilla.kernel.org/show_bug.cgi?id=59501
The root cause is that changeset 3b63aaa70e1 changed the relative
initialization order of ACPI dock
Alexander E. Patrakov patra...@gmail.com reports two bugs related to
dock station support on Sony VAIO VPCZ23A4R. Actually there are at least
four bugs related to Sony VAIO VPCZ23A4R dock support.
1) can't correctly detect hotplug slot for dock state
2) resource leak on undocking
3) resource
Current ACPI glue logic expects that physical devices are destroyed
before destroying companion ACPI devices, otherwise it will break the
ACPI unbind logic and cause following warning messages:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci :1b:00.0: Oops,
Please refer to https://bugzilla.kernel.org/show_bug.cgi?id=56531 for
more information.
This issue is caused by differences in PCI resource assignment between
boot time and runtime hotplug. On x86 platforms, OS respects PCI
resource assignment from BIOS and only reassign resources for unassigned
The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.git
tags/msm-clock-for-3.11
for you to fetch changes up to
Hi Tony, Vaibhav,
I just doublechecked MMC rootfs on bone and evmsk as it's the standard
smoke test. My EVM is intermittent now so trying to coax it to power up
to reverify.
Matt,
Your branch is working for me, I tested it on EVM. Not sure what is wrong
with manual rebasing
I did
On Fri, Jun 07, 2013 at 06:56:00PM +0200, Michael Holzheu wrote:
From: Jan Willeke will...@de.ibm.com
This patch introduces the s390 specific way to map pages from oldmem.
The memory area below OLDMEM_SIZE is mapped with offset OLDMEM_BASE.
The other old memory is mapped directly.
If we
On 05/23/2013 08:35 PM, Li, Zhen-Hua wrote:
In Intel Vt-D specs, Chapter 9.3 Page-Table Entry,
The size of ADDR(address) field is 12:51, but the function dma_pte_addr
treats it as 12:63.
Signed-off-by: Li, Zhen-Huazhen-h...@hp.com
---
drivers/iommu/intel-iommu.c |4 ++--
On 06/14/2013 04:05:34 AM, Rojhalat Ibrahim wrote:
Commit 50d8f87d2b3 (powerpc/fsl-pci Make PCIe hotplug work with
Freescale
PCIe controllers) does not handle non-PCIe controllers properly,
which causes
a panic during boot for certain configurations.
This patch fixes the issue by calling
On Fri, 14 Jun 2013, Christoph Lameter wrote:
It's possible to avoid such problems (or at least to make them less
probable)
by avoiding direct compaction. If it's not possible to allocate a contiguous
page without compaction, slub will fall back to order 0 page(s). In this
case
Now that debug_ll_io_init() maps memory via iotable_init() we
don't get much information in vmallocinfo about what the mapping
corresponds to. Introduce iotable_init_caller() that does the
same thing as iotable_init() except that it allows us to specify
the function that should appear in
Failure to add the mapping created in debug_ll_io_init() can lead
to the BUG_ON() triggering in lib/ioremap.c:27 if the static
virtual address decided for the debug_ll mapping overlaps with
another mapping that is created later. This happens because the
generic ioremap code has no idea there is a
Change __device_suspend() path to include driver name and the ops that
get run for a device. This additional information helps associate the
driver and the type of pm_ops the device uses in the suspend path very
quickly which will aid in debugging problems in suspend and resume paths.
Changed both
On Fri, Jun 14, 2013 at 6:23 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Thu, Jun 13, 2013 at 10:22:05AM +0200, Daniel Vetter wrote:
On Thu, Jun 06, 2013 at 04:59:26PM +0300, Jani Nikula wrote:
With Greg's address fixed. Please drop the old one from any
replies. Sorry for
On Fri, 14 Jun 2013, James Bottomley wrote:
From 48bbf44a96676ce6f520a408378730c976e9a11e Mon Sep 17 00:00:00 2001
From: James Bottomley jbottom...@parallels.com
Date: Wed, 8 May 2013 14:05:34 -0700
Subject: [PATCH] [PARISC] fix WARNING: at kernel/cpu/idle.c:96
On PA-RISC (and presumably
901 - 1000 of 1176 matches
Mail list logo
