From: Haojian Zhuang
This patch looks like it should be in the 3.8-stable tree, should we apply
it?
--
From: "Haojian Zhuang "
commit ad4e1a7caf937ad395ced585ca85a7d14395dc80 upstream
If index++ calculates from 0, the checking condition of "while
(index++)" fails & it doesn't
On 04/12, Andrey Vagin wrote:
> exit_task_work() must be called after exit_notify, because
> exit_task_namespaces() may release a file and fput() enqueues a work.
>
> exit_notify
> exit_task_namespaces
> free_ipc_ns
> shm_destroy
> fput
> task_work_add
>
> so if task
On 04/12, Steven Rostedt wrote:
>
> On Thu, 2013-04-11 at 13:59 +0200, Oleg Nesterov wrote:
>
> > > If so, we can do same thing also on trace_events.
> > > (perf_trace_##call in include/trace/ftrace.h)
> >
> > Yes, yes, this is not kprobe-specific. It seems that more users of
> >
Hi Linus
My for-linus branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Has a recent fix from Josef for our tree log replay code. It fixes
problems where the inode counter for the number of bytes in the file
wasn't getting updated properly during fsync
From: "Luis R. Rodriguez"
This adds backport support for all media subsystem
drivers. This is enabled only for >= 3.2. Some media
drivers rely on the new probe deferrral mechanism
(-EPROBE_DEFER see commit d1c3414c), those are only
enabled for kernels >= 3.4. Some media drivers only
depend on
From: "Luis R. Rodriguez"
This backports the latest regulator drivers for kernels >= 3.4.
We enable the regulator only on kernels >= 3.4 given that
it relies on the new probe deferral mechanism which would
otherwise mean having to support drivers that do not probe
correctly. Note that 3.2 had a
Don't complain about camelcase when using SUPPORTED_*/ADVERTISED_*
defines, they are part of the user api so can't be (easily) fixed.
Removes false positives in e.g. ethernet drivers like:
WARNING: Avoid CamelCase:
+ SUPPORTED_Autoneg |
Signed-off-by: Jonas
Ping.
Hi Lee,
Can you review this patch.
I think this one is a bug fix.
Regards,
Axel
2013/4/8 Axel Lin :
> The special handling code for getting shared mode status is wrong
> because it needs to check info->shared_mode->lp_mode_req for
> both regulators that shared the same mode register.
>
>
perf_trace_buf_prepare() + perf_trace_buf_submit() make no sense
if this task/CPU has no active counters. Change uprobe_perf_print()
to return if hlist_empty(call->perf_events).
Note: this is not uprobe-specific, we can change other users too.
Signed-off-by: Oleg Nesterov
---
2013/4/13 Paul E. McKenney :
> From: "Paul E. McKenney"
>
> Adaptive-ticks CPUs inform RCU when they enter kernel mode, but they do
> not necessarily turn the scheduler-clock tick back on. This state of
> affairs could result in RCU waiting on an adaptive-ticks CPU running
> for an extended
pdata is either a valid pointer or NULL, use NULL checking rather than
IS_ERR_OR_NULL macro.
Signed-off-by: Axel Lin
---
drivers/regulator/max8997.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/max8997.c b/drivers/regulator/max8997.c
index
From: Andrey Vagin
This patch looks like it should be in the 3.8-stable tree, should we apply
it?
--
From: "Andrey Vagin "
commit e9c5d8a562f01b211926d70443378eb14b29a676 upstream
do_loopback calls lock_mount(path) and forget to unlock_mount
if clone_mnt or copy_mnt fails.
[
Return proper error instead of 0 if pdata is NULL.
Signed-off-by: Axel Lin
---
drivers/mfd/max8997.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mfd/max8997.c b/drivers/mfd/max8997.c
index 1471405..823f34b 100644
--- a/drivers/mfd/max8997.c
+++
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
https://lkml.org/lkml/2013/4/1/292
As per above discussion, there is possibility that request's __data_len
field may overflow when max_discard_sectors greater than UINT_MAX >> 9
If multiple discard requests get merged, merged discard request's
size exceeds 4GB, there is
From: Namjae Jeon
https://lkml.org/lkml/2013/4/1/292
As per above discussion, it has been oberved that few drivers are
setting q->limits.max_discard_sectors to more than (UINT_MAX >> 9)
If multiple discard requests get merged, merged discard request's
size exceeds 4GB, there is possibility
From: Namjae Jeon
linux-v3.8-rc1 and later support for plug for blkdev_issue_discard with
commit 0cfbcafcae8b7364b5fa96c2b26ccde7a3a296a9
(block: add plug for blkdev_issue_discard )
For example,
1) DISCARD rq-1 with size size 4GB
2) DISCARD rq-2 with size size 1GB
If these 2 discard requests
On Sat, Apr 13, 2013 at 09:01:32PM +0800, Wanpeng Li wrote:
> Add how-to for ramster.
>
> Acked-by: Dan Magenheimer
> Singed-off-by: Dan Magenheimer
> Signed-off-by: Wanpeng Li
> ---
> drivers/staging/zcache/ramster/HOWTO.txt | 257
> ++
> 1 file changed, 257
On Thu, Apr 11, 2013 at 11:39 AM, Neil Zhang wrote:
> Add SMP support for pxa988.
>
> Signed-off-by: Neil Zhang
> Signed-off-by: Chao Xie
> ---
> arch/arm/mach-mmp/Makefile |4 +
> arch/arm/mach-mmp/common.h |2 +
> arch/arm/mach-mmp/headsmp.S | 104 ++
>
On Thu, Apr 11, 2013 at 11:38 AM, Neil Zhang wrote:
> bring up pxa988 with device tree support.
>
> Signed-off-by: Neil Zhang
> Signed-off-by: Chao Xie
> ---
> arch/arm/boot/dts/pxa988-dkb.dts | 36 ++
> arch/arm/boot/dts/pxa988.dtsi | 196
>
Fix coding style issue: ERROR: space prohibited before that '++' (ctx:WxO)
and line beyond 8 characters.
Acked-by: Dan Magenheimer
Signed-off-by: Wanpeng Li
---
drivers/staging/zcache/debug.h | 95
1 file changed, 76 insertions(+), 19 deletions(-)
Add how-to for ramster.
Acked-by: Dan Magenheimer
Singed-off-by: Dan Magenheimer
Signed-off-by: Wanpeng Li
---
drivers/staging/zcache/ramster/HOWTO.txt | 257 ++
1 file changed, 257 insertions(+)
create mode 100644 drivers/staging/zcache/ramster/HOWTO.txt
diff
Note that at this point there is no CONFIG_RAMSTER_DEBUG
option in the Kconfig. So in effect all of the counters
are nop until that option gets introduced in patch:
ramster/debug: Add CONFIG_RAMSTER_DEBUG Kconfig entry
Acked-by: Dan Magenheimer
Signed-off-by: Wanpeng Li
---
Use an array to initialize/use debugfs attributes, it makes them
neater as zcache/debug.c does.
Acked-by: Dan Magenheimer
Signed-off-by: Wanpeng Li
---
drivers/staging/zcache/ramster/debug.c | 68 +++-
1 file changed, 32 insertions(+), 36 deletions(-)
diff --git
Add incremental accessory counters that are going to be used for
debug fs entries.
Acked-by: Dan Magenheimer
Signed-off-by: Wanpeng Li
---
drivers/staging/zcache/ramster/debug.h | 67 ++
drivers/staging/zcache/ramster/ramster.c | 32 +++---
2 files
Add CONFIG_RAMSTER_DEBUG Kconfig entry.
Acked-by: Dan Magenheimer
Signed-off-by: Wanpeng Li
---
drivers/staging/zcache/Kconfig |8
drivers/staging/zcache/Makefile|2 +-
drivers/staging/zcache/ramster/debug.h |2 +-
3 files changed, 10 insertions(+), 2
Changelog:
v3 -> v4:
* fix compile issue
v2 -> v3:
* update patch description of staging: ramster: Move debugfs code out of
ramster.c file
* update patch title of staging: ramster/debug: Add RAMSTER_DEBUG Kconfig
entry
v1 -> v2:
* fix bisect issue
* fix issue in patch
On Thu, Apr 11, 2013 at 11:37 AM, Neil Zhang wrote:
> Move some of the function declaration to head file.
>
> Signed-off-by: Neil Zhang
> Signed-off-by: Chao Xie
> ---
> arch/arm/mach-mmp/common.h |3 +++
> arch/arm/mach-mmp/mmp-dt.c |3 ---
> arch/arm/mach-mmp/mmp2-dt.c |3 ---
>
On Mon, Mar 4, 2013 at 1:46 PM, Tony Lindgren wrote:
>
>> drivers/gpu/drm/tilcdc/tilcdc_slave.o:(.data+0x54): multiple definition of
>> `__mod_of_device_table'
>> drivers/gpu/drm/tilcdc/tilcdc_tfp410.o:(.data+0x54): first defined here
>> drivers/gpu/drm/tilcdc/tilcdc_panel.o:(.data+0x54):
Adding in cc: lkml
Il 13/04/2013 14:14, Marco Stornelli ha scritto:
Hi,
I was seeing the code of __mm_populate (in -next) and I've got a doubt
about the return value. The function __mlock_posix_error_return should
return a proper error for mlock, converting the return value from
On Sat, 2013-04-13 at 13:56 +0200, Ulf Hansson wrote:
>
> Den 13 apr 2013 12:49 skrev "Sergey Yanovich" :
> > A possible solution is to make card a separate device (now only the
> host
> > is a device). In this case, the probing could be done asynchronously
> > without breaking the assumption in
Hi,
On Sat, Apr 13 2013, Sergey Yanovich wrote:
> On Wed, 2013-03-27 at 07:57 -0400, Chris Ball wrote:
>> If the delay's significant, I agree with you and will revert this patch.
>
> The patch was reverted. The problem is back. Filed bug:
> https://bugzilla.kernel.org/show_bug.cgi?id=56561
>
> A
On Thu, Apr 11, 2013 at 11:37 AM, Neil Zhang wrote:
> From: Chao Xie
>
> PXA988 will use GIC as its interrupt controller, and ICU is used as wakeup
> logic. When AP subsystem is powered off, GIC will lose its context, the
> PMU will need ICU to wakeup the AP subsystem.
> When ICU works as wakeup
Sure, sorry about that. I was hoping the GUID would be enough. I'll see
what I can come up with.
On 04/12/2013 09:35 PM, Matthew Garrett wrote:
On Sat, 2013-04-13 at 03:31 +0200, Pali Rohár wrote:
all Fn keys, wifi switch, web and mute buttons not working anymore
on my notebook HP EliteBook
Dear Justin,
looking at the example at
http://www.lanedo.com/~aleksander/fanotify/fanotify-example.c
the large file support is enabled by passing O_LARGEFILE to fanotify_init:
if ((fanotify_fd = fanotify_init (FAN_CLOEXEC,
O_RDONLY | O_CLOEXEC |
Hello,
This morning I did a luksOpen on an external harddisk and saw:
# cryptsetup luksOpen /dev/sde1 crypto2
Enter passphrase for /dev/sde1:
semid 557063: semop failed for cookie 0xd4dd6db: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by
cookie
The pm2301-charger driver implements runtime pm and at the same time uses the
legacy pm callbacks for suspend and resume. This does not work since the I2C
core wont look at the legacy pm callbacks if a driver has the 'pm' field set.
This patch fixes it by moving over to dev_pm_ops for
On Wed, 2013-03-27 at 07:57 -0400, Chris Ball wrote:
> If the delay's significant, I agree with you and will revert this patch.
The patch was reverted. The problem is back. Filed bug:
https://bugzilla.kernel.org/show_bug.cgi?id=56561
A possible solution is to make card a separate device (now
Signed-off-by: Jussi Kivilinna
---
crypto/tcrypt.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c
index 24ea7df..66d254c 100644
--- a/crypto/tcrypt.c
+++ b/crypto/tcrypt.c
@@ -1768,6 +1768,21 @@ static int do_test(int m)
Patch adds AVX2/x86-64 implementation of Serpent cipher, requiring 16 parallel
blocks for input (256 bytes). Implementation is based on the AVX implementation
and extends to use the 256-bit wide YMM registers. Since serpent does not use
table look-ups, this implementation should be close to two
Patch adds AVX2/x86-64 implementation of Twofish cipher, requiring 16 parallel
blocks for input (256 bytes). Table look-ups are performed using vpgatherdd
instruction directly from vector registers and thus should be faster than
earlier implementations. Implementation also uses 256-bit wide YMM
Signed-off-by: Jussi Kivilinna
---
crypto/testmgr.h | 1100 --
1 file changed, 1062 insertions(+), 38 deletions(-)
diff --git a/crypto/testmgr.h b/crypto/testmgr.h
index d503660..dc2c054 100644
--- a/crypto/testmgr.h
+++ b/crypto/testmgr.h
@@
Patch adds AVX2/x86-64 implementation of Blowfish cipher, requiring 32 parallel
blocks for input (256 bytes). Table look-ups are performed using vpgatherdd
instruction directly from vector registers and thus should be faster than
earlier implementations.
Signed-off-by: Jussi Kivilinna
---
The following series implements four block ciphers - Blowfish, Twofish, Serpent
and Camellia - using AVX2 instruction set. This work on AVX2 implementations
started over year ago and have been available at
https://github.com/jkivilin/crypto-avx2
The Serpent and Camellia implementations
Replace sb_start_write with sb_start_write_killable where
possible.
Signed-off-by: Marco Stornelli
---
fs/open.c |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/fs/open.c b/fs/open.c
index 8c74100..d621d76 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -182,7 +182,9
Replace file_start_write with file_start_write_killable where
possible.
Signed-off-by: Marco Stornelli
---
drivers/block/loop.c |4 +++-
fs/aio.c |7 +--
fs/coda/file.c |4 +++-
fs/read_write.c | 28 +---
fs/splice.c |
Added a new enum to decide if we want to sleep in uninterruptible or
killable state or we want simply to return immediately.
Signed-off-by: Marco Stornelli
---
fs/super.c | 24 ++--
include/linux/fs.h | 19 +--
2 files changed, 31 insertions(+),
Hi,
I rebased the work on top of -next and I applied a Jan's comment about
__sb_start_write.
I did some basic tests and they are ok.
Open points:
- without change mnt_want_write several paths are still blocking paths;
- page_mkwrite still call blocking variant of __sb_start_write.
Any comments
On Fri, Apr 12, 2013 at 09:34:13AM -0600, Stephen Warren wrote:
> On 04/12/2013 08:58 AM, Jay Agarwal wrote:
> >>> err = regulator_disable(pcie->pex_clk_supply);
> >>> if (err < 0)
> >>> - dev_err(pcie->dev, "failed to disable pex-clk regulator:
> >> %d\n",
> >>> +
* Oleg Nesterov [2013-04-09 22:13:02]:
> On 04/09, Oleg Nesterov wrote:
> >
> > > Should we a check here before using top most ri.
> > > What if the application had done a longjmp and the trampoline he hit
> > > corresponds to something thats below in the stack?
> > >
> > > Not sure if this what
On Sat, Apr 13, 2013 at 12:51 AM, Rafael J. Wysocki wrote:
> On Friday, April 12, 2013 11:08:37 PM Sedat Dilek wrote:
>> On Fri, Apr 12, 2013 at 6:27 PM, Sedat Dilek wrote:
>> > On Fri, Apr 12, 2013 at 5:45 PM, Sedat Dilek wrote:
>> >> On Fri, Apr 12, 2013 at 4:24 PM, Sedat Dilek
>> >> wrote:
* Oleg Nesterov [2013-04-09 21:32:35]:
> Change uprobe_trace_print() and uprobe_perf_print() to check
> is_ret_probe() and fill ring_buffer_event accordingly.
>
> Also change uprobe_trace_func() and uprobe_perf_func() to not
> _print() if is_ret_probe() is true. Note that we keep ->handler()
>
* Oleg Nesterov [2013-04-09 15:33:33]:
> On 04/07, Srikar Dronamraju wrote:
> >
> > * Oleg Nesterov [2013-04-01 18:08:51]:
> >
> > > diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c
> > > index e91a354..db2718a 100644
> > > --- a/kernel/trace/trace_uprobe.c
> > > +++
* Oleg Nesterov [2013-04-10 16:58:44]:
> uprobe_perf_print() passes addr=ip to perf_trace_buf_submit() for
> no reason. This sets perf_sample_data->addr for PERF_SAMPLE_ADDR,
> we already have perf_sample_data->ip initialized if PERF_SAMPLE_IP.
>
> Signed-off-by: Oleg Nesterov
Acked-by:
On 64 bit systems the agp_info struct has a hole between ->agp_mode and
->aper_base. We need to clear it to avoid leaking stack information to
userspace.
Signed-off-by: Dan Carpenter
diff --git a/drivers/char/agp/frontend.c b/drivers/char/agp/frontend.c
index 2e04433..3fbce33 100644
---
At Fri, 12 Apr 2013 22:33:59 -0500,
Calvin Owens wrote:
>
> When recording at 176.2KHz or 192Khz, the device adds a 32-bit length
> header to the capture packets, which obviously needs to be ignored for
> recording to work properly.
>
> Userspace expected: L0 L1 L2 R0 R1 R2
> ...but actually
On 04/12/2013 02:09 PM, Federico Vaga wrote:
> [...]
>
> [**] (argumentation based, obviously, on my limited understanding)
>
> These drivers work like this:
>
> child = device_find_child(parent, data, match_function);
> if (child) {
> put_device(child);
Signed-off-by: Jianpeng Ma
---
fs/block_dev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/block_dev.c b/fs/block_dev.c
index aae187a..f0328f1 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -1559,7 +1559,7 @@ static ssize_t blkdev_aio_read(struct kiocb *iocb, const
Hi Linus,
Can you please pull the m68knommu git tree, for-linus branch.
It contains only a single compilation fix for ColdFire m68k targets
that use local non-GPIOLIB support.
Regards
Greg
The following changes since commit 31880c37c11e28cb81c70757e38392b42e695dc6:
Linux 3.9-rc6
On Fri, Apr 12, 2013 at 04:54:02PM -0700, Josh Triplett wrote:
> On Fri, Apr 12, 2013 at 04:19:13PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > Systems with HZ=100 can have slow bootup times due to the default
> > three-jiffy delays between quiescent-state forcing
Hello,
On Apr 10, 2013, at 11:18 , Seth Jennings wrote:
> +/* invalidates all pages for the given swap type */
> +static void zswap_frontswap_invalidate_area(unsigned type)
> +{
> + struct zswap_tree *tree = zswap_trees[type];
> + struct rb_node *node;
> + struct zswap_entry *entry;
Hello,
On Apr 10, 2013, at 11:18 , Seth Jennings wrote:
+/* invalidates all pages for the given swap type */
+static void zswap_frontswap_invalidate_area(unsigned type)
+{
+ struct zswap_tree *tree = zswap_trees[type];
+ struct rb_node *node;
+ struct zswap_entry *entry;
+
+
On Fri, Apr 12, 2013 at 04:54:02PM -0700, Josh Triplett wrote:
On Fri, Apr 12, 2013 at 04:19:13PM -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Systems with HZ=100 can have slow bootup times due to the default
three-jiffy delays between quiescent-state
Hi Linus,
Can you please pull the m68knommu git tree, for-linus branch.
It contains only a single compilation fix for ColdFire m68k targets
that use local non-GPIOLIB support.
Regards
Greg
The following changes since commit 31880c37c11e28cb81c70757e38392b42e695dc6:
Linux 3.9-rc6
Signed-off-by: Jianpeng Ma majianp...@gmail.com
---
fs/block_dev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/block_dev.c b/fs/block_dev.c
index aae187a..f0328f1 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -1559,7 +1559,7 @@ static ssize_t
On 04/12/2013 02:09 PM, Federico Vaga wrote:
[...]
[**] (argumentation based, obviously, on my limited understanding)
These drivers work like this:
child = device_find_child(parent, data, match_function);
if (child) {
put_device(child);
At Fri, 12 Apr 2013 22:33:59 -0500,
Calvin Owens wrote:
When recording at 176.2KHz or 192Khz, the device adds a 32-bit length
header to the capture packets, which obviously needs to be ignored for
recording to work properly.
Userspace expected: L0 L1 L2 R0 R1 R2
...but actually got: R2
On 64 bit systems the agp_info struct has a hole between -agp_mode and
-aper_base. We need to clear it to avoid leaking stack information to
userspace.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/char/agp/frontend.c b/drivers/char/agp/frontend.c
index
* Oleg Nesterov o...@redhat.com [2013-04-10 16:58:44]:
uprobe_perf_print() passes addr=ip to perf_trace_buf_submit() for
no reason. This sets perf_sample_data-addr for PERF_SAMPLE_ADDR,
we already have perf_sample_data-ip initialized if PERF_SAMPLE_IP.
Signed-off-by: Oleg Nesterov
* Oleg Nesterov o...@redhat.com [2013-04-09 15:33:33]:
On 04/07, Srikar Dronamraju wrote:
* Oleg Nesterov o...@redhat.com [2013-04-01 18:08:51]:
diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c
index e91a354..db2718a 100644
--- a/kernel/trace/trace_uprobe.c
* Oleg Nesterov o...@redhat.com [2013-04-09 21:32:35]:
Change uprobe_trace_print() and uprobe_perf_print() to check
is_ret_probe() and fill ring_buffer_event accordingly.
Also change uprobe_trace_func() and uprobe_perf_func() to not
_print() if is_ret_probe() is true. Note that we keep
On Sat, Apr 13, 2013 at 12:51 AM, Rafael J. Wysocki r...@sisk.pl wrote:
On Friday, April 12, 2013 11:08:37 PM Sedat Dilek wrote:
On Fri, Apr 12, 2013 at 6:27 PM, Sedat Dilek sedat.di...@gmail.com wrote:
On Fri, Apr 12, 2013 at 5:45 PM, Sedat Dilek sedat.di...@gmail.com wrote:
On Fri, Apr 12,
* Oleg Nesterov o...@redhat.com [2013-04-09 22:13:02]:
On 04/09, Oleg Nesterov wrote:
Should we a check here before using top most ri.
What if the application had done a longjmp and the trampoline he hit
corresponds to something thats below in the stack?
Not sure if this what
On Fri, Apr 12, 2013 at 09:34:13AM -0600, Stephen Warren wrote:
On 04/12/2013 08:58 AM, Jay Agarwal wrote:
err = regulator_disable(pcie-pex_clk_supply);
if (err 0)
- dev_err(pcie-dev, failed to disable pex-clk regulator:
%d\n,
+ dev_warn(pcie-dev, failed to disable
Hi,
I rebased the work on top of -next and I applied a Jan's comment about
__sb_start_write.
I did some basic tests and they are ok.
Open points:
- without change mnt_want_write several paths are still blocking paths;
- page_mkwrite still call blocking variant of __sb_start_write.
Any comments
Added a new enum to decide if we want to sleep in uninterruptible or
killable state or we want simply to return immediately.
Signed-off-by: Marco Stornelli marco.storne...@gmail.com
---
fs/super.c | 24 ++--
include/linux/fs.h | 19 +--
2 files
Replace file_start_write with file_start_write_killable where
possible.
Signed-off-by: Marco Stornelli marco.storne...@gmail.com
---
drivers/block/loop.c |4 +++-
fs/aio.c |7 +--
fs/coda/file.c |4 +++-
fs/read_write.c | 28 +---
Replace sb_start_write with sb_start_write_killable where
possible.
Signed-off-by: Marco Stornelli marco.storne...@gmail.com
---
fs/open.c |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/fs/open.c b/fs/open.c
index 8c74100..d621d76 100644
--- a/fs/open.c
+++
The following series implements four block ciphers - Blowfish, Twofish, Serpent
and Camellia - using AVX2 instruction set. This work on AVX2 implementations
started over year ago and have been available at
https://github.com/jkivilin/crypto-avx2
The Serpent and Camellia implementations
Signed-off-by: Jussi Kivilinna jussi.kivili...@iki.fi
---
crypto/testmgr.h | 1100 --
1 file changed, 1062 insertions(+), 38 deletions(-)
diff --git a/crypto/testmgr.h b/crypto/testmgr.h
index d503660..dc2c054 100644
--- a/crypto/testmgr.h
+++
Patch adds AVX2/x86-64 implementation of Blowfish cipher, requiring 32 parallel
blocks for input (256 bytes). Table look-ups are performed using vpgatherdd
instruction directly from vector registers and thus should be faster than
earlier implementations.
Signed-off-by: Jussi Kivilinna
Patch adds AVX2/x86-64 implementation of Twofish cipher, requiring 16 parallel
blocks for input (256 bytes). Table look-ups are performed using vpgatherdd
instruction directly from vector registers and thus should be faster than
earlier implementations. Implementation also uses 256-bit wide YMM
Patch adds AVX2/x86-64 implementation of Serpent cipher, requiring 16 parallel
blocks for input (256 bytes). Implementation is based on the AVX implementation
and extends to use the 256-bit wide YMM registers. Since serpent does not use
table look-ups, this implementation should be close to two
Signed-off-by: Jussi Kivilinna jussi.kivili...@iki.fi
---
crypto/tcrypt.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c
index 24ea7df..66d254c 100644
--- a/crypto/tcrypt.c
+++ b/crypto/tcrypt.c
@@ -1768,6 +1768,21 @@ static int
On Wed, 2013-03-27 at 07:57 -0400, Chris Ball wrote:
If the delay's significant, I agree with you and will revert this patch.
The patch was reverted. The problem is back. Filed bug:
https://bugzilla.kernel.org/show_bug.cgi?id=56561
A possible solution is to make card a separate device (now only
The pm2301-charger driver implements runtime pm and at the same time uses the
legacy pm callbacks for suspend and resume. This does not work since the I2C
core wont look at the legacy pm callbacks if a driver has the 'pm' field set.
This patch fixes it by moving over to dev_pm_ops for
Hello,
This morning I did a luksOpen on an external harddisk and saw:
# cryptsetup luksOpen /dev/sde1 crypto2
Enter passphrase for /dev/sde1:
semid 557063: semop failed for cookie 0xd4dd6db: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by
cookie
Dear Justin,
looking at the example at
http://www.lanedo.com/~aleksander/fanotify/fanotify-example.c
the large file support is enabled by passing O_LARGEFILE to fanotify_init:
if ((fanotify_fd = fanotify_init (FAN_CLOEXEC,
O_RDONLY | O_CLOEXEC |
Sure, sorry about that. I was hoping the GUID would be enough. I'll see
what I can come up with.
On 04/12/2013 09:35 PM, Matthew Garrett wrote:
On Sat, 2013-04-13 at 03:31 +0200, Pali Rohár wrote:
all Fn keys, wifi switch, web and mute buttons not working anymore
on my notebook HP EliteBook
On Thu, Apr 11, 2013 at 11:37 AM, Neil Zhang zhan...@marvell.com wrote:
From: Chao Xie chao@marvell.com
PXA988 will use GIC as its interrupt controller, and ICU is used as wakeup
logic. When AP subsystem is powered off, GIC will lose its context, the
PMU will need ICU to wakeup the AP
Hi,
On Sat, Apr 13 2013, Sergey Yanovich wrote:
On Wed, 2013-03-27 at 07:57 -0400, Chris Ball wrote:
If the delay's significant, I agree with you and will revert this patch.
The patch was reverted. The problem is back. Filed bug:
https://bugzilla.kernel.org/show_bug.cgi?id=56561
A possible
On Sat, 2013-04-13 at 13:56 +0200, Ulf Hansson wrote:
Den 13 apr 2013 12:49 skrev Sergey Yanovich ynv...@gmail.com:
A possible solution is to make card a separate device (now only the
host
is a device). In this case, the probing could be done asynchronously
without breaking the
Adding in cc: lkml
Il 13/04/2013 14:14, Marco Stornelli ha scritto:
Hi,
I was seeing the code of __mm_populate (in -next) and I've got a doubt
about the return value. The function __mlock_posix_error_return should
return a proper error for mlock, converting the return value from
On Mon, Mar 4, 2013 at 1:46 PM, Tony Lindgren t...@atomide.com wrote:
drivers/gpu/drm/tilcdc/tilcdc_slave.o:(.data+0x54): multiple definition of
`__mod_of_device_table'
drivers/gpu/drm/tilcdc/tilcdc_tfp410.o:(.data+0x54): first defined here
drivers/gpu/drm/tilcdc/tilcdc_panel.o:(.data+0x54):
On Thu, Apr 11, 2013 at 11:37 AM, Neil Zhang zhan...@marvell.com wrote:
Move some of the function declaration to head file.
Signed-off-by: Neil Zhang zhan...@marvell.com
Signed-off-by: Chao Xie chao@marvell.com
---
arch/arm/mach-mmp/common.h |3 +++
arch/arm/mach-mmp/mmp-dt.c |
101 - 200 of 332 matches
Mail list logo
