hi,
On Thu, Jan 30, 2014 at 2:24 PM, Linus Torvalds
wrote:
> I'm adding in some people here, because I think in the end this bug
> was introduced by commit 304bceda6a18 ("x86, fpu: use non-lazy fpu
> restore for processors supporting xsave") that introduced that
> math_state_restore() in
Fixed Below coding style errors -
octeon-hcd.h:146: ERROR: spaces prohibited around that ':' (ctx:WxW)
octeon-hcd.h:147: ERROR: spaces prohibited around that ':' (ctx:WxW)
total: 243 errors, 0 warnings, 1819 lines checked - fixed all errors
Signed-off-by: Surendra Patil
---
* Dave Hansen wrote:
> On 01/30/2014 12:55 AM, Ingo Molnar wrote:
> >> > + This kernel feature is useful for number crunching
> >> > applications
> >> > + that may need to compute untrusted bytecode during their
> >> > + execution. By using pipes or other transports
Hi, David
Thank you for taking look at this and adding the missing patch
description. WRT your patch, please see the comment inline.
On 01/31/2014 02:39 AM, David Rientjes wrote:
> On Thu, 30 Jan 2014, Andrew Morton wrote:
>
>>> It always was.
>> eh? kmem_cache_create_memcg()'s kstrdup() will
Hi Vinod,
On Mon, Jan 27, 2014 at 4:36 PM, Srikanth Thokala wrote:
> Hi Vinod,
>
> On Sun, Jan 26, 2014 at 7:29 PM, Vinod Koul wrote:
>> On Fri, Jan 24, 2014 at 02:24:27PM +0100, Lars-Peter Clausen wrote:
>>> On 01/24/2014 12:16 PM, Srikanth Thokala wrote:
>>> > Hi Lars,
>>> >
>>> > On Thu, Jan
Hi Vinod,
On Tue, Jan 28, 2014 at 8:43 AM, Vinod Koul wrote:
> On Mon, Jan 27, 2014 at 06:42:36PM +0530, Srikanth Thokala wrote:
>> Hi Lars/Vinod,
>> >> The question here i think would be waht this device supports? Is the
>> >> hardware
>> >> capable of doing interleaved transfers, then would
With d8d14bd09cdd "fs/compat: fix lookup_dcookie() parameter handling" I
changed the type of the len parameter of the lookup_dcookie() syscall.
However I missed that there was still a stale declaration in arch/tile/..
which now causes a compile error on tile:
In file included from
Hi Josh,
On 30 January 2014 22:17, Josh Boyer wrote:
> Hi All,
>
> After the DRM merge, the exynos_hdmi.c file fails to build with our
> ARM config. The error is:
>
> drivers/gpu/drm/exynos/exynos_hdmi.c:382:8: error: 'hdmi_infoframe'
> defined as wrong kind of tag
> struct hdmi_infoframe {
>
On 01/30/2014 11:16 PM, Olivier Langlois wrote:
rtl8192ce is disabling for too long the local interrupts during hw
initiatialisation when performing scans
The observable symptoms in dmesg can be:
- underruns from ALSA playback
- clock freezes (tstamps do not change for several dmesg entries
fixed below errors - only few listed
octeon-hcd.c:162: ERROR: spaces prohibited around that ':' (ctx:WxW)
cteon-hcd.c:249: ERROR: Macros with complex values should be enclosed in
parenthesis
octeon-hcd.c:992: WARNING: braces {} are not necessary for single statement
blocks
octeon-hcd.c:3228:
On Thu, Jan 23, 2014 at 08:40 PM, Linus Walleij
wrote:
> I'm holding this off until you've made up your mind about whether it's needed
> or not...
By setting the SION bit the actual status of a gpio pin can be read back
regardless of its driver configuration.
You can drop my patch as there
Hi Greg,
Sorry, I forgot to mentioned base kernel version. Following patch based on
linux-3.13.y till date.
I don't find a better way to avoid infinite loops. Moreover in worst case I
find that device lock is held forever. Usually usb_open was able to get this
lock in less than 5 seconds but
On Thu, Jan 30, 2014 at 05:27:18PM -0800, John Stultz wrote:
> On 01/29/2014 10:30 AM, Johannes Weiner wrote:
> > On Tue, Jan 28, 2014 at 05:43:54PM -0800, John Stultz wrote:
> >> On 01/28/2014 04:03 PM, Johannes Weiner wrote:
> >>> On Thu, Jan 02, 2014 at 04:12:08PM +0900, Minchan Kim wrote:
>
On Wed, Jan 29, 2014 at 10:32 PM, Max Filippov wrote:
> On Wed, Jan 29, 2014 at 9:12 PM, Florian Fainelli
> wrote:
>> On Jan 28, 2014 11:01 PM, "Max Filippov" wrote:
>>>
>>> On Wed, Jan 29, 2014 at 10:47 AM, Florian Fainelli
>>> wrote:
>>> > Hi Max,
>>> >
>>> > Le 28/01/2014 22:00, Max
Signed-off-by: Max Filippov
---
Changes v1->v2:
- fix {get,set}_settings return code in case there's no PHY.
drivers/net/ethernet/ethoc.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/net/ethernet/ethoc.c b/drivers/net/ethernet/ethoc.c
index
Hello David, Ben, Florian and everybody,
this series implements ethtool callbacks for the ethoc driver as was
requested by Florian.
Changes v1->v2:
- fix {get,set}_settings return code in case there's no PHY;
- fix set_ringparam: check ring sizes, change ring sizes on the fly.
Max Filippov (4):
Signed-off-by: Max Filippov
Reviewed-by: Florian Fainelli
Reviewed-by: Ben Hutchings
---
drivers/net/ethernet/ethoc.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/net/ethernet/ethoc.c b/drivers/net/ethernet/ethoc.c
index 779d3c3..5da32a7 100644
---
The following methods are implemented:
- get link state (standard implementation);
- get timestamping info (standard implementation).
Signed-off-by: Max Filippov
Reviewed-by: Florian Fainelli
Reviewed-by: Ben Hutchings
---
drivers/net/ethernet/ethoc.c | 6 ++
1 file changed, 6
TX and RX rings share memory and descriptors. Maximal number of
descriptors reported is one less than the total available nuber of
descriptors. For the set operation the requested number of TX descriptors
is rounded down to the nearest power of two (driver logic requirement).
Signed-off-by: Max
On Fri, 31 Jan 2014, Dave Chinner wrote:
> The read/write path is broken, Willy. We can't map arbitrary byte
> ranges to the DIO subsystem. I'm now certain that the data
> corruptions I'm seeing are in sub-sector regions from unaligned IOs
> from userspace. We still need to use the buffered IO
On Thu, 2014-01-30 at 21:43 -0500, Mikulas Patocka wrote:
>
> On Thu, 30 Jan 2014, James Bottomley wrote:
>
> > > A device may be accessed direcly (by opening /dev/sdX) and it creates a
> > > mapping too - thus, the size of a mapping limits the size of a block
> > > device.
> >
> > Right,
Hello,
I am Tete Appiah Head, Personnel and Business Banking in
Ghana. In 2010, A customer made a fixed Number Deposit $14.6Million
This investor died four years ago leaving no WILL.This is an opportunity
for me to claim the said fund through a trustworthy foreigner, If
interested I will give
On Fri, Jan 31, 2014 at 12:16:23AM -0500, Olivier Langlois wrote:
> rtl_ps_enable_nic() is called from loops that will loop until this function
> returns true or a
> maximum number of retries is performed.
>
> hw_init() returns non-zero on error. In that situation return false to
> restore the
From: Kuninori Morimoto
config->gpios[x].flags indicates initial pin status,
and it will be used for drvdata->state
on gpio_regulator_probe().
But, current of_get_gpio_regulator_config() doesn't care
about this flags.
This patch adds new gpios-status property in order to
care about initial pin
rtl8192ce is disabling for too long the local interrupts during hw
initiatialisation when performing scans
The observable symptoms in dmesg can be:
- underruns from ALSA playback
- clock freezes (tstamps do not change for several dmesg entries until irqs are
finaly reenabled):
[ 250.817669]
On Thu, 2014-01-30 at 14:19 -0600, Larry Finger wrote:
> On 01/30/2014 12:22 AM, Olivier Langlois wrote:
> > Signed-off-by: Olivier Langlois
> > ---
> > drivers/net/wireless/rtlwifi/ps.c | 2 +-
> > drivers/net/wireless/rtlwifi/rtl8192ce/hw.c | 18 --
> > 2 files
rtl_ps_enable_nic() is called from loops that will loop until this function
returns true or a
maximum number of retries is performed.
hw_init() returns non-zero on error. In that situation return false to
restore the original design intent to retry hw init when it fails.
Signed-off-by: Olivier
On Thu, Jan 30, 2014 at 6:29 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Jan 30, 2014 at 03:52:16PM -0800, Kevin Hilman wrote:
>> On Wed, Jan 29, 2014 at 5:32 AM, Maxime Ripard
>> wrote:
>> > On Wed, Jan 29, 2014 at 12:25:20PM +, Mark Brown wrote:
>> >> On Wed, Jan 29, 2014 at 12:10:48PM
This patchset is a precursor for enabling deep idle states on powerpc,
when the local CPU timers stop. The tick broadcast framework in
the Linux Kernel today handles wakeup of such CPUs at their next timer event
by using an external clock device. At the expiry of this clock device, IPIs
are sent
From: Preeti U Murthy
Split timer_interrupt(), which is the local timer interrupt handler on ppc
into routines called during regular interrupt handling and __timer_interrupt(),
which takes care of running local timers and collecting time related stats.
This will enable callers interested only
From: Srivatsa S. Bhat
The IPI handlers for both PPC_MSG_CALL_FUNC and PPC_MSG_CALL_FUNC_SINGLE map
to a common implementation - generic_smp_call_function_single_interrupt(). So,
we can consolidate them and save one of the IPI message slots, (which are
precious on powerpc, since only 4 of those
From: Srivatsa S. Bhat
For scalability and performance reasons, we want the tick broadcast IPIs
to be handled as efficiently as possible. Fixed IPI messages
are one of the most efficient mechanisms available - they are faster than
the smp_call_function mechanism because the IPI handlers are
On Thu, Jan 30, 2014 at 06:01:54PM +0100, Pavel Machek wrote:
> Hi!
>
> > diff --git a/drivers/power/Makefile b/drivers/power/Makefile
> > index 77535fd..6d184c8 100644
> > --- a/drivers/power/Makefile
> > +++ b/drivers/power/Makefile
> > @@ -59,4 +59,5 @@ obj-$(CONFIG_CHARGER_BQ24735) +=
> On Thu, Jan 30, 2014 at 6:16 PM, Eric Dumazet wrote:
> > On Wed, 2014-01-29 at 23:05 -0800, dormando wrote:
> >
> >> We hit the routing code fairly hard. Any hints for what to look at or how
> >> to instrument it? Or if it's fixed already? It's a real pain to iterate
> >> since it takes ~30
On Thu, Jan 30, 2014 at 08:44:58PM +0800, Arnd Bergmann wrote:
> On Thursday 30 January 2014, Pratyush Anand wrote:
> > On Thu, Jan 30, 2014 at 07:43:37PM +0800, Kishon Vijay Abraham I wrote:
> > > Hi,
> > >
> > > On Thursday 30 January 2014 04:18 PM, Mohit Kumar wrote:
> > > > From: Pratyush
On Thu, Jan 30, 2014 at 6:16 PM, Eric Dumazet wrote:
> On Wed, 2014-01-29 at 23:05 -0800, dormando wrote:
>
>> We hit the routing code fairly hard. Any hints for what to look at or how
>> to instrument it? Or if it's fixed already? It's a real pain to iterate
>> since it takes ~30 days to crash,
On Wed, 2014-01-29 at 12:51 +0100, Peter Zijlstra wrote:
> On Tue, Jan 28, 2014 at 02:51:35PM -0800, Jason Low wrote:
> > > But urgh, nasty problem. Lemme ponder this a bit.
>
> OK, please have a very careful look at the below. It survived a boot
> with udev -- which usually stresses mutex
On Thu, Jan 30, 2014 at 08:25:37PM +1100, Dave Chinner wrote:
> On Thu, Jan 30, 2014 at 05:42:30PM +1100, Dave Chinner wrote:
> > On Wed, Jan 15, 2014 at 08:24:18PM -0500, Matthew Wilcox wrote:
> > > This series of patches add support for XIP to ext4. Unfortunately,
> > > it turns out to be
Hi,
Way back in 2010, Frederic added commit
ebc8827f75954fe315492883eee5cb3f355d547d to warn us about cases where
faults were incorrectly firing during NMI handling on x86, as the IRET
from such faults would possibly trigger nested NMIs.
Later (2012), Salman added commit
On Thu, Jan 30, 2014 at 08:59:09AM +0100, Luca Ognibene wrote:
> Yes it's indeed very strange.. i tend to rule out application errors
> because i don't write directly to the device so i don't think i can
> break a filesystem from userspace. I've checked previous and next blocks
> and they seem ok,
On Thu, 30 Jan 2014, James Bottomley wrote:
> > A device may be accessed direcly (by opening /dev/sdX) and it creates a
> > mapping too - thus, the size of a mapping limits the size of a block
> > device.
>
> Right, that's what I suspected below. We can't damage large block
> support on
On Thu, Jan 30, 2014 at 9:03 AM, David Howells wrote:
>
> I've been asked by Kerberos developers to slightly change the behaviour of the
> add_key() and request_key() system calls and a couple of the keyctl()
> functions
> - and I'm wondering if you'd be okay with it.
So the rule about ABI
Hello Jesse,
> This looks like the kernel module included with upstream Linux instead
> of from OVS git, is that correct?
coorect.
> Can you please describe what you are doing instead of just giving your script?
I created 8 hosts. 2 hosts are connected two each switches. That gives
me 4
Hi,
On Thu, Jan 30, 2014 at 03:52:16PM -0800, Kevin Hilman wrote:
> On Wed, Jan 29, 2014 at 5:32 AM, Maxime Ripard
> wrote:
> > On Wed, Jan 29, 2014 at 12:25:20PM +, Mark Brown wrote:
> >> On Wed, Jan 29, 2014 at 12:10:48PM +0100, Maxime Ripard wrote:
> >>
> >> > +config SPI_SUN6I
> >> > +
One of the error paths in vmw_setup_otable_base causes us to return with
'ret' having never been set to anything causing us to return whatever was
on the stack.
Found with Coverity
Signed-off-by: Dave Jones
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_mob.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_mob.c
Hi all,
There will probable be no linux-next release next Monday (next-20140203).
Please do *not* add material destined for v3.15 to your linux-next
included trees until after v3.14-rc1 is released.
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140130
On 01/30/2014 09:25 PM, Andrew Lunn wrote:
On Thu, Jan 30, 2014 at 07:50:34PM +0100, Sebastian Hesselbarth wrote:
On 01/30/2014 07:29 PM, Andrew Lunn wrote:
On Tue, Jan 28, 2014 at 01:39:12AM +0100, Sebastian Hesselbarth wrote:
This patch set is one required step for Dove to hop into
On Wed, 2014-01-29 at 23:05 -0800, dormando wrote:
> We hit the routing code fairly hard. Any hints for what to look at or how
> to instrument it? Or if it's fixed already? It's a real pain to iterate
> since it takes ~30 days to crash, usually. Sometimes.
I really wonder... it looks like a
If we take the false branch of the if quoted in the diff below, we
end up doing a return ret, without ever having initialized it.
Picked up by coverity.
Signed-off-by: Dave Jones
diff --git a/drivers/gpu/drm/radeon/kv_dpm.c b/drivers/gpu/drm/radeon/kv_dpm.c
index b6e01d5d2cce..351db361239d
On Thu, 2014-01-30 at 19:20 -0500, Mikulas Patocka wrote:
>
> On Thu, 30 Jan 2014, James Bottomley wrote:
>
> > On Thu, 2014-01-30 at 18:10 -0500, Mikulas Patocka wrote:
> > >
> > > On Thu, 30 Jan 2014, James Bottomley wrote:
> > >
> > > > Why is this? the whole reason for CONFIG_LBDAF is
On Thu, Jan 30, 2014 at 12:44 PM, Thomas Glanzmann wrote:
> Hello,
> open vswitch git head with Linus tip OOPses for me reproducable when I
> load the following mininet topology:
This looks like the kernel module included with upstream Linux instead
of from OVS git, is that correct?
Can you
On 01/29/2014 10:30 AM, Johannes Weiner wrote:
> On Tue, Jan 28, 2014 at 05:43:54PM -0800, John Stultz wrote:
>> On 01/28/2014 04:03 PM, Johannes Weiner wrote:
>>> On Thu, Jan 02, 2014 at 04:12:08PM +0900, Minchan Kim wrote:
o Syscall interface
>>> Why do we need another syscall for this?
Hi Linus,
This patchset adds more infrastructure for link time optimization
(LTO).
This patchset was pulled into my tree late because of a
miscommunication (part of the patchset was picked up by other
maintainers.) However, the patchset is strictly build-related and
seems to be okay in testing.
On Thu, 30 Jan 2014, David Howells wrote:
> (5) Don't implicitly create a new anonymous keyring and don't implicitly set
> the session keyring to the user-session keyring, but rather just fall
> back
> to using the user-session keyring if there isn't a session keyring.
>
>
> That
On Jan 30, 2014, at 7:44 PM, David Miller wrote:
> From: David Miller
> Date: Thu, 30 Jan 2014 16:29:26 -0800 (PST)
>
>> From: Richard Yao
>> Date: Thu, 30 Jan 2014 13:02:48 -0500
>>
>>> The 9p-virtio transport does zero copy on things larger than 1024 bytes
>>> in size. It accomplishes this
Hi Thomas,
Thanks for your reply.
On Thu, Jan 30, 2014 at 3:27 PM, Thomas Graf wrote:
> On 01/30/14 at 02:05pm, Tom Gundersen wrote:
>> Userspace needs to reliably know the ifindex of the netdevs it creates,
>> as we cannot rely on the ifname staying unchanged.
>>
>> Earlier, a simlpe
On 01/08/2014 06:06 AM, Long Wind wrote:
> On 1/8/14, Long Wind wrote:
>> I have asked Debian users, they don't seem to know
>> kernel 2.4/2.6 fail to boot on my PC
>> probably because it can't detect my memory
>> so I have to tell kernel memory map
>>
>> the following is copied from
On Fri, 2014-01-31 at 01:48 +0100, Antonio Quartulli wrote:
> On 31/01/14 01:33, Zoran Markovic wrote:
> > From: Shaibal Dutta
>
> [...]
>
> > - schedule_delayed_work(_work, delay);
> > + queue_delayed_work(system_power_efficient_wq,
> > + _work, delay);
>
Hi Veaceslav,
Thanks for your quick reply.
On Thu, Jan 30, 2014 at 4:05 PM, Veaceslav Falico wrote:
> On Thu, Jan 30, 2014 at 02:20:02PM +0100, Tom Gundersen wrote:
>>
>> In systemd's networkd and udevd, we would like to give the administrator a
>> simple way to filter net devices by their
kstrimdup creates a whitespace-trimmed duplicate of the passed
in null-terminated string. This is useful for strings coming
from sysfs that often include trailing whitespace due to user
input.
Thanks to Joe Perches for this implementation.
Signed-off-by: Sebastian Capella
Cc: Andrew Morton
Hi Linus,
These are a few changes that arrived a little late but were considered
self-contained enough to still go in for v3.14.
They are all device tree updtes this time around, and mainly for
Broadcom SoCs.
There is one trivial add/add conflict in one of the device tree files.
Please pull,
Patchset related to hibernation resume:
- enhancement to make the use of an existing resume file more general
- add kstrimdup function which trims and duplicates a string
Both patches are based on the 3.13 tag. This was tested on a
Beaglebone black with partial hibernation support, and
Use the name_to_dev_t call to parse the device name echo'd to
to /sys/power/resume. This imitates the method used in hibernate.c
in software_resume, and allows the resume partition to be specified
using other equivalent device formats as well. By allowing
/sys/debug/resume to accept the same
From: Nitin A Kamble
This is pull request with a fix for Kconfig dependency issue. It fixes
a build failure when the kernel configuration option GENERIC_IRQ_CHIP
is enabled without enabling the IRQ_DOMAIN config option in the kernel
configuration.
Thanks,
Nitin
Nitin A Kamble (1):
irq: fix a
From: Nitin A Kamble
The generic_chip.c uses interfaces from irq_domain.c which is controlled by
the IRQ_DOMAIN config option.
Add a select statement in the Kconfig to reflect this requirement.
Without this fix, the generic_chip.c compilation fails like this:
On 31/01/14 01:33, Zoran Markovic wrote:
> From: Shaibal Dutta
[...]
> - schedule_delayed_work(_work, delay);
> + queue_delayed_work(system_power_efficient_wq,
> + _work, delay);
before talking about technical details, here and in other spots of this
On Thu, 30 Jan 2014, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Clean up descriptions of memmap= boot options.
>
> Add periods (full stops), drop commas, change "used" to
> "reserved" or "marked".
>
> Signed-off-by: Randy Dunlap
> Cc: Andiry Xu
> Cc: David Rientjes
Acked-by: David
From: David Miller
Date: Thu, 30 Jan 2014 16:29:26 -0800 (PST)
> From: Richard Yao
> Date: Thu, 30 Jan 2014 13:02:48 -0500
>
>> The 9p-virtio transport does zero copy on things larger than 1024 bytes
>> in size. It accomplishes this by returning the physical addresses of
>> pages to the
Commit-ID: 39424e89d64661faa0a2e00c5ad1e6dbeebfa972
Gitweb: http://git.kernel.org/tip/39424e89d64661faa0a2e00c5ad1e6dbeebfa972
Author: Prarit Bhargava
AuthorDate: Tue, 28 Jan 2014 08:22:11 -0500
Committer: H. Peter Anvin
CommitDate: Thu, 30 Jan 2014 16:40:13 -0800
x86, cpu hotplug:
From: Randy Dunlap
Clean up descriptions of memmap= boot options.
Add periods (full stops), drop commas, change "used" to
"reserved" or "marked".
Signed-off-by: Randy Dunlap
Cc: Andiry Xu
Cc: David Rientjes
---
Documentation/kernel-parameters.txt |8
1 file changed, 4
From: Shaibal Dutta
This patch moves the following work to the power efficient workqueue:
- Transmit work of netpoll
- Destination cache garbage collector work
- Link watch event handler work
In general, assignment of CPUs to pending work could be deferred to
the scheduler in order to
David Howells wrote:
> > > I think this is a pretty strong argument. Counter-arguments, anybody?
> >
> > Yes. CAP_DAC_READ_SEARCH.
>
> No, it would seem unlikely it's that, but I guess there's another capability
> override because the process is owned by root.
CAP_DAC_OVERRIDE, I think.
David Howells wrote:
> > I think this is a pretty strong argument. Counter-arguments, anybody?
>
> Yes. CAP_DAC_READ_SEARCH.
No, it would seem unlikely it's that, but I guess there's another capability
override because the process is owned by root.
David
--
To unsubscribe from this list:
From: Richard Yao
Date: Thu, 30 Jan 2014 13:02:48 -0500
> The 9p-virtio transport does zero copy on things larger than 1024 bytes
> in size. It accomplishes this by returning the physical addresses of
> pages to the virtio-pci device. At present, the translation is usually a
> bit shift.
>
>
From: Tom Gundersen
Date: Thu, 30 Jan 2014 14:20:02 +0100
> In systemd's networkd and udevd, we would like to give the administrator a
> simple way to filter net devices by their DEVTYPE [0][1]. Other software
> such as ConnMan and NetworkManager uses a similar filtering already.
>
> Currently,
On Thu, Jan 30 2014, Michal Hocko wrote:
> On Wed 29-01-14 11:08:46, Greg Thelen wrote:
> [...]
>> The series looks useful. We (Google) have been using something similar.
>> In practice such a low_limit (or memory guarantee), doesn't nest very
>> well.
>>
>> Example:
>> - parent_memcg: limit
Linus Torvalds wrote:
> I think this is a pretty strong argument. Counter-arguments, anybody?
Yes. CAP_DAC_READ_SEARCH.
David
--
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
On Thu, 30 Jan 2014, James Bottomley wrote:
> On Thu, 2014-01-30 at 18:10 -0500, Mikulas Patocka wrote:
> >
> > On Thu, 30 Jan 2014, James Bottomley wrote:
> >
> > > Why is this? the whole reason for CONFIG_LBDAF is supposed to be to
> > > allow 64 bit offsets for block devices on 32 bit.
Further:
[root@andromeda ~]# touch /tmp/foo
[root@andromeda ~]# chmod 0444 /tmp/foo
[root@andromeda ~]# ls -l /tmp/foo
-r--r--r--. 1 root root 0 Jan 31 00:17 /tmp/foo
[root@andromeda ~]# echo hello >/tmp/foo
[root@andromeda ~]# ls -l /tmp/foo
On Thu, 30 Jan 2014, Linus Torvalds wrote:
> On Wed, Jan 29, 2014 at 11:54 PM, Christoph Hellwig
> wrote:
> >
> > For ->set_acl that's fairly easily doable and I actually had a version
> > doing that to be able to convert 9p. But for ->get_acl the path walking
> > caller didn't seem easily
> @@ -1335,7 +1335,6 @@ config ARCH_SPARSEMEM_ENABLE
>
> config ARCH_SPARSEMEM_DEFAULT
> def_bool y
> - depends on X86_64
Is that really needed? Why does the vdso need sparsemem?
>
> static inline void __user *arch_compat_alloc_user_space(long len)
> {
> +#ifdef CONFIG_X86_32
>
Eric W. Biederman wrote:
> These files have been read-only since this code was merged in 2002.
> Over a decade of not being used seems like a strong indication that no
> one cares about the write path.
Actually, things aren't as simple as they seem. Without the patch applied:
Hi Linus,
Various build-related minor bits.
Most of this is work by David Woodhouse to be able to compile the
early boot code with clang/llvm; we have also managed to push an
actual -m16 option into gcc 4.9 so this makes us use that option if
available instead of hacking it.
The balance is a
On Wed, Jan 29, 2014 at 5:32 AM, Maxime Ripard
wrote:
> On Wed, Jan 29, 2014 at 12:25:20PM +, Mark Brown wrote:
>> On Wed, Jan 29, 2014 at 12:10:48PM +0100, Maxime Ripard wrote:
>>
>> > +config SPI_SUN6I
>> > + tristate "Allwinner A31 SPI controller"
>> > + depends on ARCH_SUNXI ||
> -Original Message-
> From: Clemens Ladisch [mailto:clem...@ladisch.de]
> Sent: Wednesday, January 29, 2014 2:31 AM
> To: Network Nut
> Cc: linux-kernel@vger.kernel.org
> Subject: RE: WaitForMultipleObjects/etc. In Kernel
>
> Network Nut wrote:
> >I was looking at POSIX because it allows
On 01/30/2014 03:43 PM, Andiry Xu wrote:
> On Thu, Jan 30, 2014 at 2:54 PM, Randy Dunlap wrote:
>> On 01/30/2014 02:17 PM, David Rientjes wrote:
>>> On Thu, 30 Jan 2014, Randy Dunlap wrote:
>>>
>>> Hi,
>>>
>>> In kernel-parameters.txt, there is following description:
>>>
>>>
On Thu, Jan 30, 2014 at 2:54 PM, Randy Dunlap wrote:
> On 01/30/2014 02:17 PM, David Rientjes wrote:
>> On Thu, 30 Jan 2014, Randy Dunlap wrote:
>>
>> Hi,
>>
>> In kernel-parameters.txt, there is following description:
>>
>> memmap=nn[KMG]$ss[KMG]
>>
From: Shaibal Dutta
Garbage collector work does not have to be bound to the CPU that scheduled
it. By moving work to the power-efficient workqueue, the selection of
CPU executing the work is left to the scheduler. This extends idle
residency times and conserves power.
This functionality is
On Thu, 2014-01-30 at 18:10 -0500, Mikulas Patocka wrote:
>
> On Thu, 30 Jan 2014, James Bottomley wrote:
>
> > Why is this? the whole reason for CONFIG_LBDAF is supposed to be to
> > allow 64 bit offsets for block devices on 32 bit. It sounds like
> > there's somewhere not using sector_t ...
On Thu, 30 Jan 2014, Nishanth Aravamudan wrote:
> In the presence of memoryless nodes, numa_node_id() will return the
> current CPU's NUMA node, but that may not be where we expect to allocate
> from memory from. Instead, we should rely on the fallback code in the
> memory allocator itself, by
On Thu, 30 Jan 2014 11:40:44 +
Roger Pau Monné wrote:
> On 30/01/14 00:15, Mukesh Rathor wrote:
> > Konrad,
> >
> > The CR4 settings were dropped from my earlier patch because you
> > didn't wanna enable them. But since you do now, we need to set them
> > in the APs also. If you decide not
Sorry for replying so late...
On Wed, Jan 29, 2014 at 11:38:47AM +0100, Nicolas Dichtel wrote:
> Le 29/01/2014 07:41, Sohny Thomas a écrit :
> >Resending this on netdev mailing list:
> >Default route for link local address is configured automatically if
> >NETWORKING_IPV6=yes is in ifcfg-eth*.
>
On Thu, 30 Jan 2014, James Bottomley wrote:
> Why is this? the whole reason for CONFIG_LBDAF is supposed to be to
> allow 64 bit offsets for block devices on 32 bit. It sounds like
> there's somewhere not using sector_t ... or using it wrongly which needs
> fixing.
The page cache uses
From: Shaibal Dutta
For better use of CPU idle time, allow the scheduler to select the CPU
on which the timeout work of regulatory settings would be executed.
This extends CPU idle residency time and saves power.
This functionality is enabled when CONFIG_WQ_POWER_EFFICIENT is selected.
Cc:
On 30.01.2014 [14:47:05 -0800], David Rientjes wrote:
> On Wed, 29 Jan 2014, Eric Dumazet wrote:
>
> > > Eric, did you try this when writing 207205a2ba26 ("kthread: NUMA aware
> > > kthread_create_on_node()") or was it always numa_node_id() from the
> > > beginning?
> >
> > Hmm, I think I did
On Tue, 28 Jan 2014, Prarit Bhargava wrote:
> Further discussion here:
> http://marc.info/?l=linux-kernel=139073901101034=2
>
> kbuild, 0day kernel build service, outputs the warning:
>
> arch/x86/kernel/irq.c:333:1: warning: the frame size of 2056 bytes
> is larger than 2048 bytes
On Thu, 30 Jan 2014, David Woodhouse wrote:
> Commit dd78b97367bd575918204cc89107c1479d3fc1a7 ("x86, boot: Move CPU
> flags out of cpucheck") introduced ambiguous inline asm in the
> has_eflag() function. In 16-bit mode want the instruction to be
> 'pushfl', but we just say 'pushf' and hope the
On 01/30/2014 02:17 PM, David Rientjes wrote:
> On Thu, 30 Jan 2014, Randy Dunlap wrote:
>
> Hi,
>
> In kernel-parameters.txt, there is following description:
>
> memmap=nn[KMG]$ss[KMG]
> [KNL,ACPI] Mark specific memory as reserved.
>
On Thu, 2014-01-30 at 15:40 -0500, Mikulas Patocka wrote:
> When running the LVM2 testsuite on 32-bit kernel, there are unkillable
> processes stuck in the kernel consuming 100% CPU:
> blkid R running 0 2005 1409 0x0004
> ce009d00 0082 ffcf c11280ba 0060 560b5dfd
On Wed, 29 Jan 2014, Eric Dumazet wrote:
> > Eric, did you try this when writing 207205a2ba26 ("kthread: NUMA aware
> > kthread_create_on_node()") or was it always numa_node_id() from the
> > beginning?
>
> Hmm, I think I did not try this, its absolutely possible NUMA_NO_NODE
> was better
1 - 100 of 1022 matches
Mail list logo
