On Fri, 2013-08-02 at 17:14 +0800, Tang Chen wrote:
> This patch introduce early_acpi_firmware_srat() to find the
> phys addr of SRAT provided by firmware. And call it in
> find_hotpluggable_memory().
>
> Since we have initialized acpi_gbl_root_table_list earlier,
> and store all the tables' phys
On Tue, 2013-08-06 at 18:08 -0500, Scott Wood wrote:
> Here's another example. get_lppaca() will only build on book3s -- and
> yet we get requests for e500 code to use this file.
Indeed, Besides there is already accessors afaik for lppaca that compile
to nothing on E (and if not they would be
On 08/05/2013 12:37 PM, Alex Williamson wrote:
> The PCI spec indicates that with stable power, reset needs to be
> asserted for a minimum of 1ms (Trst). Seems like we should be able
> to assume power is stable for a runtime secondary bus reset. The
> current code has always used 100ms with no
Hi all,
The dmi_list array is initialized using gnu designated initializers, and
therefore
contains fewer explicitly defined entries as there are elements in it. This
is because the enum above with M_blabla constants contains more items than the
designated
initializer. Those elements not
On Tue, 2013-08-06 at 16:05 -0700, H. Peter Anvin wrote:
> On 08/06/2013 02:55 PM, Anders Larsen wrote:
> > On 2013-08-06 23:23, H. Peter Anvin wrote:
> >> On 08/06/2013 02:11 PM, Bjorn Helgaas wrote:
> >> >>
> >> >> The above link is also a good example of subtleness: + in a URL
> >> means a
> >>
2013/8/6, Jaegeuk Kim :
> Hi, Namjae,
Hi Jaeguek.
>
> I found and fixed a bug as follows.
>
> In f2fs_put_super, we should call kobject_del & kobject_put.
> And, IMO, we'd better give -EINVAL instead of -EFAULT to users when
> there is no background gc thread.
Yes, Agree. Sorry to bother.
>
> If
On Wed, 2013-07-31 at 08:29 +0530, Deepthi Dharwar wrote:
> /*
> - * pseries_idle_probe()
> + * powerpc_idle_probe()
> * Choose state table for shared versus dedicated partition
> */
> -static int pseries_idle_probe(void)
> +static int powerpc_idle_probe(void)
> {
>
> +#ifndef PPC_POWERNV
On Sun, Aug 4, 2013 at 11:21 PM, Tony Lindgren wrote:
> * Christian Daudt [130802 16:13]:
>> On Fri, Aug 2, 2013 at 1:33 AM, Tony Lindgren wrote:
>> > * Jason Cooper [130731 07:25]:
>> >> So, I'd like to propose we discuss some lessons learned and maybe arrive
>> >> at some best practices.
On 08/06/2013 02:55 PM, Anders Larsen wrote:
> On 2013-08-06 23:23, H. Peter Anvin wrote:
>> On 08/06/2013 02:11 PM, Bjorn Helgaas wrote:
>> >>
>> >> The above link is also a good example of subtleness: + in a URL
>> means a
>> >> space character, it has to be escaped as %2B. Particularly a
>>
On Fri, 2013-08-02 at 17:14 +0800, Tang Chen wrote:
> In acpi_initrd_override(), it checks several things to ensure the
> table it found is valid. In later patches, we need to do these check
> somewhere else. So this patch introduces a common function
> acpi_verify_initrd() to do all these checks,
On Fri, Aug 2, 2013 at 10:24 PM, Olof Johansson wrote:
> On Fri, Aug 2, 2013 at 4:06 PM, Christian Daudt wrote:
>> On Fri, Aug 2, 2013 at 1:33 AM, Tony Lindgren wrote:
>>> * Jason Cooper [130731 07:25]:
So, I'd like to propose we discuss some lessons learned and maybe arrive
at some
On Wed, 2013-08-07 at 00:29 +0200, Rafael J. Wysocki wrote:
> On Tuesday, August 06, 2013 03:15:36 PM Toshi Kani wrote:
> > On Tue, 2013-08-06 at 02:22 +0200, Rafael J. Wysocki wrote:
> > > Hi All,
> > >
> > > The following 5 patches clean up a little mess in acpi_bind_one() and
> > >
Simple driver to enable control of the fan in ASUS laptops. So far this
has only been tested in ASUS Zenbook Prime UX31A, but according to some
online reference [1], it should work in other models as well.
Another source was a patch acpi4asus-user's mailing list [2].
[1]
From: Rafael J. Wysocki
In theory, under a given ACPI namespace node there should be only
one child device object with _ADR whose value matches a given bus
address exactly. In practice, however, there are systems in which
multiple child device objects under a given parent have _ADR matching
[ My apologies for the double send, I screwed up one of the recipient
addresses the first time around and it got dropped by some MTAs. ]
Changes in version 3:
o Lazily remove inodes without shadow entries from the global list to
reduce modifications of said list to an absolute minimum.
In order to make informed placement and reclaim decisions, the page
cache allocation requires the shadow information of refaulting pages.
Every site that does a find_or_create()-style page cache allocation is
converted to pass the shadow page found in the faulting slot of the
radix tree to
Reclaim will be leaving shadow entries in the page cache radix tree
upon evicting the real page. As those pages are found from the LRU,
an iput() can lead to the inode being freed concurrently. At this
point, reclaim must no longer install shadow pages because the inode
freeing code needs to
Provide a function that does not just delete an entry at a given
index, but also allows passing in an expected item. Delete only if
that item is still located at the specified index.
This is handy when lockless tree traversals want to delete entries as
well because they don't have to do an
Subsequent patches need a rough estimate of memory available for page
cache.
Signed-off-by: Johannes Weiner
---
include/linux/writeback.h | 1 +
mm/page-writeback.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/linux/writeback.h b/include/linux/writeback.h
The VM maintains cached filesystem pages on two types of lists. One
list holds the pages recently faulted into the cache, the other list
holds pages that have been referenced repeatedly on that first list.
The idea is to prefer reclaiming young pages over those that have
shown to benefit from
The radix tree hole searching code is only used for page cache, for
example the readahead code trying to get a a picture of the area
surrounding a fault.
It sufficed to rely on the radix tree definition of holes, which is
"empty tree slot". But this is about to change, though, as shadow
page
Previously, page cache radix tree nodes were freed after reclaim
emptied out their page pointers. But now reclaim stores shadow
entries in their place, which are only reclaimed when the inodes
themselves are reclaimed. This is problematic for bigger files that
are still in use after they have a
shmem mappings already contain exceptional entries where swap slot
information is remembered.
To be able to store eviction information for regular page cache,
prepare every site dealing with the radix trees directly to handle
entries other than pages.
The common lookup functions will filter out
Page cache radix tree slots are usually stabilized by the page lock,
but shmem's swap cookies have no such thing. Because the overall
truncation loop is lockless, the swap entry is currently confirmed by
a tree lookup and then deleted by another tree lookup under the same
tree lock region.
Use
On Monday, August 05, 2013 09:29:19 AM Kevin Hilman wrote:
> The SmartReflex AVS driver evolved out of the OMAP kernel and now
> lives under drivers/power/avs.
>
> I've historically been maintainer of this but Nishanth Menon is doing
> most of the heavy lifting now. Add us both as
On Tue, 2013-08-06 at 14:16 -0700, Andrew Morton wrote:
> On Mon, 5 Aug 2013 22:21:08 -0700 Davidlohr Bueso wrote:
>
> > This patchset teaches the kernel about hybrid master boot records (MBRs),
> > one of
> > the most common issues with GUID partition tables, as a workaround to layout
> >
On Tue, Aug 6, 2013 at 3:25 PM, Casey Schaufler wrote:
> On 8/5/2013 11:30 PM, Kees Cook wrote:
>> On Thu, Jul 25, 2013 at 11:52 PM, Casey Schaufler
>> wrote:
>>> The /proc/*/attr interfaces are given to one LSM. This can be
>>> done by setting CONFIG_SECURITY_PRESENT. Additional interfaces
>>>
On Tuesday, August 06, 2013 04:40:12 PM Ralf Baechle wrote:
> On Mon, Aug 05, 2013 at 09:27:12PM +0300, Aaro Koskinen wrote:
>
> > Commit 42913c799 (MIPS: Loongson2: Use clk API instead of direct
> > dereferences) broke the cpufreq functionality on Loongson2 boards:
> > clk_set_rate() is called
On 08/06/2013 04:28 PM, Rafael J. Wysocki wrote:
> On Tuesday, August 06, 2013 09:38:36 PM Shuah Khan wrote:
>> On 08/06/2013 03:22 PM, Alan Stern wrote:
>>> On Tue, 6 Aug 2013, Shuah Khan wrote:
>>>
With the dev_pm_ops model, drivers have to provide interfaces for each
one of these
On Tuesday, August 06, 2013 09:38:36 PM Shuah Khan wrote:
> On 08/06/2013 03:22 PM, Alan Stern wrote:
> > On Tue, 6 Aug 2013, Shuah Khan wrote:
> >
> >> With the dev_pm_ops model, drivers have to provide interfaces for each
> >> one of these states.
> >
> > No, they don't. They can leave out
On 07/20/2013 09:26 AM, Qiaowei Ren wrote:
>
> /* now map TXT heap */
> - heap_base = ioremap(*(u64 *)(config + TXTCR_HEAP_BASE),
> - *(u64 *)(config + TXTCR_HEAP_SIZE));
> + heap_base = ioremap(readl(config + TXTCR_HEAP_BASE),
> +
On 8/5/2013 11:30 PM, Kees Cook wrote:
> On Thu, Jul 25, 2013 at 11:52 PM, Casey Schaufler
> wrote:
>> The /proc/*/attr interfaces are given to one LSM. This can be
>> done by setting CONFIG_SECURITY_PRESENT. Additional interfaces
>> have been created in /proc/*/attr so that each LSM has its own
On Tue, 6 Aug 2013 17:40:40 +0900 Joonsoo Kim wrote:
> If we use a division operation, we can compute a batch count more closed
> to ideal value. With this value, we can finish our job within
> MIGRATE_PCPTYPES iteration. In addition, batching to free more pages
> may be helpful to cache usage.
On Tuesday 06 of August 2013 15:09:46 Doug Anderson wrote:
> Tomasz,
>
> On Tue, Aug 6, 2013 at 2:58 PM, Tomasz Figa
wrote:
> >> +static int dw_mci_exynos_resume_noirq(struct device *dev)
> >> +{
> >> + struct dw_mci *host = dev_get_drvdata(dev);
> >> + u32 clksel;
> >> +
> >> +
On Tuesday, August 06, 2013 03:15:36 PM Toshi Kani wrote:
> On Tue, 2013-08-06 at 02:22 +0200, Rafael J. Wysocki wrote:
> > Hi All,
> >
> > The following 5 patches clean up a little mess in acpi_bind_one() and
> > acpi_unbind_one(). They are on top of current linux-next plus the patch
> > at
Andrew Morton writes:
> On Tue, 06 Aug 2013 15:29:42 +0800 Chen Gang wrote:
>
>> Improve the usage of return value 'result', so not only can make code
>> clearer to readers, but also can improve the performance.
>
> It used to be pervasive kernel style do to
>
> ret = -ENOMEM;
> foo
On Tue, 2013-08-06 at 14:43 -0700, Andrew Morton wrote:
> On Tue, 06 Aug 2013 15:29:42 +0800 Chen Gang wrote:
>
> > Improve the usage of return value 'result', so not only can make code
> > clearer to readers, but also can improve the performance.
>
> It used to be pervasive kernel style do to
Tomasz,
On Tue, Aug 6, 2013 at 2:58 PM, Tomasz Figa wrote:
>> +static int dw_mci_exynos_resume_noirq(struct device *dev)
>> +{
>> + struct dw_mci *host = dev_get_drvdata(dev);
>> + u32 clksel;
>> +
>> + clksel = mci_readl(host, CLKSEL);
>> + if (clksel & SDMMC_CLKSEL_WAKEUP_INT)
On Tue, Aug 06, 2013 at 05:00:51PM -0500, Aravind Gopalakrishnan wrote:
> Quick question: Shall I change all instances of
> boot_cpu_data.[x86|x86_model] to use pvt->fam and pvt->model wherever
> applicable as part of this patch or have it go in as a separate patch?
Yes, a separate pre-patch
On 2013-08-06 23:23, H. Peter Anvin wrote:
On 08/06/2013 02:11 PM, Bjorn Helgaas wrote:
>>
>> The above link is also a good example of subtleness: + in a URL
means a
>> space character, it has to be escaped as %2B. Particularly a
problem in
>> gmail message-ids.
the link in question
On Tuesday 06 of August 2013 14:37:51 Doug Anderson wrote:
> The TMOUT register is initted to 0x at probe time but isn't
> initted after suspend/resume. Add an init of this value.
>
> No problems were observed without this (it will also get initted in
> __dw_mci_start_request if there is
On Tuesday 06 of August 2013 14:37:50 Doug Anderson wrote:
> After suspend/resume all of the dw_mmc registers are reset to
> defaults. We restore most of them, but specifically don't setup the
> clock registers after resume unless we've got a powered card. Things
> still work because the core
On 8/6/2013 3:55 PM, Aravind Gopalakrishnan wrote:
On 8/6/2013 3:23 PM, Borislav Petkov wrote:
On Fri, Aug 02, 2013 at 05:43:04PM -0500, Aravind Gopalakrishnan wrote:
Adding support for handling ECC error decoding for new F15 models.
On newer models, support has been included for upto 4 DCT's,
On Tuesday 06 of August 2013 14:37:48 Doug Anderson wrote:
> The dw_mmc driver keeps a cache of the current slot->clock in order to
> avoid doing a whole lot of work every time set_ios() is called.
> However, after suspend/resume the register values are bogus so we need
> to ensure that the cached
Hi Doug,
See my comment inline.
On Tuesday 06 of August 2013 14:37:49 Doug Anderson wrote:
> If the WAKEUP_INT is asserted at wakeup and not cleared, we'll end up
> looping around forever. This has been seen to happen on exynos5420
> silicon despite the fact that we haven't enabled any wakeup
On Tue, Aug 06, 2013 at 11:52:35PM +0200, Paul Bolle wrote:
> On Tue, 2013-08-06 at 14:36 -0700, Jon Mason wrote:
> > GCC v4.6.3 complains:
> > drivers/dma/ioat/dma_v3.c: In function ‘__ioat3_prep_pq16_lock’:
> > drivers/dma/ioat/dma_v3.c:264:11: warning: array subscript is below array
> > bounds
D: 22471 Comm: trinity-child36 Tainted: G W
3.11.0-rc4-next-20130806-sasha-2-gb144a3f #3977
[ 542.187428] task: 88020bc4 ti: 8801b6e7e000 task.ti:
8801b6e7e000
[ 542.188384] RIP: 0010:[] []
lookup_ioctx+0x8d/0xe0
[ 542.189408] RSP: 0018:8801b6e7ff18 EFLAGS:
On 08/03/2013 07:17 PM, Kirill A. Shutemov wrote:
> If a huge page is only partly in the range we zero out the part,
> exactly like we do for partial small pages.
What's the logic behind this behaviour? Seems like the kind of place
that we would really want to be splitting pages.
> + if
On Tue, 2013-08-06 at 14:36 -0700, Jon Mason wrote:
> GCC v4.6.3 complains:
> drivers/dma/ioat/dma_v3.c: In function ‘__ioat3_prep_pq16_lock’:
> drivers/dma/ioat/dma_v3.c:264:11: warning: array subscript is below array
> bounds [-Warray-bounds]
> drivers/dma/ioat/dma_v3.c:264:11: warning: array
Commit-ID: 1599e8fc84dd9c2954df0d4b2db52f7f6719f339
Gitweb: http://git.kernel.org/tip/1599e8fc84dd9c2954df0d4b2db52f7f6719f339
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:35 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:18:08 -0700
x86: Fix sys_call_table
Commit-ID: 04bb591ca74fb8ea06d5ab7fadfb7bf5b11fb28e
Gitweb: http://git.kernel.org/tip/04bb591ca74fb8ea06d5ab7fadfb7bf5b11fb28e
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:41 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:19:48 -0700
x86, asmlinkage: Make
Commit-ID: b6c035d04e80b4244a143e34e51c84cf2181bd94
Gitweb: http://git.kernel.org/tip/b6c035d04e80b4244a143e34e51c84cf2181bd94
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:48 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:21:01 -0700
x86, asmlinkage: Make
Chen Gang writes:
Have you tested this code? Do you have anything that actually the
uses sysctl binary interface?
If you do have code that actually uses this interface please fix it not
to use it. This code is fundamentally a stop gap measure and will
bit-rot in time and then we will remove
This series of patches addresses some suspend/resume problems with
dw_mmc on exynos platforms, espeically exynos5420. Since
suspend/resume is not fully working on ToT Linux (v3.11-rc4) on
exynos5250-snow, this series was tested against the current ToT
ChromeOS 3.8 tree. I have confirmed basic
Commit-ID: d6efc2f7240b4e55590df69d74f33fdb72ce934a
Gitweb: http://git.kernel.org/tip/d6efc2f7240b4e55590df69d74f33fdb72ce934a
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:49 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:21:03 -0700
x86, asmlinkage, power:
Commit-ID: 28596b6a8779b736829ad837f95fdc2e81bdd1ee
Gitweb: http://git.kernel.org/tip/28596b6a8779b736829ad837f95fdc2e81bdd1ee
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:50 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:21:08 -0700
x86, asmlinkage, vdso: Mark
Commit-ID: ff49103fdba59aa3f845ad2dcac0c26a9e4c5404
Gitweb: http://git.kernel.org/tip/ff49103fdba59aa3f845ad2dcac0c26a9e4c5404
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:40 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:18:33 -0700
x86, asmlinkage: Make
Commit-ID: 4a335c0695074c1fd2ede7f919b0064f53d35c3f
Gitweb: http://git.kernel.org/tip/4a335c0695074c1fd2ede7f919b0064f53d35c3f
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:47 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:20:59 -0700
x86, asmlinkage: Make 64bit
Commit-ID: 35ea7903b8a97162e38da9da3b560df74713321d
Gitweb: http://git.kernel.org/tip/35ea7903b8a97162e38da9da3b560df74713321d
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:39 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:18:30 -0700
x86, asmlinkage: Make
Commit-ID: 9a55fdbe941e5cfb7a5c438db890a58dad82ef8e
Gitweb: http://git.kernel.org/tip/9a55fdbe941e5cfb7a5c438db890a58dad82ef8e
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:46 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:20:56 -0700
x86, asmlinkage, paravirt:
On Tue, 06 Aug 2013 15:29:42 +0800 Chen Gang wrote:
> Improve the usage of return value 'result', so not only can make code
> clearer to readers, but also can improve the performance.
It used to be pervasive kernel style do to
ret = -ENOMEM;
foo = alloc(...);
if (!foo)
Commit-ID: e0e745e45d3d3c22f60dc9b2c17bcfc0d9f2bc82
Gitweb: http://git.kernel.org/tip/e0e745e45d3d3c22f60dc9b2c17bcfc0d9f2bc82
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:44 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:20:18 -0700
x86, asmlinkage: Make
Commit-ID: 277d5b40b7bf495d2d4193746181b17dd98441b2
Gitweb: http://git.kernel.org/tip/277d5b40b7bf495d2d4193746181b17dd98441b2
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:43 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:20:13 -0700
x86, asmlinkage: Make
Commit-ID: 54c2f3fdb941204cad136024c7b854b7ad112ab6
Gitweb: http://git.kernel.org/tip/54c2f3fdb941204cad136024c7b854b7ad112ab6
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:45 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:20:20 -0700
x86, asmlinkage, apm: Make
If the WAKEUP_INT is asserted at wakeup and not cleared, we'll end up
looping around forever. This has been seen to happen on exynos5420
silicon despite the fact that we haven't enabled any wakeup events due
to a silicon errata. It is safe to do on all exynos variants.
Signed-off-by: Doug
Commit-ID: a1ed4ddfb780910c1bb1e9df9cfc87454b607489
Gitweb: http://git.kernel.org/tip/a1ed4ddfb780910c1bb1e9df9cfc87454b607489
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:38 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:18:26 -0700
x86, asmlinkage: Make
Commit-ID: 1d9090e2fb32c84277cef6e72a21be7f78c929f4
Gitweb: http://git.kernel.org/tip/1d9090e2fb32c84277cef6e72a21be7f78c929f4
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:37 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:18:23 -0700
x86, asmlinkage: Make all
Commit-ID: 9e1a431de08e2a49ca8dab0edc813c8cb96ba369
Gitweb: http://git.kernel.org/tip/9e1a431de08e2a49ca8dab0edc813c8cb96ba369
Author: Andi Kleen
AuthorDate: Mon, 5 Aug 2013 15:02:36 -0700
Committer: H. Peter Anvin
CommitDate: Tue, 6 Aug 2013 14:18:17 -0700
x86, asmlinkage: Change
It appears that gcc may put some code in ".text.unlikely" or
".text.hot" sections. Right now those aren't accounted for in unwind
tables. Add them.
I found some docs about this at:
http://gcc.gnu.org/onlinedocs/gcc-4.6.2/gcc.pdf
Without this, if you have slub_debug turned on, you can get
On 08/06/2013 03:22 PM, Alan Stern wrote:
> On Tue, 6 Aug 2013, Shuah Khan wrote:
>
>> With the dev_pm_ops model, drivers have to provide interfaces for each
>> one of these states.
>
> No, they don't. They can leave out interfaces if they want.
Yes. Agreed. There is no need to provide each and
The TMOUT register is initted to 0x at probe time but isn't
initted after suspend/resume. Add an init of this value.
No problems were observed without this (it will also get initted in
__dw_mci_start_request if there is data to send), but it makes the
register dump before and after
The dw_mmc driver keeps a cache of the current slot->clock in order to
avoid doing a whole lot of work every time set_ios() is called.
However, after suspend/resume the register values are bogus so we need
to ensure that the cached value is invalidated.
In many cases we got by without this since
After suspend/resume all of the dw_mmc registers are reset to
defaults. We restore most of them, but specifically don't setup the
clock registers after resume unless we've got a powered card. Things
still work because the core will eventually call set_ios() and we'll
set things up.
There
Seungwon,
On Wed, Jul 31, 2013 at 9:18 AM, Doug Anderson wrote:
> Seungwon,
>
> On Mon, Jul 15, 2013 at 5:09 AM, Seungwon Jeon wrote:
>> Sorry for late response.
>> Yes, it's not clear.
>> If you get the confirmation, could you share this problem?
>> Possibly, auto-clear may not be implemented.
GCC v4.6.3 complains:
drivers/dma/ioat/dma_v3.c: In function ‘__ioat3_prep_pq16_lock’:
drivers/dma/ioat/dma_v3.c:264:11: warning: array subscript is below array
bounds [-Warray-bounds]
drivers/dma/ioat/dma_v3.c:264:11: warning: array subscript is below array
bounds [-Warray-bounds]
This is due
Commit a5463cd3 "ARM: make vectors page inaccessible from userspace"
introduced a typo making arch_vma_name() always return "[vectors]".
Fix up that regression (of the hush-hush security fix).
Signed-off-by: Mathias Krause
---
arch/arm/kernel/process.c |2 +-
1 file changed, 1 insertion(+),
Seungwon Jeon,
On Mon, Jul 15, 2013 at 5:09 AM, Seungwon Jeon wrote:
> On Thu, July 11, 2013, Doug Anderson wrote:
>> On some devices (like exynos5420) the dw_mmc controller may be in a
>> strange state after we wake up from sleep. Add callbacks to allow for
>> dealing with these quirks. We
Hi,
While debugging upowerd (with Logitech Unifying receiver via hidraw),
I came across this list corruption warning. It probably has something
to do with me removing the receiver and re-inserting it while the file
descriptor to /dev/hidraw0 was still open. journalctl excerpt is on the
bottom of
On 08/06/2013 02:07 PM, H. Peter Anvin wrote:
>
> I'm getting massive conflicts on this patch, so I do need to understand
> better what is your baseline, and yes, it probably would be useful to
> split it up.
>
My fault, core dumped.
Please ignore.
-hpa
--
To unsubscribe from this
On 08/06/2013 02:11 PM, Bjorn Helgaas wrote:
>>
>> The above link is also a good example of subtleness: + in a URL means a
>> space character, it has to be escaped as %2B. Particularly a problem in
>> gmail message-ids.
>
> Ooh, thanks. I wasn't aware of that, and I've certainly constructed
>
On Tue, 6 Aug 2013, Shuah Khan wrote:
> With the dev_pm_ops model, drivers have to provide interfaces for each
> one of these states.
No, they don't. They can leave out interfaces if they want.
> In this case, there will be a conflict since
> pm_op() treats this state as freeze where as the
On Tue, 2013-08-06 at 02:22 +0200, Rafael J. Wysocki wrote:
> Hi All,
>
> The following 5 patches clean up a little mess in acpi_bind_one() and
> acpi_unbind_one(). They are on top of current linux-next plus the patch
> at https://patchwork.kernel.org/patch/2839101/ .
>
> [1/5] Move duplicated
On Mon, 5 Aug 2013 22:21:08 -0700 Davidlohr Bueso wrote:
> This patchset teaches the kernel about hybrid master boot records (MBRs), one
> of
> the most common issues with GUID partition tables, as a workaround to layout
> disk partitions to be compatible with both EFI and legacy MBR based
On 08/06/2013 02:11 PM, Bjorn Helgaas wrote:
>
> I don't know what it would take to implement this. Escaping special
> characters makes it not quite as trivial as I thought it might be.
>
It depends mostly on what machinery is available on vger.
-hpa
--
To unsubscribe from this
In param_get_byte(), to which the macro STANDARD_PARAM_DEF(byte, ...) expands,
"%c" is used to print an unsigned char. So it gets printed as a character what
is not intended here. Use "%hhu" instead.
Signed-off-by: Christoph Jaeger
---
kernel/params.c | 2 +-
1 file changed, 1 insertion(+), 1
From: Philip J Kelleher
The rsxx driver was not checking the correct value during a
pci_map_page failure for PowerPC. Fixing this also uncovered a
double free if the bio was returned before it was broken up
into indiviadual 4k dmas, that is also fixed here.
Signed-off-by: Philip J Kelleher
Being affected by this bug, I can confirm that Linux 3.11-rc4 still
exhibits the unwanted behaviour for me, but that commenting out the
single line from the second patch makes it work.
Thus, for requesting a revert on that line, you are most welcome to put
me down as a "Tested-By".
Best regards,
Hi Zach,
I like the idea behind these clean ups. Thanks for working on them!
On Fri, Aug 02, 2013 at 04:21:40PM -0700, Zach Levis wrote:
> This v3 is based off Oleg's changes from "exec: more cleanups" and
> "exec: minor cleanups + minor fix"
I would echo all of Oleg's comments on the series so
From: Philip J Kelleher
The rsxx driver is returning the wrong values during
copy_from_user and copy_to_user. It, also, is not
setting ENOMEM during a failed workqueue allocation.
Signed-off-by: Philip J Kelleher
---
[+cc vger postmaster]
On Fri, Aug 2, 2013 at 3:38 PM, H. Peter Anvin wrote:
> On 08/02/2013 02:36 PM, Shuah Khan wrote:
>> On Fri, Aug 2, 2013 at 3:04 PM, Bjorn Helgaas wrote:
>>> vger already adds a "to unsubscribe from this list" footer to messages
>>> to LKML and other lists. What if it
From: Philip J Kelleher
The rsxx driver was not releasing the IDA entry during
driver unload. This would be a big problem on a DLPAR
remove where the card is remove from the LPAR but the
driver is still loaded. This patch fixes that issue.
Signed-off-by: Philip J Kelleher
From: Philip J Kelleher
Changed the device name to IBM Flash Adapter 90 (PCIe2 0.9TB).
Signed-off-by: Philip J Kelleher
---
diff -uprN -X linux-block-vanilla/Documentation/dontdiff
On 08/05/2013 03:02 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> These handlers are all referenced from assembler stubs, so need
> to be visible.
>
> The handlers without arguments become asmlinkage, the others __visible
> to not force regparms(0) on x86-32.
>
> I put it all into a single
On 08/06/2013 04:40 AM, Raghavendra K T wrote:
> This series replaces the existing paravirtualized spinlock mechanism
> with a paravirtualized ticketlock mechanism. The series provides
> implementation for both Xen and KVM.
>
> The current set of patches are for Xen/x86 spinlock/KVM guest side,
On Tue, 6 Aug 2013 12:06:56 +0800 Jianguo Wu wrote:
> If node == NUMA_NO_NODE, pol is NULL, we should return NULL instead of
> do "if (!pol->mode)" check.
>
> Signed-off-by: Jianguo Wu
> ---
> mm/mempolicy.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/mempolicy.c
On 8/6/2013 3:17 PM, Borislav Petkov wrote:
On Fri, Aug 02, 2013 at 05:43:02PM -0500, Aravind Gopalakrishnan wrote:
Adding PCI_DEVICE_ID_AMD_15H_NB_M30H_F3 and PCI_DEVICE_ID_AMD_15H_NB_M30H_F4
for F15h model 30h. This is required for the file amd_nb.c
... and amd64_edac.c
Also, remember to
On 8/6/2013 3:19 PM, Borislav Petkov wrote:
On Fri, Aug 02, 2013 at 05:43:03PM -0500, Aravind Gopalakrishnan wrote:
Adding code to check for specific model (F15h, M30h) and if yes,
do not add flag AMD_NB_GART. Also check cpuid_edx(0x8006) for
prescence of L3. If no L3, do not add any L3
Oleg Nesterov writes:
> unshare_userns(new_cred) does *new_cred = prepare_creds() before
> create_user_ns() which can fail. However, the caller expects that
> it doesn't need to take care of new_cred if unshare_userns() fails.
>
> We could change the single caller, sys_unshare(), but I think it
On Tue, Aug 06, 2013 at 01:23:48PM -0700, Dave Hansen wrote:
> On 08/03/2013 07:17 PM, Kirill A. Shutemov wrote:
> > + if (PageTransTailCache(page)) {
> > + /* part of already handled huge page */
> > + if (!page->mapping)
> > +
On 8/6/2013 3:23 PM, Borislav Petkov wrote:
On Fri, Aug 02, 2013 at 05:43:04PM -0500, Aravind Gopalakrishnan wrote:
Adding support for handling ECC error decoding for new F15 models.
On newer models, support has been included for upto 4 DCT's,
however, only DCT0 and DCT3 are currently
101 - 200 of 1196 matches
Mail list logo
