On 28 June 2013 17:05, Mark Brown wrote:
> On Tue, Jun 25, 2013 at 11:56:12AM +0530, Sachin Kamat wrote:
>
>> There is no change in the bindings, but just a correction in the
>> documentation to reflect the
>> implementation. Earlier when Samsung platforms did not have pinctrl
>> driver, legacy GP
Hi Linus !
Earlier today I mentioned that while we had fixed the kernel crashes,
EEH error recovery didn't always recover... It appears that I had
a fix for that already in powerpc-next (with a stable CC).
I cherry-picked it today and did a few tests and it seems that things
now work quite well.
Being able to examine page tables is handy, so make this a module that
can be loaded as needed.
Signed-off-by: Kees Cook
---
arch/x86/Kconfig.debug|2 +-
arch/x86/kernel/head.c|6 ++
arch/x86/mm/dump_pagetables.c | 13 ++---
3 files changed, 17 insertions(+)
pmu-tools is a toolkit to provide various Intel specific profiling
functionality on top of perf.
It does not aim to replace traditional perf, just extend it with
some (more or less) experimental features, or provide easy wrappers
to use them in a straight forward way. Some of the functionality
On 06/25/2013 01:11:00 PM, Leif Lindholm wrote:
This patch provides documentation of the [U]EFI runtime services and
configuration features.
Signed-off-by: Leif Lindholm
---
Documentation/arm/00-INDEX |3 +++
Documentation/arm/uefi.txt | 39
+++
2 f
On 06/25/2013 12:46:40 PM, Leif Lindholm wrote:
This patch provides documentation of the early_ioremap()
functionality,
including its implementation and usage instructions.
Signed-off-by: Leif Lindholm
---
Documentation/arm/00-INDEX |2 ++
Documentation/arm/early_ioremap.txt |
On 06/29/2013 08:15:40 PM, Eric W. Biederman wrote:
Rob Landley writes:
> From: Rob Landley
>
> Mounting MS_NOUSER prevents --bind mounts from rootfs. Prevent new
rootfs
> mounts with a different mechanism that doesn't affect bind mounts.
I don't see patches 4 and 5 so I don't know if you
Hi Geert,
On 27/06/13 16:49, Geert Uytterhoeven wrote:
On Thu, Jun 27, 2013 at 1:08 AM, Greg Ungerer wrote:
On 26/06/13 05:40, Geert Uytterhoeven wrote:
Some instances of config_BSP() lack an __init annotation.
Signed-off-by: Geert Uytterhoeven
Acked-by: Greg Ungerer
Looks good. Are y
On 06/29/2013 08:15:40 PM, Eric W. Biederman wrote:
Rob Landley writes:
> From: Rob Landley
>
> Mounting MS_NOUSER prevents --bind mounts from rootfs. Prevent new
rootfs
> mounts with a different mechanism that doesn't affect bind mounts.
I don't see patches 4 and 5 so I don't know if you
On Sun, Jun 30, 2013 at 12:05:31PM +1000, Dave Chinner wrote:
> On Sat, Jun 29, 2013 at 03:23:48PM -0700, Linus Torvalds wrote:
> > On Sat, Jun 29, 2013 at 1:13 PM, Dave Jones wrote:
> > >
> > > So with that patch, those two boxes have now been fuzzing away for
> > > over 24hrs without seeing that
On Sat, Jun 29, 2013 at 03:23:48PM -0700, Linus Torvalds wrote:
> On Sat, Jun 29, 2013 at 1:13 PM, Dave Jones wrote:
> >
> > So with that patch, those two boxes have now been fuzzing away for
> > over 24hrs without seeing that specific sync related bug.
>
> Ok, so at least that confirms that yes,
Greetings.
I'm working on an embedded project (developing on x86-64, targeting ppc32).
My build system goes through and builds targets in a certain order:
u-boot
kernel (uImage, modules, headers)
elftools
perf
... lots more ...
(Yes, if I had understood how all the parts fit together
Rob Landley writes:
> From: Rob Landley
>
> Mounting MS_NOUSER prevents --bind mounts from rootfs. Prevent new rootfs
> mounts with a different mechanism that doesn't affect bind mounts.
I don't see patches 4 and 5 so I don't know if you have covered this
elsewhere but a very important part of
This is a DT only driver and st_pctl_of_match is always compiled
in. Hence of_match_ptr is unnecessary.
Signed-off-by: Axel Lin
Acked-by: Linus Walleij
---
This patch was sent on https://lkml.org/lkml/2013/6/28/420.
Resend to Mark because this driver is merged via regmap tree.
drivers/pinctrl/
On Sat, Jun 29, 2013 at 11:58:04PM +0300, Sergey Meirovich wrote:
> Hi,
>
> On 27 June 2013 20:59, Greg KH wrote:
> > I'm announcing the release of the 3.9.8 kernel.
> >
> > All users of the 3.9 kernel series must upgrade.
>
> I've got issues with my radeon ("01:00.0 VGA compatible controller:
>
On Sat, Jun 29, 2013 at 6:53 PM, Matthias Kaehlcke
wrote:
> The command and status register in the driver were swapped with
> respect to the order specified in the datasheet (CY8CTMA140).
> Confirmed with Cypress that the order in the datasheet is correct.
>
> Signed-off-by: Matthias Kaehlcke
> A
On 06/29/13 15:20, Eric Dumazet wrote:
> On Sat, 2013-06-29 at 07:36 +0800, Joe Jin wrote:
>> Hi Eric,
>>
>> The patch not fix the issue and panic as same as early I posted:
>>> BUG: unable to handle kernel paging request at 88006d9e8d48
>>> IP: [] memcpy+0xb/0x120
>>> PGD 1798067 PUD 1fd2067 P
On Sat, 2013-06-29 at 19:44 -0400, Dave Jones wrote:
> Yeah, this is running as a user. Those don't sound like things that should
> be possible. What instrumentation could I add to figure out why
> that kthread got awakened ?
trace-cmd record -e sched_wakeup -f 'comm ~ "migrati*"'
Add "-O sta
On Sat, 2013-06-29 at 15:23 -0700, Linus Torvalds wrote:
> Does the machine recover? Because if it does, I'd be inclined to just
> ignore it. Although it would be interesting to hear what triggers this
> - normal users - and I'm assuming you're still running trinity as
> non-root - generally shoul
On Sat, Jun 29, 2013 at 4:52 PM, Sergey Meirovich wrote:
>
> There was overheating issue, that caused forced power off in the
> middle of the first compile.
Ok, then the thing is easily explained by simply the filesystem being
shut down in an incomplete state. Sounds like the mkregtable binary
ha
On Fri, Jun 28, 2013 at 7:09 AM, Borislav Petkov wrote:
> Btw, do we have any perf data showing any improvements from this patch?
I wrote a simple test the measures the time it takes to acquire and
release an uncontended mutex (i.e., we always take the fast path)
100k times. I ran it a few time
On 30 June 2013 01:13, Linus Torvalds wrote:
> On Sat, Jun 29, 2013 at 2:07 PM, Sergey Meirovich
> wrote:
>>> (and possibly the
>>> mkregtable binary) and trying again might fix it.
>>
>> Removing mkregtable has indeed the compile issue for me. Thanks!
>
> Ok, so something failed at an earlier
On Fri, Jun 28, 2013 at 6:10 PM, Axel Lin wrote:
> This is a DT only driver and st_pctl_of_match is always compiled
> in. Hence of_match_ptr is unnecessary.
>
> Signed-off-by: Axel Lin
Acked-by: Linus Walleij
This driver is merged in Mark Brown's regmap tree, please
resend it with my ACK and
On Sat, Jun 29, 2013 at 03:23:48PM -0700, Linus Torvalds wrote:
> > So with that patch, those two boxes have now been fuzzing away for
> > over 24hrs without seeing that specific sync related bug.
>
> Ok, so at least that confirms that yes, the problem is the excessive
> contention on inode_
On Thu, Jun 27, 2013 at 2:58 PM, Yijing Wang wrote:
> Use standard PM state macros PCI_Dx instead of numeric 0/1/2..
>
> Signed-off-by: Yijing Wang
> Cc: Michael Buesch
> Cc: Grant Likely
> Cc: Linus Walleij
> Cc: Jiri Kosina
> Cc: linux-kernel@vger.kernel.org
Patch applied.
Yours,
Linus W
On Sun, Jun 30, 2013 at 8:13 AM, Linus Torvalds
wrote:
> On Sat, Jun 29, 2013 at 2:07 PM, Sergey Meirovich
> wrote:
>>> (and possibly the
>>> mkregtable binary) and trying again might fix it.
>>
>> Removing mkregtable has indeed the compile issue for me. Thanks!
>
> Ok, so something failed at a
On Wed, Jun 26, 2013 at 1:56 PM, Simon Guinot wrote:
> This patch adds support for the GPIOs found on the Fintek Super-I/O
> chips F71882FG and F71889F.
>
> Signed-off-by: Simon Guinot
Please be more elaborate in the commit message. What kind of beast
is a Super-I/O chip? Which architecture is
I'm announcing the release of the 3.2.48 kernel.
All users of the 3.2 kernel series should upgrade.
The updated 3.2.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.2.y
and can be browsed at the normal kernel.org git web browser:
Due to recent changes and expecations of proper cpu bindings, there are
now cases for many of the in-tree devicetrees where a WARN() will hit
on boot due to badly formatted /cpus nodes.
Downgrade this to a pr_warn() to be less alarmist, since it's not a
new problem.
Tested on Arndale, Cubox, Seab
On Mon, Jun 24, 2013 at 1:54 PM, Michal Simek wrote:
>> I commented your comment on v1, and said I think you can support
>> both bindings.
>
> in 2/6 you have applied that dual support for this driver
> and that's why please add this binding description to your repo
> because it reflects actual b
On Sun, Jun 30, 2013 at 12:14:26AM +0100, Russell King - ARM Linux wrote:
> On Sat, Jun 29, 2013 at 03:54:26PM -0700, Olof Johansson wrote:
> > Most of this ruffle seems to be about the fact that booting a kernel
> > with a device tree that doesn't conform to the brand spanking new,
> > and never p
Hi Linus !
We discovered some breakage in our "EEH" (PCI Error Handling) code while
doing error injection, due to a couple of regressions. One of them is
due to a patch (37f02195b) that, in hindsight, I shouldn't have merged
considering that it caused more problems than it solved.
Please pull tho
On 13-06-29 02:47 PM, Henrique de Moraes Holschuh wrote:
> You know, either the "long" or the "offline" SMART test routines do exactly
> that on any spinning rust device with a firmware that is not utterly broken.
>
> The HDD's firmware will rewrite, and even reallocate any "weak" sectors
> found
On Sat, Jun 29, 2013 at 03:54:26PM -0700, Olof Johansson wrote:
> Most of this ruffle seems to be about the fact that booting a kernel
> with a device tree that doesn't conform to the brand spanking new,
> and never previously enforced, binding for the cpu nodes will produce
> a WARN_ON(). Lots of
On Sat, Jun 29, 2013 at 08:38:19PM +0100, Russell King - ARM Linux wrote:
> On Fri, Jun 28, 2013 at 01:05:42PM -0700, Olof Johansson wrote:
> > On Fri, Jun 28, 2013 at 1:03 PM, Maxime Ripard
> > wrote:
> > > On Fri, Jun 28, 2013 at 06:15:32PM +0100, Lorenzo Pieralisi wrote:
> > >> The patch above
On Sat, Jun 29, 2013 at 2:58 PM, Linus Torvalds
wrote:
>
> STEP 1:
>
> - create a new set of config option (say
> "CONFIG_[ARCH_]SPINLOCK_REFCOUNT") that defaults to 'y' and isn't
> actually asked about anywhere.
That "defauls to 'y'" was incomplete/misleading. The
ARCH_SPINLOCK_REFCOUNT config
On 06/29/2013 06:11 PM, Linus Torvalds wrote:
On Sat, Jun 29, 2013 at 2:34 PM, Waiman Long wrote:
I think I got it now. For architecture with transactional memory support to
use an alternative implementation, we will need to use some kind of dynamic
patching at kernel boot up time as not all CP
On Sat, Jun 29, 2013 at 1:13 PM, Dave Jones wrote:
>
> So with that patch, those two boxes have now been fuzzing away for
> over 24hrs without seeing that specific sync related bug.
Ok, so at least that confirms that yes, the problem is the excessive
contention on inode_sb_list_lock.
Ugh. There'
From: Max Filippov
Add support for HPB-DMAC found in Renesas R-Car SoCs, using 'shdma-base' DMA
driver framework.
Based on the original patch by Phil Edworthy .
Signed-off-by: Max Filippov
[Sergei: removed useless #include, sorted #include's, fixed HPB_DMA_TCR_MAX,
fixed formats and removed l
On Sat, Jun 29, 2013 at 2:07 PM, Sergey Meirovich wrote:
>> (and possibly the
>> mkregtable binary) and trying again might fix it.
>
> Removing mkregtable has indeed the compile issue for me. Thanks!
Ok, so something failed at an earlier build. That error is probably
long gone, though, since the
On Sat, Jun 29, 2013 at 2:34 PM, Waiman Long wrote:
>
> I think I got it now. For architecture with transactional memory support to
> use an alternative implementation, we will need to use some kind of dynamic
> patching at kernel boot up time as not all CPUs in that architecture will
> have that
On Sat, Jun 29, 2013 at 1:23 PM, Waiman Long wrote:
>>
>> But more importantly, I think this needs to be architecture-specific,
>> and using to try to do some generic 64-bit
>> cmpxchg() version is a bad bad idea.
>
> Yes, I can put the current implementation into
> asm-generic/spinlock_refcount.
Folks:
I sent the indented text to gre...@linuxfoundation.org, inappropriately
as I suspected. I got a polite automated response suggesting alternate
destinations for my email. To my non-technical eyes, your addresses
seemed most appropriate.
"Mr. Kroah-Hartman,
"Excuse me for bothe
Hello.
On 06/30/2013 12:15 AM, Sergei Shtylyov wrote:
Oops, forgot to add the From: line. The patch is not mine, I've only
modified it slightly. Will repost now...
Add support for HPB-DMAC found in Renesas R-Car SoCs, using 'shdma-base' DMA
driver framework.
Based on the original patch b
On 06/29/2013 04:23 PM, Waiman Long wrote:
On 06/29/2013 01:45 PM, Linus Torvalds wrote:
But more importantly, I think this needs to be architecture-specific,
and using to try to do some generic 64-bit
cmpxchg() version is a bad bad idea.
Yes, I can put the current implementation into
asm-g
Hi Linus,
On 29 June 2013 21:11, Linus Torvalds wrote:
> On Sat, Jun 29, 2013 at 8:05 AM, Sergey Meirovich
> wrote:
>>
>> 3.10-rc7 doesn't compile for me
>>
>> rathamahata@piledriver /usr/local/src/linux-3.10-rc7 $ make -j1 bzImage
>> modules
>> make[1]: Nothing to be done for `all'.
>> make[1
On 06/27/2013 10:44 AM, Thomas Gleixner wrote:
On Wed, 26 Jun 2013, Waiman Long wrote:
On 06/26/2013 07:06 PM, Thomas Gleixner wrote:
On Wed, 26 Jun 2013, Waiman Long wrote:
This is a complete design disaster. You are violating every single
rule of proper layering. The differentiation of spinlo
Hi,
On 27 June 2013 20:59, Greg KH wrote:
> I'm announcing the release of the 3.9.8 kernel.
>
> All users of the 3.9 kernel series must upgrade.
I've got issues with my radeon ("01:00.0 VGA compatible controller:
Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M
Series]") APU
On 29 June 2013 23:50, Sergey Meirovich wrote:
> Hi,
>
> On 14 February 2013 21:12, Greg KH wrote:
>> I'm announcing the release of the 3.7.8 kernel.
Please ignore - this is about 3.9.8 kernel
>
> I've got issues with my radeon GPU on 3.7.8
> ...
> [ 20.944106] BUG: unable to handle kernel NU
On 29 June 2013 15:23, Eric W. Biederman wrote:
>
> Nacked-by: "Eric W. Biederman"
>
> The pach does not solve the problem described.
Which might be true, and I am open to better proposals.
> Sami Kerola writes:
>
>> The kernel does not expose precise start time anywhere. Precision of
>> sysi
Hi,
On 14 February 2013 21:12, Greg KH wrote:
> I'm announcing the release of the 3.7.8 kernel.
I've got issues with my radeon GPU on 3.7.8
...
[ 20.944106] BUG: unable to handle kernel NULL pointer dereference
at 01f8
[ 20.945753] IP: [] radeon_vm_bo_add+0xb3/0x110
[ 20.946498
On 06/28/2013 09:46 AM, Thomas Gleixner wrote:
On Thu, 27 Jun 2013, Waiman Long wrote:
On 06/26/2013 09:37 PM, Andi Kleen wrote:
It will be hard to know what changes will be needed without knowing
the exact semantics of the spinlock functions with lock elision. Can
you explain a little more wha
--
Seven Hundred and Fifty Thousand usd deposit alert from Western Union. Send
Your Name, Telephone Number, Country, Occupation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.ke
On 06/29/2013 01:45 PM, Linus Torvalds wrote:
Sorry for not commenting earlier, I was traveling and keeping email to
a minimum..
On Wed, Jun 26, 2013 at 10:43 AM, Waiman Long wrote:
This patch introduces a new spinlock_refcount.h header file to be
included by kernel code that want to do a lock
Add support for HPB-DMAC found in Renesas R-Car SoCs, using 'shdma-base' DMA
driver framework.
Based on the original patch by Phil Edworthy .
Signed-off-by: Max Filippov
[Sergei: removed useless #include, sorted #include's, fixed HPB_DMA_TCR_MAX,
fixed formats and removed line breaks in the dev
Use tmpfs for rootfs when CONFIG_TMPFS=y and there's no root=.
Specify rootfstype=ramfs to get the old initramfs behavior.
The previous initramfs code provided a fairly crappy root filesystem:
didn't let you --bind mount directories out of it, reported zero
size/usage so it didn't show up in "df"
From: Rob Landley
Even though ramfs hasn't got a backing device, commit e0bf68ddec4f added one
anyway, and put the initialization in init_rootfs() since that's the first
user, leaving it out of init_ramfs() to avoid duplication.
But initmpfs uses init_tmpfs() instead, so move the init into the f
On Fri, Jun 28, 2013 at 01:58:25PM +1000, Dave Chinner wrote:
> > Oh, that's easy enough to fix. It's just changing the wait_sb_inodes
> > loop to use a spin_trylock(&inode->i_lock), moving the inode to
> > the end of the sync list, dropping all locks and starting again...
>
> New version be
From: Rob Landley
When the rootfs code was a wrapper around ramfs, having them in the same
file made sense. Now that it can wrap another filesystem type, move it
in with the init code instead.
This also allows a subsequent patch to access rootfstype= command line arg.
Signed-off-by: Rob Landley
From: Rob Landley
Command line option rootfstype=ramfs to obtain old initramfs behavior,
and use ramfs instead of tmpfs for stub when root= defined (for cosmetic
reasons).
Signed-off-by: Rob Landley
---
init/do_mounts.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
From: Rob Landley
Mounting MS_NOUSER prevents --bind mounts from rootfs. Prevent new rootfs
mounts with a different mechanism that doesn't affect bind mounts.
Signed-off-by: Rob Landley
---
fs/ramfs/inode.c |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/fs/ramf
From: Rob Landley
Conditionally call the appropriate fs_init function and fill_super functions.
Add a use once guard to shmem_init() to simply succeed on a second call.
(Note that IS_ENABLED() is a compile time constant so dead code elimination
removes unused function calls when CONFIG_TMPFS is
On Sat, Jun 29, 2013 at 08:38:19PM +0100, Russell King - ARM Linux wrote:
> On Fri, Jun 28, 2013 at 01:05:42PM -0700, Olof Johansson wrote:
> > On Fri, Jun 28, 2013 at 1:03 PM, Maxime Ripard
> > wrote:
> > > On Fri, Jun 28, 2013 at 06:15:32PM +0100, Lorenzo Pieralisi wrote:
> > >> The patch above
On Sat, Jun 29, 2013 at 12:55 PM, Russell King - ARM Linux
wrote:
> On Sat, Jun 29, 2013 at 12:29:55PM -0700, Yinghai Lu wrote:
>> >> On these SoCs which Santosh is working on, the main physical memory
>> >> mapping is above 4GB, with just a small alias below 4GB to allow the
>> >> system to boot
On Sat, Jun 29, 2013 at 12:29:55PM -0700, Yinghai Lu wrote:
> On Sat, Jun 29, 2013 at 10:57 AM, Tejun Heo wrote:
> > ( Expanding cc list, original thread is at
> > http://thread.gmane.org/gmane.linux.kernel/1518046 )
> >
> > Hello,
> >
> > On Sat, Jun 29, 2013 at 06:21:24PM +0100, Russell King -
Hi all,
I hate to say it, but this regression from 3.9 is still present in
3.10-rc7 :-(
Am 19.06.2013 11:02, schrieb Stefan Seyfried:
> The suspend/resume failure is easily reproduced by
>
> * booting with "init=/bin/bash no_console_suspend"
> * mount /sys
> * echo mem > /sys/power/state
> * res
On Fri, Jun 28, 2013 at 6:45 PM, Brian Gitonga Marete
wrote:
> On Fri, Jun 28, 2013 at 3:55 PM, Deucher, Alexander
> wrote:
>>
>> Can you bisect?
>>
>
Hello Alexander,
So, it turns out that it is not so easy to reproduce this issue. I
have been trying to reproduce it with the exact revision of
On Fri, Jun 28, 2013 at 01:05:42PM -0700, Olof Johansson wrote:
> On Fri, Jun 28, 2013 at 1:03 PM, Maxime Ripard
> wrote:
> > On Fri, Jun 28, 2013 at 06:15:32PM +0100, Lorenzo Pieralisi wrote:
> >> The patch above should already be queued in next/dt right ?
> >
> > Indeed.
> >
> > Then why the lat
On Sat, Jun 29, 2013 at 10:57 AM, Tejun Heo wrote:
> ( Expanding cc list, original thread is at
> http://thread.gmane.org/gmane.linux.kernel/1518046 )
>
> Hello,
>
> On Sat, Jun 29, 2013 at 06:21:24PM +0100, Russell King - ARM Linux wrote:
>> Unfortunately, that has not been true on ARM - it's v
On Sat, Jun 29, 2013 at 07:07:30PM +0100, Maxime Ripard wrote:
> On Fri, Jun 28, 2013 at 10:45:12PM +0100, Lorenzo Pieralisi wrote:
> > On Fri, Jun 28, 2013 at 09:05:42PM +0100, Olof Johansson wrote:
> > > On Fri, Jun 28, 2013 at 1:03 PM, Maxime Ripard
> > > wrote:
> > > > On Fri, Jun 28, 2013 at
On 28/06/2013 19:51, Ben Hutchings wrote:
On Fri, 2013-06-28 at 15:59 +0300, Eliezer Tamir wrote:
Our use of sched_clock is OK because we don't mind the side effects
of calling it and occasionally waking up on a different CPU.
Sure about that? Jitter matters too.
Pretty sure, this is a limi
You know, either the "long" or the "offline" SMART test routines do exactly
that on any spinning rust device with a firmware that is not utterly broken.
The HDD's firmware will rewrite, and even reallocate any "weak" sectors
found by the surface scan.
--
"One disk to rule them all, One disk to
On Fri, Jun 28, 2013 at 6:49 AM, Mathieu Desnoyers
wrote:
> This __put_user() could be used by unprivileged processes to write into
> kernel memory. The issue here is that even if copy_siginfo_to_user()
> fails, the error code is not checked before __put_user() is executed.
> Luckily, ptrace_peek_
3 makes sense to me.
Tejun Heo wrote:
>( Expanding cc list, original thread is at
> http://thread.gmane.org/gmane.linux.kernel/1518046 )
>
>Hello,
>
>On Sat, Jun 29, 2013 at 06:21:24PM +0100, Russell King - ARM Linux
>wrote:
>> Unfortunately, that has not been true on ARM - it's very common for
On Sat, Jun 29, 2013 at 8:05 AM, Sergey Meirovich wrote:
>
> 3.10-rc7 doesn't compile for me
>
> rathamahata@piledriver /usr/local/src/linux-3.10-rc7 $ make -j1 bzImage
> modules
> make[1]: Nothing to be done for `all'.
> make[1]: Nothing to be done for `relocs'.
> CHK include/generated/uap
On Fri, Jun 28, 2013 at 10:45:12PM +0100, Lorenzo Pieralisi wrote:
> On Fri, Jun 28, 2013 at 09:05:42PM +0100, Olof Johansson wrote:
> > On Fri, Jun 28, 2013 at 1:03 PM, Maxime Ripard
> > wrote:
> > > On Fri, Jun 28, 2013 at 06:15:32PM +0100, Lorenzo Pieralisi wrote:
> > >> On Fri, Jun 28, 2013 at
On Sat, Jun 29, 2013 at 09:24:41AM +0200, Ingo Molnar wrote:
>
> * Nathan Zimmer wrote:
>
> > On 06/26/2013 10:35 PM, Daniel J Blueman wrote:
> > >On Wednesday, June 26, 2013 9:30:02 PM UTC+8, Andrew Morton wrote:
> > >>
> > >> On Wed, 26 Jun 2013 11:22:48 +0200 Ingo Molnar
> > > wrote:
> > >>
>
( Expanding cc list, original thread is at
http://thread.gmane.org/gmane.linux.kernel/1518046 )
Hello,
On Sat, Jun 29, 2013 at 06:21:24PM +0100, Russell King - ARM Linux wrote:
> Unfortunately, that has not been true on ARM - it's very common for
> there to be an offset on physical memory, some
From: Miklos Szeredi
The feature prevents mistrusted filesystems to grow a large number of dirty
pages before throttling. For such filesystems balance_dirty_pages always
check bdi counters against bdi limits. I.e. even if global "nr_dirty" is under
"freerun", it's not allowed to skip bdi checks.
The aim of .flush fop is to hint file-system that flushing its state or caches
or any other important data to reliable storage would be desirable now.
fuse_flush() passes this hint by sending FUSE_FLUSH request to userspace.
However, dirty pages and pages under writeback may be not visible to users
From: Pavel Emelyanov
Any write request requires a file handle to report to the userspace. Thus
when we close a file (and free the fuse_file with this info) we have to
flush all the outstanding dirty pages.
filemap_write_and_wait() is enough because every page under fuse writeback
is accounted i
From: Pavel Emelyanov
The problem is:
1. write cached data to a file
2. read directly from the same file (via another fd)
The 2nd operation may read stale data, i.e. the one that was in a file
before the 1st op. Problem is in how fuse manages writeback.
When direct op occurs the core kernel co
From: Pavel Emelyanov
Introduce a bit kernel and userspace exchange between each-other on
the init stage and turn writeback on if the userspace want this and
mount option 'allow_wbcache' is present (controlled by fusermount).
Also add each writable file into per-inode write list and call the
gen
fuse_writepage_locked() should never submit new i/o for given page->index
if there is another one 'in progress' already. In most cases it's safe to
wait on page writeback. But if it was called due to memory shortage
(WB_SYNC_NONE), we should redirty page rather than blocking caller.
Signed-off-by:
Let the kernel maintain i_mtime locally:
- clear S_NOCMTIME
- implement i_op->update_time()
- flush mtime on fsync and last close
- update i_mtime explicitly on truncate and fallocate
Fuse inode flag FUSE_I_MTIME_UPDATED serves as indication that local i_mtime
should be flushed to the server e
From: Pavel Emelyanov
The .writepages one is required to make each writeback request carry more than
one page on it. The patch enables optimized behaviour unconditionally,
i.e. mmap-ed writes will benefit from the patch even if fc->writeback_cache=0.
Signed-off-by: Maxim Patlasov
---
fs/fuse/f
From: Pavel Emelyanov
The .write_begin and .write_end are requiered to use generic routines
(generic_file_aio_write --> ... --> generic_perform_write) for buffered
writes.
Signed-off-by: Maxim Patlasov
---
fs/fuse/file.c | 97
1 files
Move the code filling and sending read request to a separate function. Future
patches will use it for .write_begin -- partial modification of a page
requires reading the page from the storage very similarly to what fuse_readpage
does.
Signed-off-by: Maxim Patlasov
---
fs/fuse/file.c | 55 +
Sorry for not commenting earlier, I was traveling and keeping email to
a minimum..
On Wed, Jun 26, 2013 at 10:43 AM, Waiman Long wrote:
> This patch introduces a new spinlock_refcount.h header file to be
> included by kernel code that want to do a lockless update of reference
> count protected by
From: Pavel Emelyanov
Make fuse think that when writeback is on the inode's i_size is always
up-to-date and not update it with the value received from the userspace.
This is done because the page cache code may update i_size without letting
the FS know.
This assumption implies fixing the previou
From: Pavel Emelyanov
Off (0) by default. Will be used in the next patches and will be turned
on at the very end.
Signed-off-by: Maxim Patlasov
Signed-off-by: Pavel Emelyanov
---
fs/fuse/fuse_i.h |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/fs/fuse/fuse_i.h b/fs/
From: Pavel Emelyanov
When writeback is ON every writeable file should be in per-inode write list,
not only mmap-ed ones. Thus introduce a helper for this linkage.
Signed-off-by: Maxim Patlasov
Signed-off-by: Pavel Emelyanov
---
fs/fuse/file.c | 33 +++--
1 files
From: Pavel Emelyanov
The .writepages callback will issue writeback requests with more than one
page aboard. Make existing end/check code be aware of this.
Signed-off-by: Maxim Patlasov
---
fs/fuse/file.c | 24
1 files changed, 16 insertions(+), 8 deletions(-)
diff
From: Pavel Emelyanov
There will be a .writepageS callback implementation which will need to
get a fuse_file out of a fuse_inode, thus make a helper for this.
Signed-off-by: Maxim Patlasov
Signed-off-by: Pavel Emelyanov
---
fs/fuse/file.c | 24
1 files changed, 16 i
From: Pavel Emelyanov
A helper which gets called when read reports less bytes than was requested.
See patch #6 (trust kernel i_size only) for details.
Signed-off-by: Maxim Patlasov
Signed-off-by: Pavel Emelyanov
---
fs/fuse/file.c | 21 +
1 files changed, 13 insertions(+
Hi,
This is the fifth iteration of Pavel Emelyanov's patch-set implementing
write-back policy for FUSE page cache. Initial patch-set description was
the following:
One of the problems with the existing FUSE implementation is that it uses the
write-through cache policy which results in performance
On Sat, Jun 29, 2013 at 08:29:59AM -0700, Tejun Heo wrote:
> I suppose LPAE on arm is analogous to PAE on x86, IOW, high memory?
> This does affect memory initilization as you need to register memory
> areas which aren't addressable directly; however, why does it affect
> generic code which is just
Hello, Tim.
On Fri, Jun 28, 2013 at 11:44:23AM -0700, Tim Hockin wrote:
> I totally understand where you're coming from - trying to get back to
> a stable feature set. But it sucks to be on the losing end of that
Oh, it has been sucking and will continue to suck like hell for me too
for the fore
The implementation in of_regulator_match() already ensures match->init_data is
not NULL for all matched cases if the return value of of_regulator_match() > 0.
Thus remove NULL test for rmatch[i].init_data.
This patch also fixes the condition for loop iteration.
The for loop should iterate "matche
On 06/29/2013 09:26 AM, Eric Dumazet wrote:
On Sat, 2013-06-29 at 09:11 -0700, Ben Greear wrote:
Do you know if your patch should go in 3.9?
Yes it should.
Ok, I'll add that to my tree.
Your test case sounds a bit like what gives us the rare crash in tcp_collapse
(we have lots of bouncin
1 - 100 of 139 matches
Mail list logo
