On Tue, 2 Oct 2012, Glauber Costa wrote:
> #include
>
> +#define SLAB_AVAILABLE_FLAGS 0xUL /* No flag restriction */
> +
> enum stat_item {
I thought the SLAB_AVAILABLE_FLAGS would stand for something meaningful
like the flags supported by an allocator given a kernel config. F.e. SLUB
On Mon, Sep 24, 2012 at 03:34:46PM -0700, Kent Overstreet wrote:
[..]
> diff --git a/include/linux/bio.h b/include/linux/bio.h
> index 4e32be1..d985e90 100644
> --- a/include/linux/bio.h
> +++ b/include/linux/bio.h
> @@ -67,6 +67,7 @@
> #define bio_offset(bio) bio_iovec((bio))->bv_of
I started seeing the following null pointer dereference on
a linux-next sept 21 git and still seeing it on linux-next
Sep 27th git.
Can be reproduced easily. I have been able to reproduce every
time I do a complete build of a kernel on fresh checkout or
touch a header file that forces full build.
On 09/27/2012 05:07 PM, Dan Magenheimer wrote:
> Of course, I'm of the opinion that neither zcache1 nor
> zcache2 would be likely to be promoted for at least another
> cycle or two, so if you go with zcache2+zsmalloc as the compromise
> and it still takes six months for promotion, I hope you don't
Hi Linus,
Please pull these XFS updates for 3.7-rc1. inode32/64 mount options have been
remountable, and there are SEEK_HOLE/SEEK_DATA enhancements. I believe you
have already merged all of the bug fixes.
Thanks,
Ben
The following changes since commit 0d7614f09c1ebdbaa1599a5aba7593f147
I started seeing the following null pointer dereference on
a linux-next sept 21 git and still seeing it on linux-next
Sep 27th git.
Can be reproduced easily. I have been able to reproduce every
time I do a complete build of a kernel on fresh checkout or
touch a header file that forces full build.
On Tue, Oct 2, 2012 at 8:34 PM, Greg KH wrote:
> On Tue, Oct 02, 2012 at 06:00:54PM +0300, Andy Shevchenko wrote:
>> There are several places in kernel that use functionality like shell's
>> basename
>> function. Let's do it common helper for them.
>>
>> Signed-off-by: Andy Shevchenko
>> Cc: YAM
The following changes since commit 979570e02981d4a8fc20b3cc8fd651856c98ee9d:
Linux 3.6-rc7 (2012-09-23 18:10:57 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git tags/spi-3.7
for you to fetch changes up to 536a53a300d0d40152796eefb
On Tue, Oct 02, 2012 at 11:23:46AM +0100, Dave Martin wrote:
> > Well, no, it boots ELFs, so it can boot anything, with any memory
> > layout. A 2nd stage loader would be required to boot standard kernels,
> > that loader would be an ELF with 1 section for the 2nd stage, 1
> > section for the zIma
On 10/02/12 02:13, Will Deacon wrote:
>
> Thanks Stephen. I've also got some patches for OS save/restore of the debug
> registers using the various hardware locking and readout mechanisms, so that
> debug state can be persisted across low-power states.
>
> Do any of the Qualcomm chips (v7 as oppose
On Tue, Oct 02, 2012 at 05:59:11PM +0100, Will Deacon wrote:
> On x86 memory accesses to pages without the ACCESSED flag set result in the
> ACCESSED flag being set automatically. With the ARM architecture a page access
> fault is raised instead (and it will continue to be raised until the ACCESSED
Properly account for I/O in transit before returning from the RESET call.
In the absense of this patch, we could have a situation where the host may
respond to a command that was issued prior to the issuance of the RESET
command at some arbitrary time after responding to the RESET command.
Currentl
> The generic code wouldn't know about any user pointers inside
> attributes, so it'd have to be downstream consumers. Hopefully there
> won't be many attributes with user pointers in them (I don't expect
> there to be), so we won't have too much of this messyness.
I really don't like this. We sh
Kent Overstreet writes:
> So, I and other people keep running into things where we really need to
> add an interface to pass some auxiliary... stuff along with a pread() or
> pwrite().
>
> A few examples:
>
> * IO scheduler hints. Some userspace program wants to, per IO, specify
> either prioriti
On 9/28/2012 8:16 PM, John Stultz wrote:
There is two rough approaches that I have tried so far
1) Managing volatile range objects, in a tree or list, which are then
purged using a shrinker
2) Page based management, where pages marked volatile are moved to
a new LRU list and are purged from th
On Tue, Oct 02, 2012 at 06:00:54PM +0300, Andy Shevchenko wrote:
> There are several places in kernel that use functionality like shell's
> basename
> function. Let's do it common helper for them.
>
> Signed-off-by: Andy Shevchenko
> Cc: YAMANE Toshiaki
> ---
> include/linux/string.h | 11 ++
The Xen tree tries to add a line to
arch/arm/mach-vexpress/Makefile.boot that has been removed by the
following commit in Linus' master:
commit 617276307cd4cdb9a95c77efaa3063695af63aa7
Author: Rob Herring
Date: Thu Sep 6 13:43:04 2012 -0500
ARM: vexpress: convert to multi-platform
In fact
>> Then, you introduced bisect breakage. It is definitely unacceptable.
>
> What is "bisect breakage" meaning?
Think what's happen when only applying path [1/21].
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More m
On Mon, Oct 1, 2012 at 8:34 PM, Ni zhan Chen wrote:
> On 09/05/2012 05:25 PM, we...@cn.fujitsu.com wrote:
>>
>> From: Wen Congyang
>>
>> The function acpi_bus_remove() can remove a acpi device from acpi device.
>
> IIUC, s/acpi device/acpi bus
IIUC, acpi_bus_remove() mean "remove the device from
The 10 ms averager is not the only strange thing. Obviously there are some
good things in this scheduler, since it performs quite well. But I am not
criticising the good.
But the documentation makes a distinction between desktop and server with
the "resolution" parameter.
I tried some value
On Tue, Oct 02, 2012 at 06:14:08PM +0200, Jiri Kosina wrote:
> Hi,
>
> this commit:
>
> ==
> 1331e7a1bbe1f11b19c4327ba0853bee2a606543 is the first bad commit
> commit 1331e7a1bbe1f11b19c4327ba0853bee2a606543
> Author: Paul E. McKenney
> Date: Thu Aug 2 17:43:50 2012 -0700
>
> rcu: Remove
On Tue, 2 Oct 2012 18:36:42 +0200, Arnd Bergmann wrote:
> Calling kstrtoul requires checking the result. In case of
> the viper_tpm_setup function, let's fail the __setup function
> if the number was invalid.
>
> Without this patch, building viper_defconfig results in:
>
> arch/arm/mach-pxa/vip
On 10/02/2012 10:36 AM, Arnd Bergmann wrote:
> The PL310_ERRATA_753970 and ARM_ERRATA_764369 symbols only make sense
> when the base features for them are enabled, so select them
> conditionally in Kconfig to avoid warnings like:
>
> warning: (UX500_SOC_COMMON) selects PL310_ERRATA_753970 which ha
sers/dhowells/linux-headers.git/shortlog/refs/tags/uapi-prep-20121001
I have just done another regeneration so that arm64 is covered too. That
has now been posted under:
uapi-post-split-20121001- The complete set
uapi-prep-20121002 - The preparatory set
I will send
On Tue, 2012-10-02 at 18:49 +0200, Ferenc Wagner wrote:
> Going into the opposite direction: I found that Linux 3.6 does not
> permanently break the SoL console on upping eth0! I'll try to find
> the
> commit which (sort of) fixed it.
These are the likely fixes:
>
commit cf9ecf4b631f649a964fa611
On Thursday, September 27, 2012 06:19:53 PM Alex Deucher wrote:
> On Thu, Sep 27, 2012 at 10:54 AM, Alex Deucher
wrote:
> > On Thu, Sep 27, 2012 at 9:23 AM, Andres Freund wrote:
> >> On Thursday, September 27, 2012 03:14:31 PM Alex Deucher wrote:
> >>> On Thu, Sep 27, 2012 at 2:46 AM, Andres Fre
On x86 memory accesses to pages without the ACCESSED flag set result in the
ACCESSED flag being set automatically. With the ARM architecture a page access
fault is raised instead (and it will continue to be raised until the ACCESSED
flag is set for the appropriate PTE/PMD).
For normal memory pages
On Tue, Oct 02, 2012 at 05:55:11PM +0100, David Howells wrote:
> Catalin Marinas wrote:
>
> > There is arm64 that got merged, so its headers need splitting as well.
> > I'm happy to send a pull request myself just for arm64 if you give me
> > the script, otherwise you can run you script again clo
On Tue, Oct 2, 2012 at 9:36 AM, Stefano Stabellini
wrote:
> Hello,
> I am testing linus/master after the recent merge with the arm-soc tree
> and I find that if I choose:
>
> ARM system type
> 1. Allow multiple platforms to be selected (ARCH_MULTIPLATFORM) (NEW)
> 2. ARM Ltd. Integrator family
On Tue, 2 Oct 2012 11:50:28 -0400
Christoph Hellwig wrote:
> > +#defineAUDIT_TYPE_UNKNOWN 0 /* we don't know yet */
> > +#define AUDIT_TYPE_NORMAL 1 /* a "normal" audit record */
>
> I don't care about tab vs space after the #define, but at least be
> consistent.
>
I went
Catalin Marinas wrote:
> There is arm64 that got merged, so its headers need splitting as well.
> I'm happy to send a pull request myself just for arm64 if you give me
> the script, otherwise you can run you script again close to -rc1 (and
> I'll test it).
I can just re-run my scripts and post a
On Tue, Oct 02, 2012 at 05:45:17PM +0100, Stefano Stabellini wrote:
> This patch is actually a merge conflict resolution between Konrad's Xen
> tree and the following commit:
>
> commit 9fa5780beea1274d498a224822397100022da7d4
> Author: Jan Beulich
> Date: Tue Sep 18 12:23:02 2012 +0100
>
>
"Michael Chan" writes:
> On Tue, 2012-10-02 at 14:07 +0200, Ferenc Wagner wrote:
>
>> I'm done with bisecting it: the first bad commit is:
>>
>> commit dabc5c670d3f86d15ee4f42ab38ec5bd2682487d
>> Author: Matt Carlson
>> Date: Thu May 19 12:12:52 2011 +
>>
>> tg3: Move TSO_CAPABLE ass
This patch is actually a merge conflict resolution between Konrad's Xen
tree and the following commit:
commit 9fa5780beea1274d498a224822397100022da7d4
Author: Jan Beulich
Date: Tue Sep 18 12:23:02 2012 +0100
USB EHCI/Xen: propagate controller reset information to hypervisor
Compile dbgp.
On 10/02/2012 12:42 PM, Alexander Gordeev wrote:
On Tue, Oct 02, 2012 at 07:09:29AM +0200, Ingo Molnar wrote:
+irqreturn_t ahci_hw_interrupt(int irq, void *dev_instance)
+{
+ struct ata_port *ap_this = dev_instance;
+ struct ahci_port_priv *pp = ap_this->private_data;
+ struct
The sys_timer init function is only called at __init time,
so it's safe to mark mv78xx0_timer_init as __init_refok,
which allows us to call orion_time_init without getting
a link time warning.
Without this patch, building mv78xx0_defconfig results in:
WARNING: vmlinux.o(.text+0x15470): Section mi
Calling kstrtoul requires checking the result. In case of
the viper_tpm_setup function, let's fail the __setup function
if the number was invalid.
Without this patch, building viper_defconfig results in:
arch/arm/mach-pxa/viper.c: In function 'viper_tpm_setup':
arch/arm/mach-pxa/viper.c:771:10: w
On Tue, 2 Oct 2012 11:53:38 -0400
Christoph Hellwig wrote:
> On Mon, Oct 01, 2012 at 08:16:11PM -0400, Jeff Layton wrote:
> > In some cases, we were passing in NULL even when we have a dentry.
> >
> > Reported-by: Eric Paris
> > Signed-off-by: Jeff Layton
> > ---
> > kernel/auditsc.c | 4 ++--
The *_irq_add function should not be marked __init because the driver
subsystem thinks they might be called at a later stage.
The usb_simtec_init function accesses initdata and should be marked
init. This is safe because the only caller is also an init function.
Without this patch, building s3c24
The sharpsl_fatal_check has not been used since Pavel Machek removed
the caller in 99f329a2b "pxa/sharpsl_pm: zaurus c3000 aka spitz: fix
resume". Nobody has complained since 2009, so it's safe to assume we
can just remove the function.
Without this patch, building corgi_defconfig results in:
/ho
On Tue, Oct 02, 2012 at 07:09:29AM +0200, Ingo Molnar wrote:
> > +irqreturn_t ahci_hw_interrupt(int irq, void *dev_instance)
> > +{
> > + struct ata_port *ap_this = dev_instance;
> > + struct ahci_port_priv *pp = ap_this->private_data;
> > + struct ata_host *host = ap_this->host;
> > + stru
The symbol "GPIO24_SSP1_SFRM" is defined in both mfp-pxa27x.h and
mfp-pxa25x.h. Since the macro is not actually used in the cm-x2xx.c
file, but it includes both headers, a safe workaround should be
to just undefine it from the .c file. This is a bit hacky and
the headers should be fixed to not both
Gcc prints a harmless warning about palmte2_pxa_keys not being used
when the gpio keyboard driver is disabled. The solution is to use
the same #ifdef that is already present in the place where the
symbol is used.
Without this patch, building palmz72_defconfig results in:
/home/arnd/linux-arm/arch
The pci map_irq callbacks get a 'const' pci_dev argument, so change the
iop13xx version to use the same prototype as everything else.
Without this patch, building iop13xx_defconfig results in:
arch/arm/mach-iop13xx/iq81340sc.c:63:2: warning: initialization from
incompatible pointer type [enabled
The mityomapl138_cpufreq_init and read_factory_config function in
board-mityomapl138.c are not __init functions and might be called
at a later stage, so da850_register_cpufreq must not be __init either.
Without this patch, building da8xx_omapl_defconfig results in:
WARNING: arch/arm/mach-davinci/
On NOMMU systems, we do cannot remap the MMIO space, so the
definition of at91_io_desc is unused.
Without this patch, building at91x40_defconfig results in:
arch/arm/mach-at91/setup.c:90:24: warning: 'at91_io_desc' defined but not used
[-Wunused-variable]
Signed-off-by: Arnd Bergmann
Cc: Nicol
The code using the variable 'i' in this function is conditional, so
we have to make the declaration conditional as well to avoid a harmless
warning.
Without this patch, building at91sam9263_defconfig results in:
/home/arnd/linux-arm/arch/arm/mach-at91/pm.c: In function
'at91_pm_verify_clocks':
/
On Mon, Oct 1, 2012 at 1:16 PM, David Howells wrote:
>
> Could you please pull this tree at the _end_ of this merge window?
At the KS you said you'd be able to split this up into a preparatory
patch. That doesn't seem to have happened.
The whole "at the end of the merge window" tends to be somet
The CONFIG_MEMORY_SIZE value is interpreted as a 32 bit integer, which
makes sense on a system without PAE. I'm assuming 0x1000 (256 MB)
is the correct size, because that is used on most other shmobile
boards.
Without this patch, building kota2_defconfig results in:
/home/arnd/linux-arm/arch/
device_register is marked __must_check, so we better propagate the error
value by returning it from ecard_probe.
Without this patch, building rpc_defconfig results in:
arch/arm/mach-rpc/ecard.c: In function 'ecard_probe':
arch/arm/mach-rpc/ecard.c:963:17: warning: ignoring return value of
'devic
pci_scan_root_bus is __devinit, so iop13xx_scan_bus has to be the
same in order to safely call it. This is ok because the function
itself is only called from the hwpci->scan callback.
WARNING: vmlinux.o(.text+0x10138): Section mismatch in reference from the
function iop13xx_scan_bus() to the func
As tests using 'make randconfig' showed, imx5 requires the same logic
as imx6 to select ARM_CPU_SUSPEND when building with power management
enabled.
The defconfig does not have this problem because it enables imx6
as well, but disabling it leads to this warning:
arch/arm/mach-imx/built-in.o: In f
__arch_virt_to_dma expects a virtual address pointer, but
the ks8695 implementation of this macro treats it as an
integer. Adding a type cast avoids hundreds of identical
warning messages.
Without this patch, building acs5k_defconfig results in:
arch/arm/include/asm/dma-mapping.h: In function 'vi
Hello,
I am testing linus/master after the recent merge with the arm-soc tree
and I find that if I choose:
ARM system type
1. Allow multiple platforms to be selected (ARCH_MULTIPLATFORM) (NEW)
2. ARM Ltd. Integrator family (ARCH_INTEGRATOR)
3. ARM Ltd. RealView family (ARCH_REALVIEW)
> 4. A
The PL310_ERRATA_753970 and ARM_ERRATA_764369 symbols only make sense
when the base features for them are enabled, so select them
conditionally in Kconfig to avoid warnings like:
warning: (UX500_SOC_COMMON) selects PL310_ERRATA_753970 which has unmet direct
dependencies (CACHE_PL310)
warning: (AR
When run on the wrong platform, the shark_pci_init function
returns an undefined value, as reported by a gcc warning,
so let's just return -ENODEV.
Without this patch, building shark_defconfig results in:
arch/arm/mach-shark/pci.c: In function 'shark_pci_init':
arch/arm/mach-shark/pci.c:42:3: war
On Tue, Oct 2, 2012 at 6:03 AM, Mauro Carvalho Chehab
wrote:
>
> I basically tried a few different approaches, including deferred probe(),
> as you suggested, and request_firmware_async(), as Kay suggested.
Stop this crazy. FIX UDEV ALREADY, DAMMIT.
Who maintains udev these days? Is it Lennart/K
> > Some minor issues I ran into (but no show stoppers):
> > - The error messages for bad -c expressions could be better
> > - I found the requirement for no space after -c unintuitive.
>
> I'll see to that >
> > - It would be nice to have support for doing the bucketizing per line
> > instead of
Hi David,
On 1 October 2012 22:05, David Howells wrote:
> Could you please pull this tree at the _end_ of this merge window?
>
> The patches therein extract the Userspace API bits from the various header
> files named in the Kbuild files and separate them out into their own files.
> The original
On Tue, Oct 02, 2012 at 04:43:59PM +0530, Sekhar Nori wrote:
> On 10/1/2012 7:20 PM, Ben Gardiner wrote:
> > On Mon, Oct 1, 2012 at 8:32 AM, Matt Porter wrote:
> >> On Mon, Oct 01, 2012 at 05:34:02PM +0530, Sekhar Nori wrote:
> >>> Hi Matt,
> >>>
> >>> On 9/29/2012 1:07 AM, Matt Porter wrote:
> >>
On Tue, Oct 02, 2012 at 06:06:26PM +0200, Jiri Olsa wrote:
> On Tue, Oct 02, 2012 at 05:49:26PM +0200, Frederic Weisbecker wrote:
> > On Tue, Oct 02, 2012 at 04:58:15PM +0200, Jiri Olsa wrote:
> > > diff --git a/arch/x86/kernel/cpu/perf_event.c
> > > b/arch/x86/kernel/cpu/perf_event.c
> > > index
Hi,
this commit:
==
1331e7a1bbe1f11b19c4327ba0853bee2a606543 is the first bad commit
commit 1331e7a1bbe1f11b19c4327ba0853bee2a606543
Author: Paul E. McKenney
Date: Thu Aug 2 17:43:50 2012 -0700
rcu: Remove _rcu_barrier() dependency on __stop_machine()
Currently, _rcu_barrier() re
On Tue, Oct 02, 2012 at 03:32:55PM +0530, Sekhar Nori wrote:
> On 10/1/2012 6:02 PM, Matt Porter wrote:
> > On Mon, Oct 01, 2012 at 05:34:02PM +0530, Sekhar Nori wrote:
> >> Hi Matt,
> >>
> >> On 9/29/2012 1:07 AM, Matt Porter wrote:
> >>> L3RAM (shared SRAM) is needed for use by several drivers.
>
On Tue, Oct 02, 2012 at 06:19:22PM +0300, Kirill A. Shutemov wrote:
> From: "Kirill A. Shutemov"
>
> During testing I noticed big (up to 2.5 times) memory consumption overhead
> on some workloads (e.g. ft.A from NPB) if THP is enabled.
>
> The main reason for that big difference is lacking zero
On 09/28/2012 08:31 AM, Mel Gorman wrote:
> On Tue, Sep 25, 2012 at 04:31:01PM -0700, Dan Magenheimer wrote:
>> Attached patch applies to staging-next and I _think_ should
>> fix the reported problem where zbud in zcache2 does not
>> work on a PPC64 with PAGE_SIZE!=12. I do not have a machine
>> t
On Tue, 2012-10-02 at 16:35 +0300, Artem Bityutskiy wrote:
> Hi Linus,
>
> please, pull UBI changes.
>
> The following changes since commit 4cbe5a555fa58a79b6ecbb6c531b8bab0650778d:
>
> Linux 3.6-rc4 (2012-09-01 10:39:58 -0700)
>
> are available in the git repository at:
FYI, there will be t
On Tue, Oct 02, 2012 at 12:52:00PM +1000, NeilBrown wrote:
> On Fri, 28 Sep 2012 16:57:45 -0700 Greg Kroah-Hartman
> wrote:
>
> > On Sat, Sep 29, 2012 at 12:51:04AM +0200, Ben Hutchings wrote:
> > > On Fri, 2012-09-28 at 13:34 -0700, Greg Kroah-Hartman wrote:
> > > > 3.0-stable review patch. If
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git
tags/rdma-for-linus
First batch of InfiniBand/RDMA changes for the 3.7 merge window:
- mlx4 IB support for SR-IOV
- A couple of
On Tue, Oct 02, 2012 at 05:49:26PM +0200, Frederic Weisbecker wrote:
> On Tue, Oct 02, 2012 at 04:58:15PM +0200, Jiri Olsa wrote:
> > diff --git a/arch/x86/kernel/cpu/perf_event.c
> > b/arch/x86/kernel/cpu/perf_event.c
> > index 915b876..11d62ff 100644
> > --- a/arch/x86/kernel/cpu/perf_event.c
>
On 10/01/2012 07:55 PM, Michel Lespinasse wrote:
> On Fri, Sep 28, 2012 at 4:20 PM, Daniel Santos
> wrote:
>> BUILD_BUG_ON42(arg)
>> BUILD_BUG_ON_CONST42(arg)
>>
>> Prior to gcc 4.2, the optimizer was unable to determine that many
>> constant values stored in structs were indeed compile-time cons
On Wed, Oct 03, 2012 at 12:21:31AM +0900, Namhyung Kim wrote:
> Hi,
>
> This patchset improves bash completion support for perf tools. Some
> option names are really painful to type so here comes a support for
> completing those long option names. But I still think the
> --showcpuutilization opt
This simplifies the code.
Signed-off-by: Axel Lin
---
drivers/extcon/extcon-max77693.c | 18 ++
1 file changed, 6 insertions(+), 12 deletions(-)
diff --git a/drivers/extcon/extcon-max77693.c b/drivers/extcon/extcon-max77693.c
index e21387e..e0ed622 100644
--- a/drivers/extcon/
On Tue, 2 Oct 2012 11:50:28 -0400
Christoph Hellwig wrote:
> > +#defineAUDIT_TYPE_UNKNOWN 0 /* we don't know yet */
> > +#define AUDIT_TYPE_NORMAL 1 /* a "normal" audit record */
>
> I don't care about tab vs space after the #define, but at least be
> consistent.
>
My bad
On Mon, Oct 01, 2012 at 08:16:12PM -0400, Jeff Layton wrote:
> If name is NULL then the condition in the loop will never be true. Also,
> with this change, we can eliminate the check for n->name == NULL since
> the equivalence check will never be true if it is.
Given that name == NULL is a static
From: Peter Meerwald
fixe typos in comments and correct trivial debug output
Signed-off-by: Peter Meerwald
---
drivers/mfd/twl4030-madc.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/mfd/twl4030-madc.c b/drivers/mfd/twl4030-madc.c
ind
On Wed, Oct 03, 2012 at 12:21:32AM +0900, Namhyung Kim wrote:
> The '_get_comp_words_by_ref' function is available from the bash
> completion v1.2 so that earlier version emits following warning:
>
> $ perf re_get_comp_words_by_ref: command not found
>
> Use older '_get_cword' method when the a
On Mon, Oct 01, 2012 at 08:16:11PM -0400, Jeff Layton wrote:
> In some cases, we were passing in NULL even when we have a dentry.
>
> Reported-by: Eric Paris
> Signed-off-by: Jeff Layton
> ---
> kernel/auditsc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kerne
On Tue, Oct 2, 2012 at 7:13 AM, Sekhar Nori wrote:
> On 10/1/2012 7:20 PM, Ben Gardiner wrote:
>> On Mon, Oct 1, 2012 at 8:32 AM, Matt Porter wrote:
>>> On Mon, Oct 01, 2012 at 05:34:02PM +0530, Sekhar Nori wrote:
Hi Matt,
On 9/29/2012 1:07 AM, Matt Porter wrote:
> L3RAM (share
> +#define AUDIT_TYPE_UNKNOWN 0 /* we don't know yet */
> +#define AUDIT_TYPE_NORMAL1 /* a "normal" audit record */
I don't care about tab vs space after the #define, but at least be
consistent.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
On Tue, Oct 02, 2012 at 04:58:15PM +0200, Jiri Olsa wrote:
> diff --git a/arch/x86/kernel/cpu/perf_event.c
> b/arch/x86/kernel/cpu/perf_event.c
> index 915b876..11d62ff 100644
> --- a/arch/x86/kernel/cpu/perf_event.c
> +++ b/arch/x86/kernel/cpu/perf_event.c
> @@ -34,6 +34,7 @@
> #include
> #inc
On Tue, 2012-10-02 at 15:14 +, Pallala, Ramakrishna wrote:
> > On Tue, 2012-10-02 at 12:54 +, Pallala, Ramakrishna wrote:
> > > > > How can I schedule driver's worker and threaded IRQ on the same core?
> > > > >
> > > > > For work queue we have schedule_delayed_work_on () API available.
> >
On Tue, Oct 02, 2012 at 01:43:04AM +0100, Jon Masters wrote:
> On 07/06/2012 05:05 PM, Catalin Marinas wrote:
>
> > +/*
> > + * PAGE_OFFSET - the virtual address of the start of the kernel image.
> > + * VA_BITS - the maximum number of bits for virtual addresses.
> > + * TASK_SIZE - the maximum si
The main assumption of the async request design is that the file
system adds block requests to the block device queue asynchronously
without waiting for completion (see the Rationale section of
https://wiki.linaro.org/WorkingGroups/Kernel/Specs
/StoragePerfMMC-async-req).
We found out that in case
On Mon, Sep 24, 2012 at 03:34:42PM -0700, Kent Overstreet wrote:
[..]
> /**
> * bio_integrity_alloc - Allocate integrity payload and attach it to bio
> * @bio: bio to attach integrity metadata to
> @@ -84,37 +47,39 @@ struct bio_integrity_payload *bio_integrity_alloc(struct
> bio *bio,
>
On Tue, Oct 02, 2012 at 05:35:59PM +0200, Brice Goglin wrote:
> Le 02/10/2012 17:19, Kirill A. Shutemov a écrit :
> > From: "Kirill A. Shutemov"
> >
> > On right access to huge zero page we alloc a new page and clear it.
> >
>
> s/right/write/ ?
Oops... thanks.
--
Kirill A. Shutemov
--
To uns
Le 02/10/2012 17:19, Kirill A. Shutemov a écrit :
> From: "Kirill A. Shutemov"
>
> On right access to huge zero page we alloc a new page and clear it.
>
s/right/write/ ?
Brice
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.k
On Tue, 2 Oct 2012, Jan Beulich wrote:
> >>> On 02.10.12 at 17:13, Stefano Stabellini
> >>> wrote:
> > This patch is actually a merge conflict resolution between Konrad's Xen
> > tree and the following commit:
> >
> > commit 9fa5780beea1274d498a224822397100022da7d4
> > Author: Jan Beulich
> > D
Signed-off-by: Axel Lin
---
drivers/extcon/extcon-class.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/extcon/extcon-class.c b/drivers/extcon/extcon-class.c
index 946a318..337bbb4 100644
--- a/drivers/extcon/extcon-class.c
+++ b/drivers/extcon/extcon-class.c
virtio-scsi needs to report LUNs greater than 256 using the "flat"
format. Because the Linux SCSI layer just maps the SCSI LUN to
an u32, without any parsing, these end up in the range from 16640
to 32767. Fix max_lun to account for the possibility that logical
unit numbers are encoded with the "
Support the LUN parameter change event. Currently, the host fires this event
when the capacity of a disk is changed from the virtual machine monitor.
The resize then appears in the kernel log like this:
sd 0:0:0:0: [sda] 46137344 512-byte logical blocks: (23.6 GB/22.0 GIb)
sda: detected capac
From: Richard W.M. Jones
The sg struct is used without being initialized, which breaks
when CONFIG_DEBUG_SG is enabled.
Cc: sta...@vger.kernel.org
Signed-off-by: Richard W.M. Jones
Signed-off-by: Paolo Bonzini
---
drivers/scsi/virtio_scsi.c |2 +-
1 files changed, 1 insertions(+), 1 delet
James, here is a resend of the three pending patches for
virtio-scsi, with the bugfix first.
Thanks,
Paolo
Paolo Bonzini (2):
virtio-scsi: fix LUNs greater than 255
virtio-scsi: support online resizing of disks
Richard W.M. Jones (1):
virtio-scsi: initialize scatterlist structure
driver
>>> On 02.10.12 at 17:13, Stefano Stabellini
>>> wrote:
> This patch is actually a merge conflict resolution between Konrad's Xen
> tree and the following commit:
>
> commit 9fa5780beea1274d498a224822397100022da7d4
> Author: Jan Beulich
> Date: Tue Sep 18 12:23:02 2012 +0100
>
> USB EHCI
The main perf binary can receive a number of options that configure
working environment. Add them to the completion script.
Cc: Frederic Weisbecker
Cc: David Ahern
Signed-off-by: Namhyung Kim
---
tools/perf/bash_completion | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
Add internal --list-opts option to print all of long option names to
stdout so that it can be used for bash completion engine.
Cc: Frederic Weisbecker
Cc: David Ahern
Signed-off-by: Namhyung Kim
---
tools/perf/bash_completion |9 +++--
tools/perf/util/parse-options.c |8 ++
The '_get_comp_words_by_ref' function is available from the bash
completion v1.2 so that earlier version emits following warning:
$ perf re_get_comp_words_by_ref: command not found
Use older '_get_cword' method when the above function doesn't exist.
Cc: Frederic Weisbecker
Cc: David Ahern
Si
Hi,
This patchset improves bash completion support for perf tools. Some
option names are really painful to type so here comes a support for
completing those long option names. But I still think the
--showcpuutilization option needs to be renamed (at least adding a
couple of dashes in it).
Thank
Hi,
On Tue, 2 Oct 2012 16:13:15 +0100 Stefano Stabellini
wrote:
>
> This patch is actually a merge conflict resolution between Konrad's Xen
> tree and the following commit:
>
> commit 9fa5780beea1274d498a224822397100022da7d4
> Author: Jan Beulich
> Date: Tue Sep 18 12:23:02 2012 +0100
>
>
From: "Kirill A. Shutemov"
On right access to huge zero page we alloc a new page and clear it.
In fallback path we create a new table and set pte around fault address
to the newly allocated page. All other ptes set to normal zero page.
Signed-off-by: Kirill A. Shutemov
Reviewed-by: Andrea Arca
From: "Kirill A. Shutemov"
It's easy to copy huge zero page. Just set destination pmd to huge zero
page.
It's safe to copy huge zero page since we have none yet :-p
Signed-off-by: Kirill A. Shutemov
Reviewed-by: Andrea Arcangeli
---
mm/huge_memory.c | 17 +
1 files changed,
301 - 400 of 633 matches
Mail list logo
