On Mon, Mar 4, 2013 at 7:53 AM, Myklebust, Trond
wrote:
> On Mon, 2013-03-04 at 23:33 +0800, Ming Lei wrote:
>> Hi,
>>
>> CC guys who introduced the lockdep change.
>>
>> On Mon, Mar 4, 2013 at 11:04 PM, Jeff Layton wrote:
>>
>> >
>> > I don't get it -- why is it bad to hold a lock across a
On one of my m68k configs, v3.9-rc1 gives me:
mm/ksm.c: In function ‘get_kpfn_nid’:
mm/ksm.c:492: error: implicit declaration of function ‘pfn_to_nid’
It turns out lacks a definition for pfn_to_nid() if
CONFIG_DISCONTIGMEM=y.
Gr{oetje,eeting}s,
Geert
--
Geert
>> >
>> > +
>> > +#ifdef CONFIG_OF
>> > +static const struct of_device_id tpm_tis_i2c_of_match[] = {
>> > + { .compatible = "infineon,tpm_i2c_infineon", .data = (void *)0 },
>> > + { .compatible = "infineon,slb9635tt", .data = (void *)0 },
>> > + { .compatible = "infineon,slb9645tt", .data =
On Mon, 4 Mar 2013 21:56:19 +0400
Stanislav Kinsbursky wrote:
> 04.03.2013 18:47, Jeff Layton пишет:
> > On Mon, 4 Mar 2013 10:38:45 +0400
> > Stanislav Kinsbursky wrote:
> >
> >> 01.03.2013 17:09, Jeff Layton пишет:
> >>> On Fri, 01 Mar 2013 11:24:23 +0300
> >>> Stanislav Kinsbursky wrote:
>
A moderately sized pile of fixes, some specifically for merge window
introduced regressions although we others are for longer standing
items and have been queued up for -stable.
I'm kind of tired of all the RDS protocol bugs over the years, to be
honest, it's way out of proportion to the number
Am Montag, 4. März 2013, 20:42:00 schrieb Geert Uytterhoeven:
> drivers/staging/vt6656/card.c: In function ‘CARDqGetNextTBTT’:
> drivers/staging/vt6656/card.c:793: warning: integer constant is too large
> for ‘unsigned long’ type
>
> Commit c7b7cad0d8df823ea063c86a54316bbcbfa04a7c
Last known good: 3.8.0
Bad version: 3.9-rc1
[6.116492] =
[6.116614] [ BUG: ktpacpi_nvramd/446 still has locks held! ]
[6.116737] 3.9.0-rc1 #1 Not tainted
[6.116821] -
[6.116900] 1 lock held by
+ rjw, akpm, tejun, mingo, oleg
On Mon, Mar 4, 2013 at 6:23 AM, Jeff Layton wrote:
> On Mon, 4 Mar 2013 14:14:23 +
> "Myklebust, Trond" wrote:
>
>> On Mon, 2013-03-04 at 21:57 +0800, Ming Lei wrote:
>> > Hi,
>> >
>> > The below warning can be triggered each time when mount.nfs is
>> >
Hi Kent,
short reply from my private account - so only talking on behalf of myself.
Am Montag, 4. März 2013, 18:41:04 schrieb Kent Yoder:
> Hi Peter,
>
> Sorry for the long delay in getting this reviewed...
No problem.
>
> > - for (count = 0; count < MAX_COUNT; count++) {
> > -
I am currently tracking a hotlock reported by a customer on a large system,
512 cores. I am currently running 3.8-rc7 but the issue looks like it has been
this way for a very long time.
The offending lock is proc_dir_entry->pde_unload_lock.
This patch converts the lock to use the rcu. However
Removed unused function nfnl_get_lock which fixed the following warning:
net/netfilter/nfnetlink.c:65:22: warning: ‘nfnl_get_lock’ defined but not used
[-Wunused-function]
Signed-off-by: Alexandru Gheorghiu
---
net/netfilter/nfnetlink.c |5 -
1 file changed, 5 deletions(-)
diff --git
drivers/staging/vt6656/card.c: In function ‘CARDqGetNextTBTT’:
drivers/staging/vt6656/card.c:793: warning: integer constant is too large for
‘unsigned long’ type
Commit c7b7cad0d8df823ea063c86a54316bbcbfa04a7c ("staging/vt6656: Fix
sparse warning constant 0xU is so big it is
On Thu, Feb 28, 2013 at 11:28:47AM +0100, Roger Pau Monne wrote:
> This prevents us from having to call alloc_page while we are preparing
> the request. Since blkfront was calling alloc_page with a spinlock
> held we used GFP_ATOMIC, which can fail if we are requesting a lot of
> pages since it is
On Mon, Mar 4, 2013 at 9:05 AM, Theodore Ts'o wrote:
> Russ, how about this patch instead? Can you verify whether or not
> this fixes your issue? If so, I'll push it to Linus.
>
> - Ted
Yup, fixes the circular locking dependency.
Tested-by:
On 03/03/2013 10:03:55 PM, Eric W. Biederman wrote:
Rob Landley writes:
> On 03/01/2013 03:57:40 AM, Michael Kerrisk (man-pages) wrote:
>> > And yet the glibc guys insist on #define
>> GNU_GNU_GNU_ALL_HAIL_STALLMAN in
>> > order to access this Linux-specific feature which has nothing
>>
On Mon, Mar 4, 2013 at 12:59 AM, Huang Shijie wrote:
> 于 2013年03月04日 16:46, Artem Bityutskiy 写道:
>
>> Thanks, I forgot we have this great table. BTW, please, do not forget to
>> update it with information about these 4 chip you are adding,
>> irrespective of the solution we end up with.
>
> I
Hi,
On Mon, Mar 04, 2013 at 02:34:10PM +0100, Borislav Petkov wrote:
> Pjooiiing!
Heh, that was a broken one!
Rather well-deserved though - took too much time, been too busy.
> Andreas, Peter, can you guys give http://lkml.org/lkml/2012/12/30/47 a run?
Will fire up my HDD NOW.
About time to
On Mon, Mar 04, 2013 at 01:59:41PM -0500, Mimi Zohar wrote:
> On Mon, 2013-03-04 at 10:29 -0500, Vivek Goyal wrote:
> [...]
>
> > Hi Mimi,
> >
> > If we decide to merge flags, then practically we modified the
> > ima_appraise_tcb policy. ima_appraise_tcb policy expects to cache the
> > results
Matthew Dharm writes:
> Frankly, I consider it appropriate.
OK, I'll try to cook something up.
> The question is not one of reminding me of what I said earlier
> it's one of pointing people in the right direction. Frankly, some of
> the fault for this patch lies with Greg and myself for
Hi Konrad,
On 04/03/2013 19:40, Konrad Rzeszutek Wilk wrote:> After git merge
ab7826595e9ec51a51f622c5fc91e2f59440481a
> (Merge tag 'mfd-3.9-1' of
git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-2.6)
> the nouveau driver ends up shutting of the machine when booting.
>
>
> I hadn't
Hello, Lai.
On Sat, Mar 02, 2013 at 11:55:29PM +0800, Lai Jiangshan wrote:
> After we introduce multiple pools for cpu pools, a part of the comments
> in wq_unbind_fn() becomes wrong.
>
> It said that "current worker would trigger unbound chain execution".
> It is wrong. current worker only
I think that is what he was suggesting. It reuses the integrity code
but it loses the integrity flexibility. I don't think it is a good
solution :-(
On Mon, Mar 4, 2013 at 1:59 PM, Mimi Zohar wrote:
> On Mon, 2013-03-04 at 10:29 -0500, Vivek Goyal wrote:
> [...]
>
>> Hi Mimi,
>>
>> If we
On 03.12.2012 13:54, Ilya Zykov wrote:
> The root of problem is carelessly zeroing pointer(in function
> __tty_buffer_flush()),
> when another thread can use it. It can be cause of "NULL pointer dereference".
> Main idea of the patch, this is never release last (struct tty_buffer) in
> the
On Mon, 4 Mar 2013 15:04:49 +
Anton Altaparmakov wrote:
> Hi,
>
> The below commit that is present in 3.9-rc1 is buggy. It releases the page
> at which point it may no longer exist and then it unlocks it afterwards.
> Even if you are somehow getting away with it I think it is an
>
From: Silviu-Mihai Popescu
Date: Mon, 4 Mar 2013 09:09:31 +0200
> This fixes the following sparse warning:
> net/caif/caif_usb.c:84:16: warning: symbol 'cfusbl_create' was not
> declared. Should it be static?
>
> Signed-off-by: Silviu-Mihai Popescu
Applied.
--
To unsubscribe from this list:
On 03/04/2013 07:40 PM, Randy Dunlap wrote:
> On 03/03/13 19:43, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130301:
>>
>
> on x86_64:
>
> warning: (AD7606 && AD799X_RING_BUFFER && MXS_LRADC && IIO_ADIS_LIB_BUFFER &&
> INV_MPU6050_IIO && HID_SENSOR_ACCEL_3D && AD_SIGMA_DELTA &&
A few years back intel published a spec update:
http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
For the 5520 and 5500 chipsets which contained an errata (specificially errata
53), which noted that these chipsets can't properly do
This patch adds support for the tps65090 charger driver. This driver is
responsible for controlling the charger aspect of the tps65090 mfd.
Currently, this mainly consists of turning on and off the charger, but
some features of the charger can be supported through this driver
including:
Enable
Add irq resources to pass to the charger mfd sub dev so
the charger can listen for interrupts.
Signed-off-by: Rhyland Klein
---
v2:
- no changes since v1
drivers/mfd/tps65090.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/mfd/tps65090.c b/drivers/mfd/tps65090.c
This change adds the binding documentation for the tps65090-charger.
Signed-off-by: Rhyland Klein
---
v2:
- no changes since v1
.../devicetree/bindings/power_supply/tps65090.txt | 23
1 file changed, 23 insertions(+)
create mode 100644
This patchset adds support for the TPS65090-charger. This charger is
registered as a subdevice of the TPS65090 PMIC.
This series includes a fix for the tps65090 header file where all
the interrupts were shifted by 1.
Changes since v1:
- cleaned up tps65090 driver per comments (mostly var
The enum is missing the definition for the first bit, which makes all
the rest off by one. Add definition for the TPS65090_IRQ_INTERRUPT bit
which at 0.
Signed-off-by: Rhyland Klein
---
v2:
- no changes since v1
include/linux/mfd/tps65090.h |1 +
1 file changed, 1 insertion(+)
diff --git
On Mon, Mar 04, 2013 at 11:41:04AM -0600, Kent Yoder wrote:
> > .id_table = tpm_tis_i2c_table,
> > .probe = tpm_tis_i2c_probe,
> > .remove = tpm_tis_i2c_remove,
> > @@ -703,11 +759,12 @@ static struct i2c_driver tpm_tis_i2c_driver = {
> >.name = "tpm_i2c_infineon",
> >
On Mon, 2013-03-04 at 10:29 -0500, Vivek Goyal wrote:
[...]
> Hi Mimi,
>
> If we decide to merge flags, then practically we modified the
> ima_appraise_tcb policy. ima_appraise_tcb policy expects to cache the
> results and we will not do that. And this conflict just grows if we
> are forced to
On Tue, Feb 26, 2013 at 5:27 PM, Dan Williams wrote:
> On Fri, Feb 22, 2013 at 11:40 PM, Kees Cook wrote:
>> The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
>> while now and is almost always enabled by default. As agreed during the
>> Linux kernel summit, remove it from
* Nishanth Menon [130301 06:42]:
> On Fri, Mar 1, 2013 at 1:47 AM, Ивайло Димитров wrote:
> >
> > They look similar, but they are not equivalent :). The first major
> > difference is here (code taken from omap-smc.S)
> >
> >> ENTRY(omap_smc2)
> >> stmfd sp!, {r4-r12, lr}
> >>
[3.199957] Bluetooth: BNEP socket layer initialized
[3.204441] type=1400 audit(1362422678.075:2): apparmor="STATUS"
operation="profile_load" name="/usr/lib/cups/backend/cups-pdf" pid=754
comm="apparmor_parser"
[3.204671] type=1400 audit(1362422678.075:3): apparmor="STATUS"
Hello,
On Sat, Mar 02, 2013 at 09:41:54AM +0100, richard -rw- weinberger wrote:
> On Fri, Mar 1, 2013 at 10:42 PM, Srinivas Eeda
> wrote:
> > Yes that was the crash I was referring to which stopped me from testing my
> > other patch on mainline. I think the crashes started since some workqueue
* Felipe Balbi [130304 10:56]:
> Hi,
>
> On Mon, Mar 04, 2013 at 10:46:50AM -0800, Tony Lindgren wrote:
> > > The last three are caused by incorrect use of 'select':
> > >
> > > warning: (MACH_OMAP_ZOOM2 && MACH_OMAP_ZOOM3 && MWAVE) selects
> > > SERIAL_8250 which has unmet direct dependencies
Hi,
On Mon, Mar 04, 2013 at 10:46:50AM -0800, Tony Lindgren wrote:
> > The last three are caused by incorrect use of 'select':
> >
> > warning: (MACH_OMAP_ZOOM2 && MACH_OMAP_ZOOM3 && MWAVE) selects SERIAL_8250
> > which has unmet direct dependencies (TTY && HAS_IOMEM && GENERIC_HARDIRQS)
> >
There is an ifdef in page_cache_get_speculative() that checks for !SMP
and TREE_RCU, which has been an impossible combination since the advent
of TINY_RCU. The ifdef enables a fastpath that is valid when preemption
is disabled by rcu_read_lock() in UP systems, which is the case when
TINY_RCU is
Hi Rob & Felipe,
* Russell King - ARM Linux [130304 01:56]:
> Last nights automated ARM build found the following errors with randconfig.
>
> All information as usual at http://www.arm.linux.org.uk/developer/build/
>
>
> Versatile randconfig:
>
> ERROR: "irq_domain_add_simple"
On Mon, Mar 4, 2013 at 10:21 AM, Eric W. Biederman
wrote:
> Kees Cook writes:
>
>> On Mon, Mar 4, 2013 at 12:29 AM, Mathias Krause
>> wrote:
>>> On Sun, Mar 03, 2013 at 09:48:50AM -0800, Kees Cook wrote:
Several subsystems already have an implicit subsystem restriction
because they
On 03/03/13 19:43, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130301:
>
on x86_64:
warning: (AD7606 && AD799X_RING_BUFFER && MXS_LRADC && IIO_ADIS_LIB_BUFFER &&
INV_MPU6050_IIO && HID_SENSOR_ACCEL_3D && AD_SIGMA_DELTA && AD7266 && AD7298 &&
AD7476 && AD7887 && AT91_ADC && MAX1363
On 03/04/2013 04:56 AM, Huacai Chen wrote:
Currently, clear_page()/copy_page() are generated by Micro-assembler
dynamically. But they are unavailable until uasm_resolve_relocs() has
finished because jump labels are illegal before that. Since these
functions are shared by every CPU, we only call
Introduce struct workqueue_attrs which carries worker attributes -
currently the nice level and allowed cpumask along with helper
routines alloc_workqueue_attrs() and free_workqueue_attrs().
Each worker_pool now carries ->attrs describing the attributes of its
workers. All functions dealing with
Vasily Kulikov writes:
> (cc'ed kernel-hardening)
>
> On Sun, Mar 03, 2013 at 23:51 -0800, Eric W. Biederman wrote:
>> Modify the request_module to prefix the file system type with "fs-"
>> and add aliases to all of the filesystems that can be built as modules
>> to match.
>>
>> A common
> From: Ric Mason [mailto:ric.mas...@gmail.com]
> Subject: Re: zsmalloc limitations and related topics
>
> On 02/28/2013 07:24 AM, Dan Magenheimer wrote:
> > Hi all --
> >
> > I've been doing some experimentation on zsmalloc in preparation
> > for my topic proposed for LSFMM13 and have run across
There are cases where workqueue users want to expose control knobs to
userland. e.g. Unbound workqueues with custom attributes are
scheduled to be used for writeback workers and depending on
configuration it can be useful to allow admins to tinker with the
priority or allowed CPUs.
This patch
Adjusting max_active of or applying new workqueue_attrs to an ordered
workqueue breaks its ordering guarantee. The former is obvious. The
latter is because applying attrs creates a new pwq (pool_workqueue)
and there is no ordering constraint between the old and new pwqs.
Make
On Mon, 2013-03-04 at 13:18 -0500, Konrad Rzeszutek Wilk wrote:
> as if you are debugging this driver you would be using 'debug'
> on the command line anyhow - and this would dump the debug
> data on the proper loglevel.
Please add
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
before any #includes
Kees Cook writes:
> On Mon, Mar 4, 2013 at 12:29 AM, Mathias Krause
> wrote:
>> On Sun, Mar 03, 2013 at 09:48:50AM -0800, Kees Cook wrote:
>>> Several subsystems already have an implicit subsystem restriction
>>> because they load with aliases. (e.g. binfmt-, net-pf=NNN,
>>> snd-card-NNN,
On 04.03.2013 11:46, Mihai Donțu wrote:
Hi,
I apologize in advance for posting on two lists at once and for not
even being subscribed to e1000-devel.
Ever since upgrading to 3.8.x, I'm unable to use my wired connection
(e1000e - Intel Corporation 82579LM Gigabit) immediately after power
on. I
Now that v3.9-rc1 is out and you are enjoying your time in Hong Kong
and are probabally fighting with the jet-lag, here are eleven
patches that per your recommendation were deferred to v3.10.
Nothing has changed with them and they just make the code easier
to understand. The bulk of the code is
Note that at this point there is no CONFIG_ZCACHE_DEBUG
option in the Kconfig. So in effect all of the counters
are nop until that option gets re-introduced in:
zcache/debug: Coalesce all debug under CONFIG_ZCACHE_DEBUG
Acked-by: Dan Magenheimer
[v1: Fixed conflicts due to rebase]
Signed-off-by:
that are going to be used for debug fs entries.
Acked-by: Dan Magenheimer
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/zbud.c | 58 +--
1 file changed, 39 insertions(+), 19 deletions(-)
diff --git a/drivers/staging/zcache/zbud.c
It makes it neater and also allows us to piggyback on that
in the zcache_dump function.
Acked-by: Dan Magenheimer
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/debug.c | 163 +
1 file changed, 51 insertions(+), 112 deletions(-)
diff
This is the first step in moving the debugfs code out of the
main file in-to another file. And also allow the code to run
without CONFIG_DEBUG_FS defined.
Acked-by: Dan Magenheimer
[v2: Rebase on top staging/zcache: Fix/improve zcache writeback code, tie to a
config option]
[v3: Rebase on top
and also define this extra attribute in the Kconfig entry.
Acked-by: Dan Magenheimer
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/Kconfig | 8
drivers/staging/zcache/debug.c | 2 +-
drivers/staging/zcache/zcache-main.c | 6 +++---
3 files changed, 12
This way we can have all wrapped with these functions and
can disable/enable this with CONFIG_DEBUG_FS.
Acked-by: Dan Magenheimer
[v2: Rebase on top of staging/zcache: Fix/improve zcache writeback code, tie to
a config option]
[v3: Rebase on top of zcache: Fix compile warnings due to usage of
And now we can move the code ([inc|dec]_zcache_[*]) to their own file
with a header to make them nops or feed in debugfs.
Acked-by: Dan Magenheimer
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/zcache-main.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
We now have in zcache-main only the counters that are
are not debugfs related.
Acked-by: Dan Magenheimer
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/debug.h | 80 +++-
drivers/staging/zcache/zcache-main.c | 75
There are so many, but this allows us to at least have them
right in as bool.
Acked-by: Dan Magenheimer
[v1: Rebase on ramster->zcache move]
[v2: Rebase on staging/zcache: Fix/improve zcache writeback code, tie to a
config option]
Signed-off-by: Konrad Rzeszutek Wilk
---
as if you are debugging this driver you would be using 'debug'
on the command line anyhow - and this would dump the debug
data on the proper loglevel.
While at it also remove the unconditional #define ZCACHE_DEBUG.
Acked-by: Dan Magenheimer
Signed-off-by: Konrad Rzeszutek Wilk
---
The other (same license) is at the end of the file.
Acked-by: Dan Magenheimer
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/zcache-main.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/zcache/zcache-main.c
b/drivers/staging/zcache/zcache-main.c
index
> -Original Message-
> From: Dave Hansen [mailto:d...@linux.vnet.ibm.com]
> Sent: Monday, March 04, 2013 12:06 PM
> To: KY Srinivasan
> Cc: Greg KH; linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; a...@firstfloor.org; akpm@linux-
>
From: Raghavendra K T
This helps in filtering out the eligible candidates further and
thus potentially helps in quickly allowing preempted lockholders to run.
Note that if a vcpu was spinning during preemption we filter them
by checking whether they are preempted due to pause loop exit.
From: Raghavendra K T
Note that we mark as preempted only when vcpu's task state was
Running during preemption.
Thanks Jiannan, Avi for preemption notifier ideas. Thanks Gleb, PeterZ
for their precious suggestions. Thanks Srikar for an idea on avoiding
rcu lock while checking task state that
This patch series further filters better vcpu candidate to yield to
in PLE handler. The main idea is to record the preempted vcpus using
preempt notifiers and iterate only those preempted vcpus in the
handler. Note that the vcpus which were in spinloop during pause loop
exit are already filtered.
On Fri, Mar 01, 2013 at 03:06:07PM +0800, Li Zefan wrote:
> We no longer fail rmdir() when there're still css refs, so we don't
> need to check css refs in check_for_release().
>
> This also voids a bug. cgroup_has_css_refs() accesses subsys[i]
> without cgroup_mutex, so it can race with
Hello, Li.
On Fri, Mar 01, 2013 at 03:06:36PM +0800, Li Zefan wrote:
> /* Define the enumeration of all builtin cgroup subsystems */
> #define SUBSYS(_x) _x ## _subsys_id,
> -#define IS_SUBSYS_ENABLED(option) IS_ENABLED(option)
> enum cgroup_subsys_id {
> +#define IS_SUBSYS_ENABLED(option)
Making OP field a hex instead of integer to make it more readable. Also add
the dump out of the NEXT field.
Signed-off-by: Dave Jiang
---
drivers/dma/ioat/dma.h|2 +-
drivers/dma/ioat/dma_v3.c |3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git
04.03.2013 18:47, Jeff Layton пишет:
On Mon, 4 Mar 2013 10:38:45 +0400
Stanislav Kinsbursky wrote:
01.03.2013 17:09, Jeff Layton пишет:
On Fri, 01 Mar 2013 11:24:23 +0300
Stanislav Kinsbursky wrote:
Currently, UMH and Legacy trackers are disabled in containers.
But existent logic can
On Mon, Mar 04, 2013 at 11:08:24AM +0100, Samuel Ortiz wrote:
[...]
> > So, I can easily merge it, as long as MFD part is either Acked or handled
> > somehow else.
> I can Ack the MFD parts, they look good to me. And then you can take the whole
> thing through your tree, but I'd prefer you to do
"Michael Kerrisk (man-pages)" writes:
> On Fri, Mar 1, 2013 at 4:35 PM, Eric W. Biederman
> wrote:
>> "Michael Kerrisk (man-pages)" writes:
>>
>>> Hi Rob,
>>>
>>> On Fri, Mar 1, 2013 at 5:01 AM, Rob Landley wrote:
On 02/28/2013 05:24:07 AM, Michael Kerrisk (man-pages) wrote:
>>> [...]
On Mon, Mar 04, 2013 at 12:32:35PM -0500, Rhyland Klein wrote:
[...]
> >>Anton, David, would you be adverse to the changing of supplied_to
> >>from being a
> >>list of batteries stored in a charger to being a list of chargers
> >>stored in batteries?
> >>
> >I wonder if we can support both ways?..
On Fri, Mar 01, 2013 at 03:01:56PM +0800, Li Zefan wrote:
> rename() will change dentry->d_name. The result of this race can
> be worse than seeing partially rewritten name, but we might access
> a stale pointer because rename() will re-allocate memory to hold
> a longer name.
>
> As accessing
Meh, forgotten to actually cc more lists ...
-Daniel
On Mon, Mar 4, 2013 at 6:49 PM, Daniel Vetter wrote:
> On Mon, Mar 4, 2013 at 6:11 PM, Chris Li wrote:
>> To recap, the black screen first show up after the ACPI change to use widows
>> 8
>> string. The i915_setmode function did not crash.
On Mon, Mar 4, 2013 at 6:11 PM, Chris Li wrote:
> To recap, the black screen first show up after the ACPI change to use widows 8
> string. The i915_setmode function did not crash. The printk output
> from that function seems the same as the one that is in 3.6 kernel.
> I also include the 3.6 and
On Sun, Mar 03, 2013 at 07:29:53PM -0300, Marcelo Tosatti wrote:
> On Sun, Mar 03, 2013 at 03:00:22PM +0200, Gleb Natapov wrote:
> > On Fri, Mar 01, 2013 at 09:03:12PM -0300, Marcelo Tosatti wrote:
> > > On Thu, Feb 28, 2013 at 04:54:25PM +0800, Hu Tao wrote:
> > > > > > diff --git
On Mon, Mar 04, 2013 at 10:29:19AM -0500, Vivek Goyal wrote:
[..]
> This reduces our options but trying to make multiple policies co-exist
> together is just making it complicated. We can take it up again when
> somebody has a strong use case of using secureboot policy along with
> other
On Mon, Mar 04, 2013 at 08:45:48AM -0800, Paul Taysom wrote:
> @@ -449,8 +468,14 @@ static void verity_prefetch_io(struct dm_verity *v,
> struct dm_verity_io *io)
> hash_block_end = v->hash_blocks - 1;
> }
> no_prefetch_cluster:
> -
On Mon, 4 Mar 2013, Stephen Warren wrote:
> On 03/04/2013 12:55 AM, Venu Byravarasu wrote:
> > Stephen Warren wrote at Thursday, February 28, 2013 11:47 PM:
> >> On 02/27/2013 11:36 PM, Venu Byravarasu wrote:
> >>> To clear any configurations made by U-Boot on Tegra USB controller,
> >>> reset it
Hello,
On Mon, Mar 04, 2013 at 11:02:37AM +0800, Li Zefan wrote:
> > Yeah, that's what I meant by the "anal" part although it seems like
> > c99 doesn't even allow that. Do we care tho? It seems like a logical
> > feature which should show up in the standard eventually. Maybe it
> > could be a
On Sunday 24 February 2013 at 01:14:48, Rob Landley wrote:
> On 02/19/2013 08:27:41 AM, Lars Poeschel wrote:
> > From: Lars Poeschel
> >
> > This adds a simple sysfs interface to the pwm subsystem. It is
> > heavily inspired by the gpio sysfs interface.
>
> Docs!
This means I have to add more
On Mon, Mar 04, 2013 at 03:39:01AM +, Ben Hutchings wrote:
> 3.2-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Tejun Heo
>
> commit 326cf0f0f308933c10236280a322031f0097205d upstream.
>
> Most functions in idr fail to deal with the
(cc'ed kernel-hardening)
On Sun, Mar 03, 2013 at 23:51 -0800, Eric W. Biederman wrote:
> Modify the request_module to prefix the file system type with "fs-"
> and add aliases to all of the filesystems that can be built as modules
> to match.
>
> A common practice is to build all of the kernel
On Mon, 4 Mar 2013, Sergei Shtylyov wrote:
> > @@ -371,6 +371,7 @@ static int xhci_try_enable_msi(struct usb_hcd *hcd)
> > return -EINVAL;
> > }
> >
> > + legacy_irq:
> >
>
> Labels shouldn't be indented by a space (unless the existing coding
> style has them indented
On 03/04, Lianwei Wang wrote:
>
> Freeze/Thaw is a hot path for the Linux based mobile OS, e.g. Android.
> If we don't remove the pending fake signal, then the user space apps
> or the related kernel driver has to handle such error.
But if we add recalc_sigpending() we penalize the common case
(cc'ing Rusty Russell)
On Mon, Mar 04, 2013 at 10:59:58AM +0800, Li Zefan wrote:
> On 2013/3/3 3:23, Tommi Rantala wrote:
> > Hello,
> >
> > I'm seeing the following hung task warnings when fuzzing the kernel
> > with trinity (in a qemu virtual machine, as the root user), that I
> > have not
On 3/2/2013 5:48 PM, Anton Vorontsov wrote:
On Thu, Feb 28, 2013 at 02:48:03PM -0500, Rhyland Klein wrote:
[...]
Anton, David, would you be adverse to the changing of supplied_to
from being a
list of batteries stored in a charger to being a list of chargers
stored in batteries?
I wonder if we
On 3/2/2013 7:03 PM, Anton Vorontsov wrote:
Hello Rhyland,
Thanks for the driver! A few comments down below...
On Wed, Feb 27, 2013 at 06:07:30PM -0500, Rhyland Klein wrote:
This patch adds support for the tps65090 charger driver.
Would be nice to get a few more words about the hardware and
From: "Steven Rostedt (Red Hat)"
The new multi-buffers added a descriptor that kept track of module
events, and the directories they use, with struct ftace_module_file_ops.
This is used to add a ref count to keep modules from unloading while
their files are being accessed.
As the descriptor is
From: "Steven Rostedt (Red Hat)"
With the conversion of the data array to per cpu, sparse now complains
about the use of per_cpu_ptr() on the variable. But The variable is
allocated with alloc_percpu() and is fine to use. But since the structure
that contains the data variable does not annotate
From: Li Zefan
As we've added __init annotation to field-defining functions, we should
add __refdata annotation to event_call variables, which reference those
functions.
Link: http://lkml.kernel.org/r/51343c1f.2050...@huawei.com
Reported-by: Fengguang Wu
Signed-off-by: Li Zefan
From: Li Zefan
Those functions are called either during kernel boot or module init.
Before:
$ dmesg | grep 'Freeing unused kernel memory'
Freeing unused kernel memory: 1208k freed
Freeing unused kernel memory: 1360k freed
Freeing unused kernel memory: 1960k freed
After:
$ dmesg | grep
Some more updates to the linux-next queue for 3.10. Li Zefan did a few
updates to save a bit of kernel memory.
I did a few minor fixes to the previous patchset I sent out.
-- Steve
Li Zefan (4):
tracing: Add a helper function for event print functions
tracing: Annotate event
From: Li Zefan
These two functions are called during kernel boot only.
Link: http://lkml.kernel.org/r/51258796.7020...@huawei.com
Signed-off-by: Li Zefan
Signed-off-by: Steven Rostedt
---
kernel/trace/trace_syscalls.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Li Zefan
Move duplicate code in event print functions to a helper function.
This shrinks the size of the kernel by ~13K.
textdata bss dec hex filename
6596137 1743966 1013867218478775119f6b7 vmlinux.o.old
6583002 1743849 1013867218465523
On Wed, 27 Feb 2013 09:55:49 -0800
Eliezer Tamir wrote:
> This patchset adds the ability for the socket layer code to poll directly
> on an Ethernet device's RX queue. This eliminates the cost of the interrupt
> and context switch and with proper tuning allows us to get very close
> to the HW
301 - 400 of 1283 matches
Mail list logo
