Quoting Tushar Behera (2013-04-02 01:20:40)
> In legacy setup, sclk_mmc{0,1,2,3} used PRE_RATIO bit-field (8-bit wide)
> instead of RATIO bit-field (4-bit wide) for dividing clock rate.
>
> With current common clock setup, we are using RATIO bit-field which
> is creating FIFO read errors while acc
On Thu, Apr 04, 2013 at 03:28:13PM -0500, Jacob Shin wrote:
> Ah, okay .. here is the fixup:
>
> From 7236287faa1a499686c9aac1d3f3f224516a7bbf Mon Sep 17 00:00:00 2001
> From: Jacob Shin
> Date: Tue, 2 Apr 2013 09:56:56 -0500
> Subject: [PATCH 1/2] cpufreq: ondemand: allow custom powersave_bias_t
On 04/04/2013 03:28 PM, Stephen Warren wrote:
> On 04/03/2013 08:45 AM, Thierry Reding wrote:
>> Move the PCIe driver from arch/arm/mach-tegra into the drivers/pci/host
>> directory. The motivation is to collect various host controller drivers
>> in the same location in order to facilitate refactor
On 04/03/2013 08:45 AM, Thierry Reding wrote:
> Move the PCIe driver from arch/arm/mach-tegra into the drivers/pci/host
> directory. The motivation is to collect various host controller drivers
> in the same location in order to facilitate refactoring.
>
> The Tegra PCIe driver has been largely re
Quoting Peter De Schrijver (2013-04-04 01:20:44)
> On Thu, Apr 04, 2013 at 01:23:05AM +0200, Stephen Warren wrote:
> > On 04/03/2013 12:27 PM, Stephen Warren wrote:
> > > On 04/03/2013 11:52 AM, Stephen Warren wrote:
> > >> On 04/03/2013 08:40 AM, Peter De Schrijver wrote:
> > >>> This is the ninet
On 04/03/2013 01:47 PM, Linus Walleij wrote:
> From: Laurent Meunier
>
> This update adds a debugfs interface to modify a pin configuration
> for a given state in the pinctrl map. This allows to modify the
> configuration for a non-active state, typically sleep state.
> This configuration is not
On Thu, Apr 4, 2013 at 1:33 PM, Bjorn Helgaas wrote:
>> See my last email to Bjorn. Doing this in early-quirks in such a way that we
>> can detect an iommu that has interrupt remapping enabled (so we don't just
>> unilaterally print this quirk all the time) requires that we be able to parse
>> ac
If an attacker targets multiple distinct systems across a wide range
of system owners, instead of landing the exploit against all of them,
they'll get less than 1% of them, and crash all the rest, removing
them (for a while) from the target pool. Without KASLR, they would
have landed 100% of the at
Hi Linus,
Please pull from the git repository at
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
pm+acpi-3.9-rc6
to receive ACPI and power management fixes for v3.9-rc6 with top-most commit
6cb437acd93a01fdbd6bac9c78ac8159c644e576
Merge branch 'acpi-fixes' into fixes
on
On Thu, Apr 4, 2013 at 2:01 PM, H. Peter Anvin wrote:
> What system monitoring? Most systems don't have much...
The security of an unmonitored system is going to be much lower than
of a well-monitored system. That's true independent of whether kASLR
is deployed.
>
> Kees Cook wrote:
>
>>On Th
When CONFIG_XHCI_HCD_DEBUGGING is activated, the XHCI driver can dump
device and input contexts to the console. The endpoint contexts in that
dump are labeled "Endpoint N Context", where N is DCI - 1... this is
very confusing, especially for people who are not that familiar with
the XHCI specificat
On 04/04/2013 22:45, David Woodhouse wrote:
> On Thu, 2013-04-04 at 21:44 +0200, Borislav Petkov wrote:
>>> ahci :00:1f.2: DMA-API: device driver maps memory fromstack
>>> [addr=88040df2da50]
> I fixed this already.
>
> https://git.kernel.org/cgit/linux/kernel/git/jgarzik/libata-dev.git/co
On Thu, Apr 4, 2013 at 1:58 PM, H. Peter Anvin wrote:
> It seems to me that you are assuming that the attacker is targeting a
> specific system, but a bot might as well target 256 different systems and see
> what sticks...
The alarm signal from the ones that don't stick is, in my opinion, the
p
What system monitoring? Most systems don't have much...
Kees Cook wrote:
>On Thu, Apr 4, 2013 at 1:58 PM, H. Peter Anvin wrote:
>> It seems to me that you are assuming that the attacker is targeting a
>specific system, but a bot might as well target 256 different systems
>and see what sticks..
Natural evolution: when the cluster is the computer, kernel panics are
recoverable like segfaults in a multi-process OS.
You have a point and 8 bits isn't perfect, but it's already useful
regardless, in certain scenarios.
On Thu, Apr 4, 2013 at 1:58 PM, H. Peter Anvin wrote:
> It seems to me tha
On Thu, Apr 4, 2013 at 1:58 PM, H. Peter Anvin wrote:
> It seems to me that you are assuming that the attacker is targeting a
> specific system, but a bot might as well target 256 different systems and see
> what sticks...
Certainly, but system monitoring will show 255 crashed machines, which
i
It seems to me that you are assuming that the attacker is targeting a specific
system, but a bot might as well target 256 different systems and see what
sticks...
Kees Cook wrote:
>On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin wrote:
>> On 04/04/2013 01:07 PM, Kees Cook wrote:
>>> However, t
On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin wrote:
> On 04/04/2013 01:07 PM, Kees Cook wrote:
>> However, the benefits of
>> this feature in certain environments exceed the perceived weaknesses[2].
>
> Could you clarify?
I would summarize the discussion of KASLR weaknesses into to two
general
On Tuesday, March 26, 2013 02:34:25 PM Rafael J. Wysocki wrote:
> On Tuesday, March 19, 2013 11:41:01 AM Paul Bolle wrote:
> > Kconfig symbol ACPI_DEBUG_FUNC_TRACE was only used (through its
> > corresponding macro) in drivers/acpi/acpica/acmacros.h. That macro was
> > removed from that header in v
On Thu, Apr 4, 2013 at 1:27 PM, H. Peter Anvin wrote:
> On 04/04/2013 01:23 PM, Julien Tinnes wrote:
>> On Thu, Apr 4, 2013 at 1:19 PM, Julien Tinnes wrote:
>>> On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin wrote:
On 04/04/2013 01:07 PM, Kees Cook wrote:
> However, the benefits of
On Thu, Apr 4, 2013 at 1:21 PM, H. Peter Anvin wrote:
> I have to admit to being somewhat skeptical toward KASLR with only 8
> bits of randomness.
I agree that 8 bits is pretty low and more would be better. However,
even 8 bits provides a < 1% chance that any particular guess will be
correct. C
On Thu, 2013-04-04 at 21:44 +0200, Borislav Petkov wrote:
> > ahci :00:1f.2: DMA-API: device driver maps memory fromstack
> > [addr=88040df2da50]
I fixed this already.
https://git.kernel.org/cgit/linux/kernel/git/jgarzik/libata-dev.git/commit/?h=upstream-fixes&id=8e725c7f8a60feaa88edacd4
On Thu, Apr 04, 2013 at 12:12:05PM -0500, Nathan Zimmer wrote:
> Ok I am cloning the tree now.
> It does look like the patches would conflict.
> I'll run some tests and take a deeper look.
FWIW, I've just pushed there a tentative patch that switches to hopefully
saner locking (head should be at c
On Thu, Apr 4, 2013 at 6:49 PM, Peter Zijlstra wrote:
> On Thu, 2013-04-04 at 15:31 +0200, Daniel Vetter wrote:
>> We've discussed this approach of using (rt-prio, age) instead of just
>> age
>> to determine the the "oldness" of a task for deadlock-breaking with
>> -EAGAIN. The problem is that thr
tty_port_tty_get might return a tty which is NULL. But it is
dereferenced unconditionally in edge_send. Stop dereferencing that by
sending usb_serial_port pointer around.
Signed-off-by: Jiri Slaby
Cc: Johan Hovold
Cc: linux-...@vger.kernel.org
---
drivers/usb/serial/io_ti.c | 9 -
1 fil
On Thu, Apr 4, 2013 at 2:04 PM, Neil Horman wrote:
> On Thu, Apr 04, 2013 at 10:40:07AM -0700, Yinghai Lu wrote:
>> On Thu, Apr 4, 2013 at 10:27 AM, Don Dutile wrote:
>> >> You need to move the quirk to early_quirk to append nointremap to
>> >> avoid extra rebooting.
>> >>
>> > The pci-dev's of a
In pointer_press_speed_show, we do
data_pointer = hid_get_drvdata(hdev);
twice in a row. Remove one of those.
Signed-off-by: Jiri Slaby
Cc: Jiri Kosina
Cc: linux-in...@vger.kernel.org
---
drivers/hid/hid-lenovo-tpkbd.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/hid/hid-len
rc_unregister_device already calls rc_free_device to free the passed
device. But in one of ttusbir's probe fail paths, we call
rc_unregister_device _and_ rc_free_device. This is wrong and results
in a double free.
Instead, set rc to NULL resulting in rc_free_device being a noop.
Signed-off-by: Ji
ret might be uninitialized and is returned that way when kstrdup of
rbd_dev->spec->snap_name fails. Fix it by returning ENOMEM from that
place.
Signed-off-by: Jiri Slaby
---
drivers/block/rbd.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/block/rbd.c b/drivers/b
changed is not initialized in path_power_down_sync, but it is expected
to be false in case no change happened in the loop. So set it to
false.
Signed-off-by: Jiri Slaby
Cc: Jaroslav Kysela
Cc: Takashi Iwai
---
sound/pci/hda/hda_generic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
In build, we open a file, read that but do not close it. Fix that by
sticking fclose at the right place.
Signed-off-by: Jiri Slaby
Cc: "H. Peter Anvin"
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: x...@kernel.org
---
arch/x86/boot/tools/build.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/a
> I have not tested it yet, but I am pretty sure it won't work. It
> looks like the patch changes the BLKRRPART path to go ahead and remove
> existing partitions when GENHD_FL_NO_PARTSCAN is set. loop doesn't
> issue the BLKRRPART ioctl when !LO_FLAGS_PARTSCAN so this won't help.
> I think loop
On Thu, Apr 04, 2013 at 09:23:23PM +0200, Borislav Petkov wrote:
> On Thu, Apr 04, 2013 at 11:19:04AM -0500, Jacob Shin wrote:
> > Future AMD processors, starting with Family 16h, can provide software
> > with feedback on how the workload may respond to frequency change --
> > memory-bound workload
On 04/04/2013 01:23 PM, Julien Tinnes wrote:
> On Thu, Apr 4, 2013 at 1:19 PM, Julien Tinnes wrote:
>> On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin wrote:
>>> On 04/04/2013 01:07 PM, Kees Cook wrote:
However, the benefits of
this feature in certain environments exceed the perceived we
On Thu, Apr 04, 2013 at 09:12:25PM +0200, Borislav Petkov wrote:
> On Thu, Apr 04, 2013 at 12:18:04PM -0500, Jacob Shin wrote:
> > @@ -574,6 +577,45 @@ static struct common_dbs_data od_dbs_cdata = {
> > .exit = od_exit,
> > };
> >
> > +static void od_set_powersave_bias(unsigned int powersave
On 03/10/2013 03:25 AM, Pekka Enberg wrote:
>
> What is preventing us from making the 64-bit variant also work in flat
> mode to make the code consistent and not hiding the differences under
> the rug? What am I missing here?
>
There is no such thing as "flat mode" in 64-bit mode. We use a #PF
On 29-03-2013 10:26, Zhang Rui wrote:
this is the preparation work to build all the thermal core framework
source file, like governors, cpu cooling, etc, into one module.
No functional change in this patch.
Signed-off-by: Zhang Rui
Durga and me have already reviewed and acked this patch. Can
On Thu, Apr 4, 2013 at 11:35 AM, Tejun Heo wrote:
>
> It'd be nice if the error message can be stored somewhere and then
> printed out after the system is in proper address mode if that isn't
> too complex to achieve. If it gets too messy, no need to bother.
Maybe not necessary. As later during
On Thu, Apr 4, 2013 at 1:19 PM, Julien Tinnes wrote:
> On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin wrote:
>> On 04/04/2013 01:07 PM, Kees Cook wrote:
>>> However, the benefits of
>>> this feature in certain environments exceed the perceived weaknesses[2].
>>
>> Could you clarify?
>
> I think p
I have to admit to being somewhat skeptical toward KASLR with only 8
bits of randomness. There are at least two potential ways of
dramatically increasing the available randomness:
1. actually compose the kernel of multiple independently relocatable
pieces (maybe chunk it on 2M boundaries or so
On 04-04-2013 13:12, R, Durgadoss wrote:
-Original Message-
From: Eduardo Valentin [mailto:eduardo.valen...@ti.com]
Sent: Thursday, April 04, 2013 3:43 AM
To: Zhang, Rui
Cc: linux...@vger.kernel.org; linux-kernel@vger.kernel.org; R, Durgadoss;
Eduardo Valentin
Subject: [PATCHv2 1/3] therm
On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin wrote:
> On 04/04/2013 01:07 PM, Kees Cook wrote:
>> However, the benefits of
>> this feature in certain environments exceed the perceived weaknesses[2].
>
> Could you clarify?
I think privilege reduction in general, and sandboxing in particular,
can
On 04/04/2013 01:07 PM, Kees Cook wrote:
> However, the benefits of
> this feature in certain environments exceed the perceived weaknesses[2].
Could you clarify?
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.ke
On Thursday, April 04, 2013 12:26:52 PM Bjorn Helgaas wrote:
> On Mon, Jan 28, 2013 at 9:34 PM, Huang Ying wrote:
> > [PATCH 1/4] PCI/ACPI: Add target state as parameter to
> > pci_platform_pm_ops->run_wake
> > [PATCH 2/4] PCI: Rename pci_dev->runtime_d3cold to pci_dev->set_d3cold
> > [PATCH 3/4]
On Thu, 4 Apr 2013, Gilad Ben-Yossef wrote:
> Here is the last version I posted over a year ago. You were CCed and
> provided very useful feedback:
>
> http://lkml.indiana.edu/hypermail/linux/kernel/1205.0/01291.html
Ah. yes I remember now.
> Based on your feedback I re-spun them but never gotte
This creates CONFIG_RANDOMIZE_BASE, so that the base offset of the kernel
can be randomized at boot.
This makes kernel vulnerabilities harder to reliably exploit, especially
from remote attacks and local processes in seccomp containers. Keeping
the location of kernel addresses secret becomes very
This provides routines for selecting a randomized kernel base offset,
bounded by e820 details. It tries to use RDRAND and falls back to
RDTSC. If "noaslr" is on the kernel command line, no offset will be used.
Heavily based on work by Dan Rosenberg and Neill Clift.
Signed-off-by: Kees Cook
Cc: E
Hello,
This patch series implements per-boot kernel base offset ASLR. It is based
on work by Dan Rosenberg, Neill Clift, Michael Davidson, and myself. Since
Dan's original thread[1], this code has been improved to work on 64-bit,
among other things.
This is presently in use at Google, and is bein
Add logic for 64-bit kernel relocations. Since there is no need to
handle 32 and 64 bit at the same time, refactor away most of the 32/64
bit ELF differences and split the build into producing two separate
binaries. Additionally switches to using realloc instead of a two-pass
approach.
Heavily bas
On Thu, Apr 04, 2013 at 10:40:07AM -0700, Yinghai Lu wrote:
> On Thu, Apr 4, 2013 at 10:27 AM, Don Dutile wrote:
> >> You need to move the quirk to early_quirk to append nointremap to
> >> avoid extra rebooting.
> >>
> > The pci-dev's of all the (minimally, root, 5500-chipset) pci-dev's are
> > kn
On Thu, Apr 4, 2013 at 11:27 AM, Tejun Heo wrote:
>> for (no = 0; no < ACPI_OVERRIDE_TABLES; no++) {
>> + /*
>> + * have to use unsigned long, otherwise 32bit spit warning
>> + * and it is ok to unsigned long, as bootloader would not
>> + *
On Thu, Apr 04, 2013 at 12:41:27PM -0600, Bjorn Helgaas wrote:
> On Thu, Apr 4, 2013 at 11:51 AM, Neil Horman wrote:
>
> > Oh, you want the bug report that I'm fixing this against? Sure, I can do
> > that.
> > I thought you wanted me to include a url in the WARN_TAINT, with which user
> > could
On 4/4/2013 9:07 PM, Borislav Petkov wrote:
On Thu, Apr 04, 2013 at 08:05:46PM +0200, Steffen Persvold wrote:
It made more sense (to me) to skip the creation of MC4 all together
if you can't find the matching northbridge since you can't reliably
do the dec_and_test() reference counting on the sh
On Mon, Apr 1, 2013 at 4:53 PM, Kees Cook wrote:
> On Mon, Mar 18, 2013 at 7:50 AM, Nicolas Schichan
> wrote:
>> Architecture must select HAVE_SECCOMP_FILTER_JIT and implement
>> seccomp_jit_compile() and seccomp_jit_free() if they intend to support
>> jitted seccomp filters.
>>
>> struct seccom
Hi,
[ Sorry for dropping LKML on my previous email. It was caused by
replying from my smartphone. Adding everyone back now ]
On Thu, Apr 4, 2013 at 9:23 PM, Christoph Lameter wrote:
>
> On Thu, 4 Apr 2013, Gilad Ben-Yossef wrote:
>
> > The vmstat work item leaving a timer running on the CPU, per
+ linux-ide.
On Thu, Apr 04, 2013 at 09:23:27PM +0200, Eric Valette wrote:
> Hi,
>
> When booting a brand new machine freshly installed I notice in the
> dmesg output always the same worrying trace:
>
> PS copy me I'm not subscribed.
>
>
> ata2.00: ATA-9: Samsung SSD 840 Series, DXT07B0Q, max
On 04/04/2013 02:10 AM, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/net/wireless/rtlwifi/rtl8188ee/built-in.o: In function
`.rtl92c_phy_ap_calibrate':
(.text+0x21d14): multiple definition of `.rtl92c_ph
On Thursday 04 April 2013, Felipe Balbi wrote:
> On Thu, Apr 04, 2013 at 01:42:18PM -0400, Alan Stern wrote:
> > > > diff --git a/drivers/usb/misc/sisusbvga/Kconfig
> > > > b/drivers/usb/misc/sisusbvga/Kconfig
> > > > index 30ea7ca..0d03a52 100644
> > > > --- a/drivers/usb/misc/sisusbvga/Kconfig
>
On Thu, Apr 4, 2013 at 11:30 AM, Tejun Heo wrote:
> Also the comment contradicts with what you wrote in the next patch.
>
> Boot loader could load initrd above max_low_pfn.
It does not contradict:
this patch: bootloader would not load initrd above 4G for 32bit kernel
max_low_pfn is below 4G.
When rtsx_pci_acquire_irq fails in rtsx_pci_probe, we forget to
disable an MSI (if we enabled it). This results in this warning on the
next attempt to load the module:
WARNING: at drivers/pci/msi.c:834 pci_enable_msi_block+0x2a4/0x2b0()
Hardware name: HP EliteBook 840 G1
Modules linked in: rtsx_pci
Hi,
When booting a brand new machine freshly installed I notice in the dmesg
output always the same worrying trace:
PS copy me I'm not subscribed.
ata2.00: ATA-9: Samsung SSD 840 Series, DXT07B0Q, max UDMA/133
ata2.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[
On Thu, Apr 4, 2013 at 11:07 AM, Tejun Heo wrote:
>>
>> Also move down two functions declaration to avoid #ifdef in setup.c
>>
>> ACPI_INITRD_TABLE_OVERRIDE depends one ACPI and BLK_DEV_INITRD.
>> So could move declaration out from #ifdef CONFIG_ACPI protection.
>
> Heh, I couldn't really follow t
On Thu, Apr 04, 2013 at 11:19:04AM -0500, Jacob Shin wrote:
> Future AMD processors, starting with Family 16h, can provide software
> with feedback on how the workload may respond to frequency change --
> memory-bound workloads will not benefit from higher frequency, where
> as compute-bound worklo
On 4/4/2013 6:13 PM, Borislav Petkov wrote:
> On Thu, Apr 04, 2013 at 11:52:00PM +0800, Daniel J Blueman wrote:
>> On platforms where all Northbridges may not be visible (due to routing, eg on
>> NumaConnect systems), prevent oopsing due to stale pointer access when
>> offlining cores.
>>
>> Signed
It's all ifdefed out (on BYPASS_SUPPORT), severely bitrotten (try
to remove the ifdef and watch what happens on attempt to build) and, AFAICS,
it's a duplicate of the stuff in bp_mod.c.
Is there any reason to keep it around? IOW, how about
git rm drivers/staging/silicom/bp_proc.c
On Thu, Apr 04, 2013 at 12:18:04PM -0500, Jacob Shin wrote:
> @@ -574,6 +577,45 @@ static struct common_dbs_data od_dbs_cdata = {
> .exit = od_exit,
> };
>
> +static void od_set_powersave_bias(unsigned int powersave_bias)
> +{
> + struct cpufreq_policy *policy;
> + struct dbs_data
On Thu, Apr 4, 2013 at 12:01 PM, Hugh Dickins wrote:
>
> When Paul reminded us of it yesterday, I came to wonder if actually
> every use of ACCESS_ONCE in the read form should strictly be matched
> by ACCESS_ONCE whenever modifying the location.
>
> My uneducated guess is that strictly it ought to
On Thu, Apr 04, 2013 at 08:05:46PM +0200, Steffen Persvold wrote:
> It made more sense (to me) to skip the creation of MC4 all together
> if you can't find the matching northbridge since you can't reliably
> do the dec_and_test() reference counting on the shared bank when you
> don't have the commo
Viresh noticed when using merge_config.sh that a source softlink
was being created even when he didn't specify the -O option.
The problem arises due to the previous commit 409f117e2d6b
which added the -O option. Basically if -O is not specified,
we still pass '-O=.' to the make command, which then
On Thu, 4 Apr 2013, Linus Torvalds wrote:
> On Thu, Apr 4, 2013 at 11:35 AM, Hugh Dickins wrote:
> >
> > find_vma() can be called by multiple threads with read lock
> > held on mm->mmap_sem and any of them can update mm->mmap_cache.
> > Prevent compiler from re-fetching mm->mmap_cache, because oth
On Thu, Apr 04, 2013 at 02:17:09PM +0800, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Fix to return a negative error code from the error handling
> case instead of 0, as returned elsewhere in this function.
We used to have an err = -ENOMEM; "just in case"...
How about this instead:
diff --git a
On 04/04/13 00:22, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130403:
>
on x86_64, when CONFIG_BUG is not enabled:
CC [M] drivers/usb/gadget/configfs.o
drivers/usb/gadget/configfs.c: In function 'config_usb_cfg_unlink':
drivers/usb/gadget/configfs.c:442:2: error: implicit declara
On Thu, Apr 4, 2013 at 11:35 AM, Hugh Dickins wrote:
>
> find_vma() can be called by multiple threads with read lock
> held on mm->mmap_sem and any of them can update mm->mmap_cache.
> Prevent compiler from re-fetching mm->mmap_cache, because other
> readers could update it in the meantime:
Ack.
On Thu, Apr 4, 2013 at 11:51 AM, Neil Horman wrote:
> Oh, you want the bug report that I'm fixing this against? Sure, I can do
> that.
> I thought you wanted me to include a url in the WARN_TAINT, with which user
> could report occurances of this bug. Yeah, the bug that this is reported in
>
From: Jan Stancek
find_vma() can be called by multiple threads with read lock
held on mm->mmap_sem and any of them can update mm->mmap_cache.
Prevent compiler from re-fetching mm->mmap_cache, because other
readers could update it in the meantime:
thread 1
Hello,
On Sat, Mar 09, 2013 at 10:44:34PM -0800, Yinghai Lu wrote:
> For finding with 32bit, it would be easy to access initrd in 32bit
> flat mode, as we don't need to set page table.
>
> That is from head_32.S, and microcode updating already use this trick.
>
> Need to change acpi_initrd_overr
On Thu, Apr 04, 2013 at 11:27:42AM -0700, Tejun Heo wrote:
> > + /*
> > +* have to use unsigned long, otherwise 32bit spit warning
> > +* and it is ok to unsigned long, as bootloader would not
> > +* load initrd above 4G for 32bit kernel.
> > +
On Sat, Mar 09, 2013 at 10:44:33PM -0800, Yinghai Lu wrote:
> In 32bit we will find table with phys address during 32bit flat mode
> in head_32.S, because at that time we don't need set page table to
> access initrd.
>
> For copying we could use early_ioremap() with phys directly before mem mappin
On Mon, Jan 28, 2013 at 9:34 PM, Huang Ying wrote:
> [PATCH 1/4] PCI/ACPI: Add target state as parameter to
> pci_platform_pm_ops->run_wake
> [PATCH 2/4] PCI: Rename pci_dev->runtime_d3cold to pci_dev->set_d3cold
> [PATCH 3/4] PCI/PM: Set pci_dev->set_d3cold in pci_set_power_state
> [PATCH 4/4] P
Thank you.
Gwendal.
On Wed, Apr 3, 2013 at 4:49 PM, Jeff Garzik wrote:
> On 03/29/2013 01:56 AM, Gwendal Grignou wrote:
>>
>> commit 84a9a8cd9d0aa93c17e5815ab8a9cc4c0a765c63 changed the sense key
>> used for returning task registers, but HDIO_DRIVE_CMD ioctl was
>> not changed accordingly.
>>
>>
Hello everyone,
We are researchers from Simon Fraser Unviversity (Canada) and CNRS/INP
Grenoble/Universite Joseph Fourier (France). We are working on memory
traffic management for NUMA multicore architectures. We published a
paper at ASPLOS (http://asplos13.rice.edu/) on that subject and we
think
It seems that nohz still has no effect.
3.9-rc5 + patches. Affinity of init set to 0,1 so no
tasks are running on 9. The "latencytest" used here is part of my
lldiag-0.15 toolkit.
First test without any special kernel parameters. nohz off right?
$ nice -5 taskset -c 9 latencytest
CPUs: Freq=2.9
On Thu, Apr 4, 2013 at 10:36 AM, Tejun Heo wrote:
> Hello,
>
> On Sat, Mar 09, 2013 at 10:44:30PM -0800, Yinghai Lu wrote:
>> Now we have arch_pfn_mapped array, and max_low_pfn_mapped should not
>> be used anymore.
>>
>> User should use arch_pfn_mapped or just 1UL<<(32-PAGE_SHIFT) instead.
>>
>> O
On 04/04/2013 03:05 AM, Prashant Gaikwad wrote:
> Use common of_clk_init() function for clocks initialization.
>
> Signed-off-by: Prashant Gaikwad
> ---
>
> Stephen, if T114 clock series is not going to make in 3.10 then I would
> like Mike to take this patch. If T114 clock series makes it then
On 04/04/2013 03:05 AM, Prashant Gaikwad wrote:
> Register cdev1 and cdev2 peripheral clocks.
Can you please explain the relationship between the following clocks:
cdev1
extern1
clk_out1
The latter two clocks already exist in this driver. I think that
clk_out1 is meant to represent cdev1 already
Il 22/03/2013 23:30, Paolo Bonzini ha scritto:
> Il 20/02/2013 17:12, Paolo Bonzini ha scritto:
>> Il 06/02/2013 16:15, Paolo Bonzini ha scritto:
>>> This series regards the whitelist that is used for the SG_IO ioctl. This
>>> whitelist has three problems:
>>>
>>> * the bitmap of allowed commands
On Thu, Mar 7, 2013 at 7:35 PM, Andrew Cooks wrote:
> This patch creates a quirk to allow the Intel IOMMU to be enabled for devices
> that use incorrect tags during DMA. It is similar to the quirk for Ricoh
> devices, but allows mapping multiple functions and mapping of 'ghost'
> functions that do
On 04/04/2013 03:05 AM, Prashant Gaikwad wrote:
> Correct IDs for cdev1 and cdev2 are 94 and 93 respectively.
This looks OK, but needs to be split up before I can apply it.
The binding change and driver changes will be applied to Tegra's
for-3.10/clk branch, since that's where clk changes are goi
From: Linus Torvalds
Date: Thu, 4 Apr 2013 11:03:28 -0700
> [ Fixed odd legacy subject line that has nothing to do with the actual bug ]
>
> Hmm. Can you double-check and verify that reverting that commit makes
> things work again for you?
>
> Also, what's your distribution and setup? I'd like
On Sat, Mar 09, 2013 at 10:44:32PM -0800, Yinghai Lu wrote:
> To parse srat early, we need to move acpi table probing early.
> acpi_initrd_table_override is before acpi table probing. So we need to
> move it early too.
>
> Current code acpi_initrd_table_override is after init_mem_mapping and
> rel
On Thu, Mar 21, 2013 at 6:51 PM, Robert Hancock wrote:
> On 03/20/2013 10:35 PM, Myron Stowe wrote:
>>
>> Sysfs includes entries to memory regions that back a PCI device's BARs.
>> The pci-sysfs entries backing I/O Port BARs can be accessed by userspace,
>> providing direct access to the device's
[ Fixed odd legacy subject line that has nothing to do with the actual bug ]
Hmm. Can you double-check and verify that reverting that commit makes
things work again for you?
Also, what's your distribution and setup? I'd like this to get
verified, just to see that it's not some timing-dependent th
On Thu, Apr 4, 2013 at 10:50 AM, Tejun Heo wrote:
> On Sat, Mar 09, 2013 at 10:44:31PM -0800, Yinghai Lu wrote:
>> @@ -648,14 +647,14 @@ void __init acpi_initrd_override(void *data, size_t
>> size)
>> memblock_reserve(acpi_tables_addr, acpi_tables_addr + all_tables_size);
>> arch_res
Hi,
On Thu, Apr 04, 2013 at 01:42:18PM -0400, Alan Stern wrote:
> > > diff --git a/drivers/usb/misc/sisusbvga/Kconfig
> > > b/drivers/usb/misc/sisusbvga/Kconfig
> > > index 30ea7ca..0d03a52 100644
> > > --- a/drivers/usb/misc/sisusbvga/Kconfig
> > > +++ b/drivers/usb/misc/sisusbvga/Kconfig
> > >
On 04/04/2013 07:01 AM, Venu Byravarasu wrote:
>> -Original Message-
>> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
>> Sent: Thursday, April 04, 2013 12:47 AM
>> To: Venu Byravarasu
>> Cc: gre...@linuxfoundation.org; ba...@ti.com;
>> st...@rowland.harvard.edu; linux-te...@vger.kerne
Due to the __weak annotation in the forward declaration
of the 'pcibios_get_phb_of_node' function GCC will emit
a weak symbol for this functions even if the actual
implementation does not use the weak attribute.
If an architecture tries to override the function
by providing its own implementation
The of_node field of the device assigned to a
PCI bus is used during scanning of the PCI bus.
However on MIPS, the of_node field is assigned
only after the bus has been scanned.
Implement the architecture specific version of
'pcibios_get_phb_of_node'. Which ensures that the
PCI driver core will in
On Thu, Apr 4, 2013 at 10:48 AM, Tejun Heo wrote:
> On Sat, Mar 09, 2013 at 10:44:29PM -0800, Yinghai Lu wrote:
>> Use common get_ramdisk_image() to get ramdisk start phys address.
>>
>> We need this to get correct ramdisk adress for 64bit bzImage that
>> initrd can be loaded above 4G by kexec-too
On 04/04/2013 11:48 AM, Peter De Schrijver wrote:
> The device tree binding models Tegra114 CAR (Clock And Reset) as a single
> monolithic clock provider.
>
> --
>
> Mike,
>
> This is a small binding doc update only. Hence I didn't make an entire new
> patch series, but just an updated version o
Hi Mike,
> Quoting Stephen Warren (2013-02-19 10:39:35)
> > On 02/15/2013 05:36 AM, Peter De Schrijver wrote:
> > > This is the seventh version of the Tegra114 clockframework. It is based
> > > on the
> > > for-next branch of
> > > git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra
201 - 300 of 709 matches
Mail list logo
