On Thu, Jun 06, 2013 at 11:13:29AM +0800, Jason Wang wrote:
> On 06/05/2013 06:43 PM, Michael S. Tsirkin wrote:
> > On Wed, Jun 05, 2013 at 02:36:30PM +0800, Jason Wang wrote:
> >> Though the queue were in fact created by open(), we still need to add this
> >> check
> >> to be compatible with tunt
Hi
On Tue, 30 Apr 2013, Guennadi Liakhovetski wrote:
> of_parse_phandle_with_args() and of_count_phandle_with_args() functions
> are declared with their first parameter as const. However, their
> respective stubs, used when CONFIG_OF isn't defined, don't have the "const"
> modifier. This patch ad
On 5 June 2013 21:31, Stratos Karafotis wrote:
> Changes since v2:
> - Reorder patches 2/3 and 3/3
> - Fix typos in patch changelog
>
> Changes since v1:
> - Use policy->cpuinfo.max_freq in the calculation formula
> of target frequency instead of policy->max
On Thu, Jun 06, 2013 at 09:33:28AM +0800, Ming Lei wrote:
> On Thu, Jun 6, 2013 at 12:34 AM, Andreas Mohr wrote:
> > Hi,
> >
> > On Wed, Jun 05, 2013 at 09:22:25AM +0800, Ming Lei wrote:
> >> On Wed, Jun 5, 2013 at 2:28 AM, Andreas Mohr wrote:
> >> > Value 8 now managed to reduce powertop wakeu
On 06/06/2013 10:06 AM, Johannes Weiner wrote:
> From: Johannes Weiner
> Subject: [patch] mm: invoke oom-killer from remaining unconverted page fault
> handlers
>
> A few remaining architectures directly kill the page faulting task in
> an out of memory situation. This is usually not a good ide
>>> On 05.06.13 at 21:17, Mukesh Rathor wrote:
> On Wed, 05 Jun 2013 08:03:12 +0100
> "Jan Beulich" wrote:
>
>> >>> On 04.06.13 at 23:53, Mukesh Rathor
>> >>> wrote:
>> > Following OK? :
>> >
>> > if (xen_feature(XENFEAT_auto_translated_physmap)) {
>> > switch_to_new_gd
>>> On 05.06.13 at 19:35, Konrad Rzeszutek Wilk wrote:
>> > Looking at the code, one would expect that the existing check
>>
>> The "expect ..." here doesn't really seem to have a proper
>> termination later in the sentence (or I'm having problems parsing
>> the whole construct), so if I didn't k
On Wed, 2013-06-05 at 07:30 -0600, Bjorn Helgaas wrote:
> On Tue, Jun 4, 2013 at 6:38 PM, Yanmin Zhang
> wrote:
> > On Tue, 2013-06-04 at 12:04 -0600, Bjorn Helgaas wrote:
> >> I'm not sure where we are with this patch. I think Joseph initially
> >> reported a problem (though I haven't actually s
Hi,
On Wed, Jun 5, 2013 at 6:23 PM, Eduardo Valentin
wrote:
> On 04-06-2013 23:20, amit daniel kachhap wrote:
>> Hi Eduardo,
>>
>> On Tue, Jun 4, 2013 at 6:25 PM, Eduardo Valentin
>> wrote:
>>> On 04-06-2013 00:44, amit daniel kachhap wrote:
Hi Jonghwa,
Sorry for the late reply as
Hi all,
After merging the final tree, today's linux-next build (sparc64 defconfig)
failed like this:
drivers/rtc/class.c: In function 'rtc_init':
drivers/rtc/class.c:339:18: error: lvalue required as unary '&' operand
Caused by commit c5a32d622261 ("drivers/rtc/class: convert from Legacy pm
ops
On Wed, Jun 05, 2013 at 11:54:07AM -0400, Jeff Mahoney wrote:
> This fixes the following build failure:
> arch/powerpc/kvm/book3s_xics.c:812: error: implicit declaration of function
> 'get_tb'
>
> Signed-off-by: Jeff Mahoney
Acked-by: Paul Mackerras
Could you please send this to linuxppc-...@
On Thu, Jun 6, 2013 at 6:09 AM, Xiang Wang wrote:
> 2013/6/3 Andy Shevchenko :
>> On Mon, Jun 3, 2013 at 6:22 AM, Xiang Wang wrote:
>>> 2013/5/31 Andy Shevchenko :
On Fri, May 31, 2013 at 11:21 AM, Xiang Wang wrote:
> In some of our drivers (e.g. UART) we may stop a running DMA
> be
On Wed, Jun 05, 2013 at 11:45:59PM +0300, Aldo Iljazi wrote:
> Specifically fixed:
> sync.c:128: WARNING: braces {} are not necessary for single statement blocks
> sync.c:879: WARNING: Prefer seq_puts to seq_printf
> sync.c:883: WARNING: Prefer seq_puts to seq_printf
> sync.c:898: WARNING: Prefer
On 06.06.2013 07:54, Paul Walmsley wrote:
здравствуйте,
On Wed, 5 Jun 2013, Aida Mynzhasova wrote:
Not so long ago I tried to boot Linux 3.10-rc4 kernel on DM816x EVM
board. Unfortunately, my attempts were failed by reason of poor
support of DM81xx-based devices in new kernels.
Yeah, TI pret
From: "Yan, Zheng"
If perf event buffer is in overwrite mode, the kernel only updates
the data head when it overwrites old samples. The program that owns
the buffer need periodically check the buffer and update a variable
that tracks the date tail. If the program fails to do this in time,
the dat
Andy Lutomirski wrote:
> I broke them in this commit:
>
> commit 1be374a0518a288147c6a7398792583200a67261
> Author: Andy Lutomirski
> Date: Wed May 22 14:07:44 2013 -0700
>
> net: Block MSG_CMSG_COMPAT in send(m)msg and recv(m)msg
>
> This patch adds __sys_sendmsg and __
On Wed, 2013-06-05 at 22:25 -0700, Guenter Roeck wrote:
>
>
> Can you point me to some of the breaking code ? I guess it must be in some of
> the pci_dma_dev_setup callbacks, but those I looked at only check devicetree
> data or simply set function pointers, both of which should not be affected b
Replace /include/ by #include for bcm281xx device tree
files, enabling use of the C preprocessor.
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/bcm11351-brt.dts |2 +-
arch/arm/boot/dts/bcm11351.dtsi|2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boo
於 四,2013-06-06 於 13:05 +0800,joeyli 提到:
> 於 三,2013-06-05 於 16:59 +0100,Matt Fleming 提到:
> > On Wed, 05 Jun, at 02:53:27PM, Matthew Garrett wrote:
> > > On Wed, 2013-06-05 at 15:49 +0100, Fleming, Matt wrote:
> > >
> > > > Folks, what do you want me to do with this? Merge it with Matthew's
> > > >
On Thu, 2013-06-06 at 13:05 +0800, joeyli wrote:
> + if (!(attributes & EFI_VARIABLE_NON_VOLATILE))
> + return EFI_OUT_OF_RESOURCES;
I'd move this up to the top of the function, and just return 0 - there's
no risk of the firmware causing problems if it's a volatile
This series follows the same approach as taken on Tegra and
OMAP DT files to use the C preprocessor in order to improve
readability. Since bcm281xx does not yet have gpio and pinctrl
support, this series just enables the C preprocessor and removes
the magic constants from existing irq properties. A
Use the standard interrupt-controller and ARM GIC constants to
improve the readability of bcm281xx DT irq properties.
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/bcm11351.dtsi |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/bcm11351.dtsi b/arc
I broke them in this commit:
commit 1be374a0518a288147c6a7398792583200a67261
Author: Andy Lutomirski
Date: Wed May 22 14:07:44 2013 -0700
net: Block MSG_CMSG_COMPAT in send(m)msg and recv(m)msg
This patch adds __sys_sendmsg and __sys_sendmsg as common helpers that accept
M
Hi all,
Today's linux-next merge of the mvebu tree got a conflict in
arch/arm/Kconfig.debug between commit 284166ffebc3 ("ARM: imx: enable
low-level debug support for imx6sl") from the imx-mxs tree and commit
5be22d8c29fd ("arm: mvebu: add another earlyprintk Kconfig option") from
the mvebu tree.
On Wed, Jun 05, 2013 at 09:10:51PM -0700, David Rientjes wrote:
> On Wed, 5 Jun 2013, Johannes Weiner wrote:
>
> > The memcg OOM handling is incredibly fragile because once a memcg goes
> > OOM, one task (kernel or userspace) is responsible for resolving the
> > situation.
>
> Not sure what this
Add the various binding files for the palmas family of chips. There is a
top level MFD binding then a seperate binding for regulators IP blocks on chips.
Signed-off-by: Graeme Gregory
Signed-off-by: J Keerthy
Signed-off-by: Ian Lartey
Reviewed-by: Stephen Warren
---
Documentation/devicetree/
Hi Linus,
Can you please pull the m68knommu git tree, for-linus branch.
It contains only a single fix for compilation breakage to many of the
ColdFire CPU targets.
Regards
Greg
The following changes since commit e4aa937ec75df0eea0bee03bffa3303ad36c986b:
Linux 3.10-rc3 (2013-05-26 16:00:47
Hi,
this time after I appended the right file.
regression fixers for the big 3:
nouveau: hdmi audio, dac load detect, s/r regressions fixed
radeon: long standing system hang fixed, hdmi audio and rs780 fast fb
fixes
intel: one old regression, a WARN removal, and a stop X dying fix
otherwise one
On Thu, Jun 6, 2013 at 3:22 PM, Linus Torvalds
wrote:
> On Thu, Jun 6, 2013 at 2:14 PM, Dave Airlie wrote:
>>
>> 7 files changed, 32 insertions(+), 42 deletions(-)
>
> That's not at all what I get (including shortlog). I got
>
> 29 files changed, 188 insertions(+), 68 deletions(-)
>
> from a lo
On Thu, Jun 06, 2013 at 11:00:04AM +1000, Benjamin Herrenschmidt wrote:
> On Sat, 2013-06-01 at 06:58 -0700, Guenter Roeck wrote:
> > the comment was actuially directed towards Yuanquan.
> >
> > No problem, take your time. I did my best to test it, but I agree that this
> > is a
> > critical area
On 05/31/2013 12:10 PM, Lee, Chun-Yi wrote:
> There have some situation we unregister whole acpi/video driver by downstream
> driver just want to remove backlight control interface of acpi/video. It caues
> we lost other functions of acpi/video, e.g. transfer acpi event to input
> event.
>
> So,
On Thu, Jun 6, 2013 at 2:14 PM, Dave Airlie wrote:
>
> 7 files changed, 32 insertions(+), 42 deletions(-)
That's not at all what I get (including shortlog). I got
29 files changed, 188 insertions(+), 68 deletions(-)
from a lot of commits you don't list.
Linus
--
To unsubscribe
Hi Linus,
regression fixers for the big 3:
nouveau: hdmi audio, dac load detect, s/r regressions fixed
radeon: long standing system hang fixed, hdmi audio and rs780 fast fb
fixes
intel: one old regression, a WARN removal, and a stop X dying fix
otherwise one mgag200 fix, a couple of arm build f
於 三,2013-06-05 於 16:59 +0100,Matt Fleming 提到:
> On Wed, 05 Jun, at 02:53:27PM, Matthew Garrett wrote:
> > On Wed, 2013-06-05 at 15:49 +0100, Fleming, Matt wrote:
> >
> > > Folks, what do you want me to do with this? Merge it with Matthew's patch?
> >
> > Do that and add Joey's signed-off-by?
>
>
From: Eric Dumazet
Date: Wed, 05 Jun 2013 21:35:25 -0700
> On Thu, 2013-06-06 at 12:56 +1000, Michael Neuling wrote:
>> On Thu, May 23, 2013 at 7:07 AM, Andy Lutomirski wrote:
>> > MSG_CMSG_COMPAT is (AFAIK) not intended to be part of the API --
>> > it's a hack that steals a bit to indicate to
On Thu, 6 Jun 2013, Johannes Weiner wrote:
> From: Johannes Weiner
> Subject: [patch] mm: invoke oom-killer from remaining unconverted page fault
> handlers
>
> A few remaining architectures directly kill the page faulting task in
> an out of memory situation. This is usually not a good idea s
On Thu, Jun 06, 2013 at 08:30:01AM +0530, anish singh wrote:
> Hello Wim Van,
> Can you look into below?
>
Please be patient. Wim tends to be busy.
Guenter
> On Wed, Jun 5, 2013 at 8:39 AM, anish singh
> wrote:
> > Hello Wim Van Sabroeck,
> > Can I get your inputs on this?
> >
> > On Tue, Jun
On Wed, 5 Jun 2013, Johannes Weiner wrote:
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index ff7b40d..d169a8d 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -187,10 +187,6 @@ struct mem_cgroup_per_node {
> struct mem_cgroup_per_zone zoneinfo[MAX_NR_ZONES];
> };
>
> -st
On 06/05/13 17:26, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
on i386: when CONFIG_PCI is
On 5/25/2013 11:09 PM, Prabhakar Lad wrote:
> From: Lad, Prabhakar
>
> remove init_enable from ths7303 pdata as it is being dropped
> from ths7303_platform_data.
>
> Signed-off-by: Lad, Prabhakar
> Cc: Sekhar Nori
> Cc: Hans Verkuil
> Cc: Laurent Pinchart
> Cc: Mauro Carvalho Chehab
> Cc: l
On Wed, Jun 05, 2013 at 08:57:44PM -0700, David Rientjes wrote:
> On Wed, 5 Jun 2013, Johannes Weiner wrote:
>
> > Since '1c0fe6e mm: invoke oom-killer from page fault', page fault
> > handlers should not directly kill faulting tasks in an out of memory
> > condition.
>
> I have no objection to t
On Thu, 2013-06-06 at 12:56 +1000, Michael Neuling wrote:
> On Thu, May 23, 2013 at 7:07 AM, Andy Lutomirski wrote:
> > MSG_CMSG_COMPAT is (AFAIK) not intended to be part of the API --
> > it's a hack that steals a bit to indicate to other networking code
> > that a compat entry was used. So don'
On 06/05/13 17:26, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
on i386 when CONFIG_PM is not
On Wed, 2013-06-05 at 21:25 -0700, gree...@candelatech.com wrote:
> From: Ben Greear
> diff --git a/kernel/softirq.c b/kernel/softirq.c
> index 14d7758..f150ad6 100644
> --- a/kernel/softirq.c
> +++ b/kernel/softirq.c
> @@ -204,6 +204,7 @@ EXPORT_SYMBOL(local_bh_enable_ip);
> * should not be ab
From: Ben Greear
The stop machine logic can lock up if all but one of
the migration threads make it through the disable-irq
step and the one remaining thread gets stuck in
__do_softirq. The reason __do_softirq can hang is
that it has a bail-out based on jiffies timeout, but
in the lockup case, j
On Wed, 5 Jun 2013, Stephen Boyd wrote:
> On 06/04, Nicolas Pitre wrote:
> >
> > The LC0 area should be considered read-only as it may be located in
> > flash.
> >
> > Here's what I came with instead:
> >
> > From: Nicolas Pitre
> > Date: Tue, 4 Jun 2013 17:01:30 -0400
> > Subject: [PATCH] AR
Hi,
also,
On Wed, 5 Jun 2013, Aida Mynzhasova wrote:
> Aida Mynzhasova (5):
> ARM: OMAP: AM33xx: multiple renames for early initialization
If this patch is what's responsible for all the file renaming, please drop
it. Looks from the change summary that it's just useless churn (although
I h
Hi,
On Tue, May 28, 2013 at 2:34 PM, Jingoo Han wrote:
> Add support for EXYNOS4210 that includes USB EHCI/OHCI.
> Previous PHY initialization code is not correct; thus, it is modifed
^ You might
want to say "previous PHY init code does not
On Wed, 5 Jun 2013, Johannes Weiner wrote:
> The memcg OOM handling is incredibly fragile because once a memcg goes
> OOM, one task (kernel or userspace) is responsible for resolving the
> situation.
Not sure what this means. Are you referring to the case where the memcg
is disabled from oom ki
On Wed, 2013-06-05 at 20:50 -0700, Ben Greear wrote:
> On 06/05/2013 08:46 PM, Eric Dumazet wrote:
> >
> > We use in Google a patch triggering warning is a thread holds the cpu
> > without taking care to need_resched() for more than xx ms
>
> Well, I'm sure that patch works nicely until the clock
On Wed, 5 Jun 2013, Johannes Weiner wrote:
> Since '1c0fe6e mm: invoke oom-killer from page fault', page fault
> handlers should not directly kill faulting tasks in an out of memory
> condition.
I have no objection to the patch, but there's no explanation given here
why exiting with a kill shoul
Hi all,
Today's linux-next merge of the kvm tree got a conflict in
arch/s390/include/asm/pgtable.h between commit 338679f7ba4a
("s390/pgtable: Fix guest overindication for change bit") from the s390
tree and commit 0d0dafc1e48f ("s390/kvm: rename RCP_xxx defines to
PGSTE_xxx") from the kvm tree.
здравствуйте,
On Wed, 5 Jun 2013, Aida Mynzhasova wrote:
> Not so long ago I tried to boot Linux 3.10-rc4 kernel on DM816x EVM
> board. Unfortunately, my attempts were failed by reason of poor
> support of DM81xx-based devices in new kernels.
Yeah, TI pretty much gave up on trying to get support
On 06/05/2013 08:46 PM, Eric Dumazet wrote:
On Wed, 2013-06-05 at 20:41 -0700, Ben Greear wrote:
On 06/05/2013 08:26 PM, Eric Dumazet wrote:
On Wed, 2013-06-05 at 20:14 -0700, Tejun Heo wrote:
Ah, so, that's why it's showing up now. We probably have had the same
issue all along but it used
On Wed, May 29, 2013 at 10:37:00PM +0200, Andi Kleen wrote:
> > As Dave said before, is the last path component sufficient? Or how
> > about an inode number?
>
> Neither works, the profiler needs to find the file and read it.
>
> inode searching would be incredible expensive, unless the file sys
On Wed, 2013-06-05 at 20:41 -0700, Ben Greear wrote:
> On 06/05/2013 08:26 PM, Eric Dumazet wrote:
> > On Wed, 2013-06-05 at 20:14 -0700, Tejun Heo wrote:
> >
> >>
> >> Ah, so, that's why it's showing up now. We probably have had the same
> >> issue all along but it used to be masked by the softir
On 06/05/2013 08:26 PM, Eric Dumazet wrote:
On Wed, 2013-06-05 at 20:14 -0700, Tejun Heo wrote:
Ah, so, that's why it's showing up now. We probably have had the same
issue all along but it used to be masked by the softirq limiting. Do
you care to revive the 10 iterations limit so that it's l
Hi Grant,
> -Original Message-
> From: Grant Likely [mailto:glik...@secretlab.ca] On Behalf Of Grant
> Likely
> Sent: Thursday, June 06, 2013 5:32 AM
> To: J, KEERTHY; linux-kernel@vger.kernel.org
> Cc: linux-...@vger.kernel.org; devicetree-disc...@lists.ozlabs.org;
> swar...@wwwdotorg.org
Hi Stephen,
Thanks for the quick review.
> -Original Message-
> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
> Sent: Wednesday, June 05, 2013 10:44 PM
> To: J, KEERTHY
> Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;
> devicetree-disc...@lists.ozlabs.org;
> broo...@op
When we decide not use zero-copy, msg.control should be set to NULL otherwise
macvtap/tap may set zerocopy callbacks which may decrease the kref of ubufs
wrongly.
Bug were introduced by commit cedb9bdce099206290a2bdd02ce47a7b253b6a84
(vhost-net: skip head management if no outstanding).
This solve
Hi Anton,
On Thu, 6 Jun 2013 13:01:05 +1000 Anton Blanchard wrote:
>
> > This is causing a regression on 64bit powerpc with 32bit usermode.
> > When I hit userspace, udev is broken and I suspect all networking is
> > broken as well.
> >
> > Can we please revert 1be374a0518a288147c6a7398792583200
On 06/05/2013 09:44 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 05-06-2013 11:40, Jason Wang wrote:
>
>> When we decide not use zero-copy, msg.control should be set to NULL
>> otherwise
>> macvtap/tap may set zerocopy callbacks which may decrease the kref of
>> ubufs
>> wrongly.
>
>> Bug were introd
On Wed, 2013-06-05 at 20:14 -0700, Tejun Heo wrote:
>
> Ah, so, that's why it's showing up now. We probably have had the same
> issue all along but it used to be masked by the softirq limiting. Do
> you care to revive the 10 iterations limit so that it's limited by
> both the count and timing?
On 06/05/2013 06:59 PM, Michael S. Tsirkin wrote:
> On Wed, Jun 05, 2013 at 02:36:31PM +0800, Jason Wang wrote:
>> This patch adds TUNSETQUEUE ioctl to let userspace can temporarily disable or
>> enable a queue of macvtap. This is used to be compatible at API layer of
>> tuntap
>> to simplify the
Hello, Eric.
On Wed, Jun 05, 2013 at 06:34:52PM -0700, Eric Dumazet wrote:
> > Ingo, Thomas, we're seeing a stop_machine hanging because
> >
> > * All other CPUs entered IRQ disabled stage. Jiffies is not being
> > updated.
> >
> > * The last CPU get caught up executing softirq indefinitely.
On 06/05/2013 06:43 PM, Michael S. Tsirkin wrote:
> On Wed, Jun 05, 2013 at 02:36:30PM +0800, Jason Wang wrote:
>> Though the queue were in fact created by open(), we still need to add this
>> check
>> to be compatible with tuntap which can let mgmt software use a single API to
>> manage queues. T
Since '1c0fe6e mm: invoke oom-killer from page fault', page fault
handlers should not directly kill faulting tasks in an out of memory
condition. Instead, they should be invoking the OOM killer to pick
the right task. Convert the remaining architectures.
Signed-off-by: Johannes Weiner
---
arch
The memcg OOM handling is incredibly fragile because once a memcg goes
OOM, one task (kernel or userspace) is responsible for resolving the
situation. Every other task that gets caught trying to charge memory
gets stuck in a waitqueue while potentially holding various filesystem
and mm locks on wh
2013/6/3 Andy Shevchenko :
> On Mon, Jun 3, 2013 at 6:22 AM, Xiang Wang wrote:
>> 2013/5/31 Andy Shevchenko :
>>> On Fri, May 31, 2013 at 11:21 AM, Xiang Wang wrote:
In some of our drivers (e.g. UART) we may stop a running DMA
before it finishes. So we need to know how many bytes have
>
On 06/05/2013 06:36 PM, Michael S. Tsirkin wrote:
> On Wed, Jun 05, 2013 at 02:36:23PM +0800, Jason Wang wrote:
>> > Hi all:
>> >
>> > This series implements a v3 of fully tuntap compatiable API which could be
>> > used
>> > by userspace to manage multiple macvtap queues. The main parts is to add
Remove struct mem_cgroup_lru_info and fold its single member, the
variably sized nodeinfo[0], directly into struct mem_cgroup. This
should make it more obvious why it has to be the last member there.
Also move the comment that's above that special last member below it,
so it is more visible to so
在 2013-06-06四的 10:24 +0800,Gu Zheng写道:
> On 06/06/2013 09:40 AM, liguang wrote:
>
> > this driver will support cpu phyical add/removal automatically
> > after online/offline. if cpu hotpluged, cpu will not
> > online automatically, and for cpu offline, we try to
> > do actually eject if allowed fo
Hi,
> This is causing a regression on 64bit powerpc with 32bit usermode.
> When I hit userspace, udev is broken and I suspect all networking is
> broken as well.
>
> Can we please revert 1be374a0518a288147c6a7398792583200a67261
> upstream?
>
> Found via bisect.
Doesn't this patch break compat_s
Hello Wim Van,
Can you look into below?
On Wed, Jun 5, 2013 at 8:39 AM, anish singh wrote:
> Hello Wim Van Sabroeck,
> Can I get your inputs on this?
>
> On Tue, Jun 4, 2013 at 8:39 AM, anish singh
> wrote:
>> On Tue, Jun 4, 2013 at 3:55 AM, Guenter Roeck wrote:
>>> On Mon, Jun 03, 2013 at 10:
On Thu, May 23, 2013 at 7:07 AM, Andy Lutomirski wrote:
> MSG_CMSG_COMPAT is (AFAIK) not intended to be part of the API --
> it's a hack that steals a bit to indicate to other networking code
> that a compat entry was used. So don't allow it from a non-compat
> syscall.
Dave & Linus
This is cau
Hi Arnd,
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: 2013年5月31日 19:25
> To: linux-arm-ker...@lists.infradead.org
> Cc: Neil Zhang; haojian.zhu...@gmail.com; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2] ARM: mmp: bring up pxa988 with device tree suppo
v2->v3:
- Remove unused local variables i, node from mls_level_isvalid().
v1->v2:
- Move the new ebitmap comparison logic from mls_level_isvalid()
into the ebitmap_contains() helper function.
- Rerun perf and performance tests on the latest v3.10-rc4 kernel.
While running the high_systime
On Wed, 2013-06-05 at 09:41 -0400, Steven Rostedt wrote:
> >
> > If preempt_enable_notrace() is the only user, why does this live in
> > kernel/context_tracking.c and not in kernel/sched/core.c?
>
> Then we would need to add #ifdef CONFIG_CONTEXT_TRACKING around it too.
> As we have in preempt.h:
Avoid strncpy anti-pattern. Use strdup() instead, as already done for
the logfile optarg.
Signed-off-by: Kees Cook
---
Fix for -mm clean-up-scary-strncpydst-src-strlensrc-uses-fix.patch
---
Documentation/accounting/getdelays.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --
cpuacct causes duplicate accountings on the scheduler and cpu will
provide equivalent stats. Optimizations for cases where cpu and
cpuacct are co-mounted are being worked on but we want to deprecate it
eventually. Let's disallow cpuacct if __DEVEL__sane_behavior.
Signed-off-by: Tejun Heo
Cc: Gl
v2:
re-based on latest tip/master
default_cfs_period(), do_sched_cfs_period_timer(), do_sched_cfs_slack_timer()
already defined previously, no need to declare again.
CC: Ingo Molnar
CC: Peter Zijlstra
Signed-off-by: Michael Wang
---
kernel/sched/fair.c |4
1 files changed, 0
On Thu, Jun 6, 2013 at 11:29 AM, Al Viro wrote:
>
> Probably... procfs symlinks neutering O_DIRECTORY might, in theory, be usable
> to cook something nasty, but I don't see any obvious ways to exploit that.
> FWIW, resulting kernel seems to survive the minimal beating, but obviously
> more is nee
v2:
re-based on latest tip/master
Directly use rq to save some code.
CC: Ingo Molnar
CC: Peter Zijlstra
Signed-off-by: Michael Wang
---
kernel/sched/fair.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 143dcdb
From: Xiang Wang
In mmp pdma, phy channels are allocated/freed dynamically
and frequently. But no proper protection is added.
Conflict will happen when multi-users are requesting phy
channels at the same time. Use spinlock to protect.
Signed-off-by: Xiang Wang
---
drivers/dma/mmp_pdma.c | 42
On Thu, Jun 06, 2013 at 10:38:31AM +0900, Linus Torvalds wrote:
> On Thu, Jun 6, 2013 at 10:20 AM, Al Viro wrote:
> > I'm not sure whether to treat that as a bug or as a weird misfeature
> > enshrined in userland ABI:
> > open("/tmp", O_CREAT, 0) => -EISDIR // LAST_NORM case
>
On 06/06/2013 09:40 AM, liguang wrote:
> this driver will support cpu phyical add/removal automatically
> after online/offline. if cpu hotpluged, cpu will not
> online automatically, and for cpu offline, we try to
> do actually eject if allowed for cpu like
> "echo 1 > /sys/bus/acpi/devices/LNXCPU
From: Xiang Wang
In mmp pdma, phy channels are allocated/freed dynamically.
The mapping from DMA request to DMA channel number in DRCMR
should be cleared when a phy channel is freed. Otherwise
conflicts will happen when:
1. A is using channel 2 and free it after finished, but A
still maps to chan
於 三,2013-06-05 於 16:08 +,Matthew Garrett 提到:
> On Wed, 2013-06-05 at 16:59 +0100, Matt Fleming wrote:
>
> > + /* clean DUMMY object */
> > + efi.set_variable(efi_dummy_name, &EFI_DUMMY_GUID, 0, 0, NULL);
>
> Hm. Actually, is that going to work? From the spec:
>
The patch I tested on OVM
From: Xiang Wang
This patch set deals with the issues that 1) phy channels are not protected
in mmp_pdma. 2) dma request<->channel mapping is not cleared when a phy chan
is freed.
Xiang Wang (2):
dma: mmp_pdma: add protect when alloc/free phy channels
dma: mmp_pdma: clear DRCMR when free a p
On 06/05/2013 07:15 PM, Peter Zijlstra wrote:
> On Tue, Jun 04, 2013 at 02:23:39PM +0800, Michael Wang wrote:
>> Directly use rq to save some code.
>>
>> CC: Ingo Molnar
>> CC: Peter Zijlstra
>> Signed-off-by: Michael Wang
>
> Please send patches against tip/master; the below didn't apply clean
On 06/05/2013 07:06 PM, Peter Zijlstra wrote:
> On Wed, Jun 05, 2013 at 10:24:18AM +0800, Michael Wang wrote:
>> v2:
>> Move comments back before init_tg_cfs_entry(). (Thanks for the notify
>> from pjt)
>>
>> In sched_init(), there is no need to initialize 'root_task_group.shares' and
>> 'roo
于 2013年06月06日 05:08, Brian Norris 写道:
> Note that a 2-jiffy timeout does not, in fact, totally resolve my
> problems; with a timeout of 2 jiffies, I still get a timeout that
> (according to getnstimeofday()) occurs after only 56us. It does
since the 2-jiffy does not resolve your problem, i suggest
Hi Andrew,
On Wed, 05 Jun 2013 17:26:36 -0700 a...@linux-foundation.org wrote:
>
> linux-next-git-rejects.patch
We must figure out why you sometimes get rejects that I do not get when I
import your series into a git tree. However in this case you resolution
is not quite right. It leaves 2 con
Hi guys,
I noticed the following warning in a linux-next build:
fs/ext4/inode.c: In function 'ext4_da_writepages':
fs/ext4/inode.c:2212:6: warning: 'err' may be used uninitialized in this
function [-Wmaybe-uninitialized]
In tracking this down, I followed the call chains and discovered that
io_s
When a PCI host bridge device receives a Bus Check notification, we
must re-enumerate starting with the bridge to discover changes (devices
that have been added or removed).
Prior to 668192b678 ("PCI: acpiphp: Move host bridge hotplug to
pci_root.c"), this happened in _handle_hotplug_event_bridge(
This patch-set try to support physically hot-plug/unplug
a cpu automatically, that is:
if you offline a cpu, it will automatically actually remove
a cpu, and if you hot-plug a cpu, then it will online this
cpu automatically.
so, offline is just like eject, but eject attribute seems not
available si
add a notifier for anyone who are instresting in
ec space changing.
Signed-off-by: liguang
---
drivers/acpi/ec.c| 32
include/linux/acpi.h |2 ++
2 files changed, 34 insertions(+), 0 deletions(-)
diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
index
this driver will support cpu phyical add/removal automatically
after online/offline. if cpu hotpluged, cpu will not
online automatically, and for cpu offline, we try to
do actually eject if allowed for cpu like
"echo 1 > /sys/bus/acpi/devices/LNXCPU\:0X/eject"
this "echo ..." is only present for re
Signed-off-by: liguang
---
drivers/platform/x86/cpu_physic_hotplug.c | 30 ++--
1 files changed, 27 insertions(+), 3 deletions(-)
diff --git a/drivers/platform/x86/cpu_physic_hotplug.c
b/drivers/platform/x86/cpu_physic_hotplug.c
index a52c042..1cdac1b 100644
--- a/driv
Hello, Glauber.
On Wed, May 29, 2013 at 03:03:11PM +0400, Glauber Costa wrote:
> I am *not* going as far as marking cpuacct deprecated, because I think it
> deserves a special discussion (even though my position in this matter is
> widely
> known), but all the infrastructure to make it happen is
1 - 100 of 983 matches
Mail list logo