On Wed, 13 Feb 2013 09:19:37 -0600, Clark Williams wrote:
> On Wed, 13 Feb 2013 10:15:12 +0100
> Ingo Molnar wrote:
>> * Namhyung Kim wrote:
>> > On Mon, 11 Feb 2013 10:54:58 +0100, Ingo Molnar wrote:
>> > > * Clark Williams wrote:
>> > >
>> > >> I figured that was coming. :)
>> > >
>> > > ;-)
This driver supports GRGPIO gpio cores available in the GRLIB VHDL IP
core library from Aeroflex Gaisler.
This also adds support to gpio-generic for using custom accessor
functions. The grgpio driver uses this to use ioread32be and iowrite32be
for big endian register accesses.
Reviewed-by: Anton
Hello,
Any comments about this patch and functionality?
Thanks,
Dmitry
On Wed, Feb 13, 2013 at 11:07 AM, Dmitry Kasatkin
wrote:
> User space tools use getxattr() system call to read values of extended
> attributes. getxattr() system call uses vfs_getattr(), which for "security."
> namespace
We now have a binding which adds two parameters to the matrix keypad DT
node. This is separate from the GPIO-driven matrix keypad binding, and
unfortunately incompatible, since that uses row-gpios/col-gpios for the
row and column counts.
So the easiest option here is to provide a function for
On Wed, 2013-02-13 at 17:20 -0800, H. Peter Anvin wrote:
> On 02/13/2013 04:12 PM, Satoru Takeuchi wrote:
> > From: Satoru Takeuchi
> >
> > There was a serious problem in samsung-laptop that its platform driver is
> > designed to run under BIOS and running under EFI can cause the machine to
> >
On Wed, 2013-02-13 at 11:23 +0100, Marc Kleine-Budde wrote:
> err = ubifs_init_security(dir, inode, >d_name);
> - if (err)
> + if (err) {
> + ubifs_err("cannot initialize extended attribute, error %d",
> + err);
> goto
On Wed, 2013-02-13 at 11:23 +0100, Marc Kleine-Budde wrote:
> --- a/fs/ubifs/journal.c
> +++ b/fs/ubifs/journal.c
> @@ -553,7 +553,8 @@ int ubifs_jnl_update(struct ubifs_info *c, const struct
> inode *dir,
>
> dbg_jnl("ino %lu, dent '%.*s', data len %d in dir ino %lu",
>
There is a forever loop calling iio_channel_release() because the
"chan < " part of the "chan < ARRAY_SIZE()" is missing. This is in both
the error handling on probe and also in the remove function.
The other thing is that it's possible for some of the elements of the
adc_bat->channel[chan]
On Wed, 2013-02-13 at 11:23 +0100, Marc Kleine-Budde wrote:
> This patch moves the modification of ui->ui_size and ui->data_len in the
> create_xattr() and change_xattr() functions, so that they are protected by the
> ui_mutex as stated in the documenation of the the struct ubifs_inode.
>
>
On Wed, 13 Feb 2013 14:09:08 -0700, Stephen Warren wrote:
> On 02/13/2013 11:02 AM, Doug Anderson wrote:
> > The force_nr parameter to i2c_add_mux_adapter() uses 0 to signify that
> > we don't want to force the bus number of the adapter. This is
> > non-ideal because:
> > * 0 is actually a valid
Mark, how about this one? I compiled it and ran on my fedora 16 with
SElinux enabled, no obvious issues.
>From a19350097200570571aa522afebb96b34db534f4 Mon Sep 17 00:00:00 2001
From: Artem Bityutskiy
Date: Thu, 14 Feb 2013 09:07:36 +0200
Subject: [PATCH] selinux: do not confuse lockdep
Selinux
14.02.2013 03:22, Eric W. Biederman пишет:
"J. Bruce Fields" writes:
On Wed, Feb 13, 2013 at 02:32:29PM -0800, Eric W. Biederman wrote:
"J. Bruce Fields" writes:
On Wed, Feb 13, 2013 at 01:29:35PM -0800, Eric W. Biederman wrote:
"J. Bruce Fields" writes:
On Wed, Feb 13, 2013 at
On Thu, 2013-02-14 at 15:44 +0900, Namjae Jeon wrote:
> 2013/2/14, Andrew Bartlett :
> > (apologies for the duplicate mail, I typo-ed the maintainers address)
> >
> > G'day,
> >
> > I've been looking into the patch "[v2] fat: editions to support
> > fat_fallocate()" and I wonder if there is a way
Hi Rusty,
On Thu, 14 Feb 2013 13:30:37 +1030 Rusty Russell wrote:
>
> This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but
> CONFIG_HVC_DRIVER isn't set.
>
> From drivers/char/Kconfig:
>
> config VIRTIO_CONSOLE
> tristate "Virtio console"
>
On Wed, Feb 13, 2013 at 10:09:56PM +, Grant Likely wrote:
> On Wed, 13 Feb 2013 22:29:51 +0100, Thierry Reding
> wrote:
> > On Wed, Feb 13, 2013 at 01:54:53PM -0600, Rob Herring wrote:
> > > On 02/13/2013 08:25 AM, Thierry Reding wrote:
> > > > On Wed, Feb 13, 2013 at 08:23:28AM -0600, Rob
On 2/14/2013 10:46 AM, Vishwanathrao Badarkhe, Manish wrote:
> Hi Sekhar,
>
> On Thu, Feb 14, 2013 at 09:48:59, Nori, Sekhar wrote:
>> Manish,
>>
>> On 1/31/2013 2:56 PM, Vishwanathrao Badarkhe, Manish wrote:
>>> As per OMAP-L138 TRM, Software must poll for SLEEPCOMPLETE bit until
>>> it is set
On Wed, Feb 13, 2013 at 10:56:07PM +, Grant Likely wrote:
> On Mon, 11 Feb 2013 09:22:19 +0100, Thierry Reding
> wrote:
> > This function can be used to parse the number of a device's parent PCI
> > bus from a standard 5-cell PCI resource.
> >
> > Signed-off-by: Thierry Reding
>
> This
On Wed, Feb 13, 2013 at 10:59:50PM +, Grant Likely wrote:
> On Mon, 11 Feb 2013 09:22:18 +0100, Thierry Reding
> wrote:
> > This function can be used to parse the device and function number from a
> > standard 5-cell PCI resource. PCI_SLOT() and PCI_FUNC() can be used on
> > the returned
On Wed, Feb 13, 2013 at 10:58:44PM +, Grant Likely wrote:
> On Mon, 11 Feb 2013 09:22:20 +0100, Thierry Reding
> wrote:
> > This function can be used to parse a bus-range property as specified by
> > device nodes representing PCI bridges.
> >
> > Signed-off-by: Thierry Reding
>
> Ditto
Use the key-matrix layer to interpret key scan information from the EC
and inject input based on the FDT-supplied key map. This driver registers
itself with the ChromeOS EC driver to perform communications.
The matrix-keypad FDT binding is used with a small addition to control
ghosting.
Hi Dmitry,
On Wed, Feb 13, 2013 at 12:02 PM, Dmitry Torokhov
wrote:
> Hi SImon,
>
> On Tue, Feb 12, 2013 at 06:42:26PM -0800, Simon Glass wrote:
>> Use the key-matrix layer to interpret key scan information from the EC
>> and inject input based on the FDT-supplied key map. This driver registers
2013/2/14 Rob Herring :
> On 02/13/2013 11:33 AM, Michal Simek wrote:
>> 2013/2/13 Rob Herring :
>>> On 02/13/2013 10:21 AM, Michal Simek wrote:
2013/2/7 Rob Herring :
> From: Rob Herring
>
> In cases where we have multiple nodes of the same type, we may need the
> node
2013/2/14, Andrew Bartlett :
> (apologies for the duplicate mail, I typo-ed the maintainers address)
>
> G'day,
>
> I've been looking into the patch "[v2] fat: editions to support
> fat_fallocate()" and I wonder if there is a way we can split this issue
> in two, so that we get at least some of
To replace magic number in "clocks = <_car 28>;"
Signed-off-by: Hiroshi Doyu
---
This patch depends on:
[PATCH 0/9] ARM: tegra: use new dtc+cpp feature
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-February/149613.html
This patch is the experiment for Tegra20. The same
On Wed, 2013-02-13 at 15:37 +0100, Marc Kleine-Budde wrote:
> > + lockdep_set_class(>lock, inode->i_sb->s_type->i_mutex_key);
>
> So I added an "&", so that the line looks like that:
Yeah, I did not compile it, and for the deadlock of course I have to add
own class for isec->lock in the fstype
Hi Sekhar,
This mail reached my inbox after I sent out v3.
On Tue, Feb 12, 2013 at 11:51:34, Nori, Sekhar wrote:
> On 2/7/2013 1:27 PM, Manjunathappa, Prakash wrote:
> > Adds device tree support for davinci_mmc. Also add binding documentation.
> > Tested in non-dma PIO mode and without GPIO
Paolo Bonzini writes:
> This series adds a different set of APIs for adding a buffer to a
> virtqueue. The new API lets you pass the buffers piecewise, wrapping
> multiple calls to virtqueue_add_sg between virtqueue_start_buf and
> virtqueue_end_buf. Letting drivers call virtqueue_add_sg
Randy Dunlap writes:
> On 02/13/13 00:35, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130212:
>
> on i386:
>
> drivers/built-in.o: In function `in_intr':
> virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll'
> virtio_console.c:(.text+0x2dd41): undefined reference to
"Michael S. Tsirkin" writes:
> On Wed, Feb 13, 2013 at 03:28:52PM +, Marc Zyngier wrote:
>> On 13/02/13 15:08, Pawel Moll wrote:
>> > On Wed, 2013-02-13 at 14:25 +, Marc Zyngier wrote:
>> >> Using readl() to read the magic value and then memcmp() to check it
>> >> fails on BE, as bytes
After commit 88b8dac0, dst-cpu can be changed in load_balance(),
then we can't know cpu_idle_type of dst-cpu when load_balance()
return positive. So, add explicit cpu_idle_type checking.
Cc: Srivatsa Vaddagiri
Signed-off-by: Joonsoo Kim
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
Commit 88b8dac0 makes load_balance() consider other cpus in its group,
regardless of idle type. When we do NEWLY_IDLE balancing, we should not
consider it, because a motivation of NEWLY_IDLE balancing is to turn
this cpu to non idle state if needed. This is not the case of other cpus.
So, change
Commit 88b8dac0 makes load_balance() consider other cpus in its group.
But, there are some missing parts for this feature to work properly.
This patchset correct these things and make load_balance() robust.
Others are related to LBF_ALL_PINNED. This is fallback functionality
when all tasks can't
Some validation for task moving is performed in move_tasks() and
move_one_task(). We can move these code to can_migrate_task()
which is already exist for this purpose.
Signed-off-by: Joonsoo Kim
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 97498f4..849bc8e 100644
---
Currently, LBF_ALL_PINNED is cleared after affinity check is passed.
So, if can_migrate_task() is failed by small load value or small
imbalance value, we don't clear LBF_ALL_PINNED. At last, we trigger
'redo' in load_balance().
Imbalance value is often so small that any tasks cannot be moved
to
Commit 88b8dac0 makes load_balance() consider other cpus in its group.
But, in that, there is no code for preventing to re-select dst-cpu.
So, same dst-cpu can be selected over and over.
This patch add functionality to load_balance() in order to exclude
cpu which is selected once.
Cc: Srivatsa
cur_ld_moved is reset if env.flags hit LBF_NEED_BREAK.
So, there is possibility that we miss doing resched_cpu().
Correct it as changing position of resched_cpu()
before checking LBF_NEED_BREAK.
Signed-off-by: Joonsoo Kim
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index
Commit 88b8dac0 makes load_balance() consider other cpus in its group.
So, now, When we redo in load_balance(), we should reset some fields of
lb_env to ensure that load_balance() works for initial cpu, not for other
cpus in its group. So correct it.
Cc: Srivatsa Vaddagiri
Signed-off-by: Joonsoo
This name doesn't represent specific meaning.
So rename it to imply it's purpose.
Signed-off-by: Joonsoo Kim
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 26058d0..e6f8783 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -6814,7 +6814,7 @@ struct task_group
If execve() fails past flush_old_exec(), we are obviously going to
kill the process. Right now it's implemented in $BIGNUM places in
->load_binary() and that's obviously brittle (and in at least one case
buggy - binfmt_flat lacks send_sig_info() on late failures). Now, there's
an obvious
Hi Sekhar,
On Thu, Feb 14, 2013 at 09:48:59, Nori, Sekhar wrote:
> Manish,
>
> On 1/31/2013 2:56 PM, Vishwanathrao Badarkhe, Manish wrote:
> > As per OMAP-L138 TRM, Software must poll for SLEEPCOMPLETE bit until
> > it is set to 1 before clearing SLEEPENABLE bit in DEEPSLEEP register
> > in
On Tue, 2013-02-12 at 00:01 -0500, tmhik...@gmail.com wrote:
> Okay, I finally have located the patch causing this bizzare problem
> for me. Before I discuss it, I'm going to drag out the kernel bug reporting
> guidelines and try to make a proper bug report out of this.
>
> [1.] One line
Commit-ID: 1de63d60cd5b0d33a812efa455d5933bf1564a51
Gitweb: http://git.kernel.org/tip/1de63d60cd5b0d33a812efa455d5933bf1564a51
Author: Satoru Takeuchi
AuthorDate: Thu, 14 Feb 2013 09:12:52 +0900
Committer: H. Peter Anvin
CommitDate: Wed, 13 Feb 2013 17:24:11 -0800
efi: Clear
On Wed, Feb 13, 2013 at 12:26:23PM +0100, Cong Ding wrote:
> > > > You need to send this to whomever is working on DMA bindings.
> > > Thank you bob, I added Vinod the the receiver list.
> > I have moved the of/dma.c to dma/of-dma.c, can you regenerate this patch and
> > resend to me
> Sorry
On 02/13/2013 05:38 PM, Doug Anderson wrote:
> Stephen,
>
>
> On Wed, Feb 13, 2013 at 1:04 PM, Stephen Warren wrote:
>> On 02/13/2013 11:02 AM, Doug Anderson wrote:
>>> We need to use the i2c-arbitrator to talk to any of the devices on i2c
>>> bus 4 on exynos5250-snow so that we don't confuse
On 02/13/2013 08:25 PM, Stephen Rothwell wrote:
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
kernel/timeconst.pl between commit 63a3f603413f ("timeconst.pl: Eliminate
Perl warning") from the tip tree and commit "timeconst.pl: remove
deprecated defined(@array)" from the
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
include/linux/sched.h between commit cf4aebc292fa ("sched: Move sched.h
sysctl bits into separate header") from the tip tree and commit "aio:
don't include aio.h in sched.h" from the akpm tree.
I fixed it up (see below) and
On Tue, Feb 12, 2013 at 11:05:12AM +0100, Samuel Ortiz wrote:
> Adding Dmitry to the thread, for the input parts.
Looks reasonable, however the patch is against older version of the
driver and most likely will not apply anymore...
Thanks.
>
> On Thu, Dec 20, 2012 at 09:57:19AM +0100,
On Fri, Feb 01, 2013 at 04:29:00PM +0800, Daniel Kurtz wrote:
> Investigating the following gesture highlighted two slight implementation
> errors with choosing which slots to report in which slot when multiple
> contacts are present:
>
> Action SGM AGM (MTB slot:Contact)
> 1.
On Sun, Feb 10, 2013 at 12:15:40PM -0800, Benson Leung wrote:
> This patch adds support for the Cypress APA Smbus Trackpad type,
> which uses a modified register map that fits within the
> limitations of the smbus protocol.
>
> Devices that use this protocol include:
> CYTRA-116001-00 - Samsung
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
kernel/timeconst.pl between commit 63a3f603413f ("timeconst.pl: Eliminate
Perl warning") from the tip tree and commit "timeconst.pl: remove
deprecated defined(@array)" from the akpm tree.
These both fix the same problem, I
On Wed, Feb 06, 2013 at 05:23:49PM +0100, Heiko Carstens wrote:
> When removing the !S390 dependency from drivers/input/Kconfig a couple
> of drivers don't compile because they have a dependency on GENERIC_HARDIRQS.
> So add the missing dependencies.
> Fixes e.g. this one:
>
>
Manish,
On 1/31/2013 2:56 PM, Vishwanathrao Badarkhe, Manish wrote:
> As per OMAP-L138 TRM, Software must poll for
> SLEEPCOMPLETE bit until it is set to 1 before clearing
> SLEEPENABLE bit in DEEPSLEEP register in resume routine.
> Modifications are as per datasheet:
>
On Wed, Feb 13, 2013 at 10:08 PM, Dirk Brandewie
wrote:
> For the case where both are built-in the load order works my driver uses
> device_initcall() and acpi_cpufreq uses late_initcall().
>
> For the case where both are a module (which I was sure I tested) you are
> right
> I will have to do
workqueue has moved away from global_cwqs to worker_pools and with the
scheduled custom worker pools, wforkqueues will be associated with
pools which don't have anything to do with CPUs. The workqueue code
went through significant amount of changes recently and mass renaming
isn't likely to hurt
On Thu, Feb 14, 2013 at 3:06 AM, Grant Likely wrote:
> On Tue, 12 Feb 2013 10:52:10 +0800, Haojian Zhuang
> wrote:
>> On 12 February 2013 07:10, Andrew Morton wrote:
>> > On Sun, 10 Feb 2013 00:57:57 +0800
>> > Haojian Zhuang wrote:
>> >
>> >> do_initcalls() could call all driver
is_chained_work() was added before current_wq_worker() and implemented
its own ham-fisted way of finding out whether %current is a workqueue
worker - it iterates through all possible workers.
Drop the custom implementation and reimplement using
current_wq_worker().
Signed-off-by: Tejun Heo
---
c9e7cf273f ("workqueue: move busy_hash from global_cwq to
worker_pool") incorrectly converted is_chained_work() to use
get_gcwq() inside for_each_gcwq_cpu() while removing get_gcwq().
As cwq might not exist for all possible workqueue CPUs, @cwq can be
NULL and the following cwq deferences can
> I've seen you have a notify_ops in the vmci bits. Do you have different
> notify ops depending on socket type or something? Does it make sense to
> move the notify ops ptr into "struct vsock_sock" maybe?
The notify stuff only applies to STREAMs. However, we have two different
notify impls,
On 02/12/2013 06:22 PM, Peter Zijlstra wrote:
> On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
>> Guess the search cpu from bottom to up in domain tree come from
>> commit 3dbd5342074a1e sched: multilevel sbe sbf, the purpose is
>> balancing over tasks on all level domains.
>>
>> This
On Thu, Feb 14, 2013 at 7:54 AM, Ryan Mallon wrote:
> Nitpicky - Is it accurate to call these hardware numbers? Don't some of
> the platforms remap the gpio numbers? These numbers may not match
> against the platform's datasheet for example.
I'm following a suggestion by Grant and Linus W. here.
and also define this extra attribute in the Kconfig entry.
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 insertions(+), 4 deletions(-)
On 02/12/2013 06:39 PM, Peter Zijlstra wrote:
> On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
>>
>> The cpu's utilization is to measure how busy is the cpu.
>> util = cpu_rq(cpu)->avg.runnable_avg_sum
>> / cpu_rq(cpu)->avg.runnable_avg_period;
>>
>> Since the util is
It makes it neater and also allows us to piggyback on that
in the zcache_dump function.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/debug.c | 163 +
1 file changed, 51 insertions(+), 112 deletions(-)
diff --git
The other (same license) is at the end of the file.
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 059c0f2..4b9ee7f 100644
---
> > + if (protocol)
> > + return -EPROTONOSUPPORT;
> > +
>
> IMO protocol == PF_VSOCK should not get rejected here.
Agreed, let me fix that too.
Thanks!
- Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi everyone,
On 02/13/2013 09:15 PM, Paul Turner wrote:
> On Wed, Feb 13, 2013 at 7:23 AM, Alex Shi wrote:
>> On 02/12/2013 06:27 PM, Peter Zijlstra wrote:
>>> On Thu, 2013-01-24 at 11:06 +0800, Alex Shi wrote:
Remove CONFIG_FAIR_GROUP_SCHED that covers the runnable info, then
we can
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/zbud.c | 38 --
1 file changed, 24 insertions(+), 14 deletions(-)
diff --git a/drivers/staging/zcache/zbud.c b/drivers/staging/zcache/zbud.c
index cff596c..e139cd6 100644
---
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.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/zcache-main.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git
>From Konrad Rzeszutek Wilk # This line is ignored.
From: Konrad Rzeszutek Wilk
Subject: [PATCH] Various cleanups/fixes to zcache (v3).
In-Reply-To:
Hey Greg,
These patches do various cleanups of the zcache driver. The majority of the
work is just to move all the different counters out to a
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.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/zcache-main.c |
There are so many, but this allows us to at least have them
right in as bool.
[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
---
drivers/staging/zcache/zcache-main.c | 30
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.
[v2: Rebase on top staging/zcache: Fix/improve zcache writeback code, tie to a
config option]
Signed-off-by: Konrad Rzeszutek Wilk
---
When we compile we get tons of:
include/linux/debugfs.h:80:16: note: expected ‘size_t *’ but argument is
of type ‘long int *’
drivers/staging/zcache/zcache-main.c:279:2: warning: passing argument 4
of ‘debugfs_create_size_t’ from incompatible pointer type [enabled by d
efault]
which is b/c we end
This way we can have all wrapped with these functions and
can disable/enable this with CONFIG_DEBUG_FS.
[v2: Rebase on top of staging/zcache: Fix/improve zcache writeback code, tie to
a config option]
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/zcache-main.c | 96
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
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/Makefile
We get tons of:
drivers/staging/zcache/zbud.c: In function ‘zbud_debugfs_init’:
drivers/staging/zcache/zbud.c:323:2: warning: passing argument 4 of
‘debugfs_create_size_t’ from incompatible pointer type [enabled by
default]
In file included from drivers/staging/zcache/zbud.c:305:0:
This fixes it
We get tons of "note: expected ‘size_t *’ but argument is of type ‘long
int *’" warnings. This fixes it.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/ramster/ramster.c | 34
1 file changed, 17 insertions(+), 17 deletions(-)
diff --git
Dear RT Folks,
I'm pleased to announce the 3.0.62-rt88 stable release.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
Head SHA1: 3568cae0aa56660cadd607e19096ad853822b28c
Or to build 3.0.62-rt88 directly, the following
We get:
WARNING: drivers/staging/zcache/zcache.o(.text+0x13a1): Section mismatch
in reference from the function zcache_init() to the function
.init.text:zbud_init()
The function zcache_init() references
the function __init zbud_init().
This is often because zcache_init lacks a __init
annotation or
that are going to be used for debug fs entries.
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 b/drivers/staging/zcache/zbud.c
Dear RT Folks,
I'm pleased to announce the 3.2.38-rt57 stable release.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
Head SHA1: 97eeac44604babd344fbcea25620de62ab520d88
Or to build 3.2.38-rt57 directly, the following
We now have in zcache-main only the counters that are
are not debugfs related.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/debug.h | 80 +++-
drivers/staging/zcache/zcache-main.c | 75 +
2 files changed,
Dear RT Folks,
I'm pleased to announce the 3.4.29-rt42 stable release.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
Head SHA1: eab759b5f284bd3c29aaa12f41623ef2cb2ac60d
Or to build 3.4.29-rt42 directly, the following
Clang/scan-build complains about a possible buffer overflow in
ieee80211_wx_get_name:
.../staging/rtl8192u/ieee80211/ieee80211_softmac_wx.c:499:3:
warning: String copy function overflows destination buffer
strcat(wrqu->name," link..");
On Wed, Feb 13, 2013 at 9:13 AM, Thomas Gleixner wrote:
> Dear RT Folks,
>
> I'm pleased to announce the 3.6.11-rt29 release.
>
> Changes since 3.6.11-rt26:
>
>1) Fix the RT highmem implementation on x86 this time really. The
> issue I was seeing with kmap_atomic and friends was
On Thu, Feb 14, 2013 at 7:49 AM, Ryan Mallon wrote:
> Is it really useful to use the same pr_debug for the error case? Why not do:
>
> desc = gpio_to_desc(gpio);
> if (!desc) {
> pr_debug("%s - Invalid gpio %d\n", __func__, gpio);
> return -EINVAL;
(apologies for the duplicate mail, I typo-ed the maintainers address)
G'day,
I've been looking into the patch "[v2] fat: editions to support
fat_fallocate()" and I wonder if there is a way we can split this issue
in two, so that we get at least some of the patch into the kernel.
G'day,
I've been looking into the patch "[v2] fat: editions to support
fat_fallocate()" and I wonder if there is a way we can split this issue
in two, so that we get at least some of the patch into the kernel.
https://lkml.org/lkml/2012/10/13/75
https://patchwork.kernel.org/patch/1589161/
What
On Wed, 2013-02-13 at 17:08 -0800, H. Peter Anvin wrote:
> Well, for at least things with device nodes (/dev/mem, /dev/msr and so
> on) it should be possible, no? ioperm() and iopl() are another matter.
Sure, if we can guarantee that a signed userspace loads a signed SELinux
policy before any
clang/scan-build complains that:
p80211netdev.c:451:6: warning: Branch condition evaluates to a garbage
value
if ((p80211_wep.data) && (p80211_wep.data != skb->data))
^
This can happen in p80211knetdev_hard_start_xmit if
- if (wlandev->state !=
> > > I thought about that, but actually there's no guarantee that the
> > > handle will be valid after _EJ0 as far as I can say. So the race
> > > condition is going to be there anyway and using struct acpi_device
> > > just makes it easier to avoid it.
> >
> > In theory, yes, a stale handle
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/thermal/intel_powerclamp.c: In function 'clamp_thread':
drivers/thermal/intel_powerclamp.c:360:21: error: 'MAX_USER_RT_PRIO' undeclared
(first use in this function)
Caused by commit
On Wed, Feb 13, 2013 at 10:13:16AM -0800, Eric W. Biederman wrote:
> Joel Becker writes:
>
> > On Wed, Nov 21, 2012 at 10:55:24AM +1100, Dave Chinner wrote:
> >> > diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> >> > index 2778258..3656b88 100644
> >> > --- a/fs/xfs/xfs_inode.c
> >> > +++
Last posting: http://marc.info/?l=linux-fsdevel=136063048002755=2
Got it working and ran some benchmarks. On a high end SSD, doing 4k
random reads with fio I got around a 30% increase in throughput.
(That was without the aio changes I recently did. With those, throughput
was aproximately
On 02/13/2013 05:31 PM, Linus Torvalds wrote:
> On Wed, Feb 13, 2013 at 4:54 PM, H. Peter Anvin wrote:
>>
>> It does for the callee, but only on a whole-file basis. It would be a
>> lot nicer if we could do it with function attributes.
>
> A way to just set the callee-clobbered list on a
On Wed, Feb 13, 2013 at 5:21 PM, Linus Torvalds
wrote:
>
> Now, on other machines you get the call chain even with pebs because
> you can get the whole
Oops, that got cut short early, because I started looking up when PEBS
and the last-branch-buffer work together, and couldn't find it, and
then
On Wed, Feb 13, 2013 at 04:52:14PM -0500, Benjamin LaHaise wrote:
> The io_cancel() syscall allows for cancellation of iocbs in flight to
> generate a completion event. The current behaviour of batch_complete_aio()
> is to suppress all completion events. Some types of asynchronous operations
>
On Wed, Feb 13, 2013 at 12:46:36PM -0500, Benjamin LaHaise wrote:
> The recent changes overhauling fs/aio.c introduced a bug that results in the
> kioctx not being freed when outstanding kiocbs are cancelled at exit_aio()
> time. Specifically, a kiocb that is cancelled has its completion events
>
On 2/13/2013 5:04 PM, Matthew Garrett wrote:
> On Wed, 2013-02-13 at 16:44 -0800, Casey Schaufler wrote:
>
>> If you want that sort of granularity throw yourself on the SELinux
>> bandwagon. Fine grained capabilities are insane and unmanageable
>> and will only lead to tears. Security is despised
On Wed, Feb 13, 2013 at 12:45:52PM -0500, Benjamin LaHaise wrote:
> When the number of available events in the ring buffer is calculated,
> the avail calculation is incorrect when head == tail. This is harmless
> in aio_read_events_ring(), but in free_ioctx() leads to the subsequent
>
1 - 100 of 1450 matches
Mail list logo
