Set cmd_per_lun to reflect value supported by the Host.
In this version of the patch I have addressed comments from
Christoph Hellwig h...@infradead.org
Signed-off-by: K. Y. Srinivasan k...@microsoft.com
Cc: stable@vger.kernel.org
---
drivers/scsi/storvsc_drv.c |2 +-
1 files changed, 1
On Mon, 2014-07-07 at 16:55 +0200, Mike Galbraith wrote:
Seems the below stable tagged rtmutex fixes won't go further back than
3.14 unless someone does the leg work of making them applicable.
Ergo, this series contains..
397335f0 rtmutex: Fix deadlock detector for real
82084984 rtmutex:
Hi Viresh:
I have verified this patch, all the issues I reported disappeared.
Thanks for the quick fix.
Best Regards
-Original Message-
From: Viresh Kumar [mailto:viresh.ku...@linaro.org]
Sent: Thursday, July 10, 2014 1:19 PM
To: r...@rjwysocki.net
Cc:
On 10 July 2014 12:38, Bu, Yitian y...@qti.qualcomm.com wrote:
Hi Viresh:
I have verified this patch, all the issues I reported disappeared.
Thanks for the quick fix.
Please don't top post. http://en.wikipedia.org/wiki/Posting_style
Rafael would be adding your:
Tested-by: Bu Yitian
-Original Message-
From: Viresh Kumar [mailto:viresh.ku...@linaro.org]
Sent: Thursday, July 10, 2014 3:10 PM
To: Bu, Yitian
Cc: r...@rjwysocki.net; linaro-ker...@lists.linaro.org; linux-
p...@vger.kernel.org; arvind.chau...@arm.com; sriva...@mit.edu;
skan...@codeaurora.org; Stable
On Wed, 9 Jul 2014, Sasha Levin wrote:
On 07/09/2014 08:47 AM, Sasha Levin wrote:
So it would again help to see stacks of other tasks, to see who holds
the i_mutex and where it's stuck...
The stacks print got garbled due to having large amount of tasks and too
low of a
console
On Wed, Jul 09, 2014 at 12:18:36PM -0400, Jason Cooper wrote:
On Sat, Jul 05, 2014 at 11:04:53AM +0530, Amit Shah wrote:
The hwrng core asks for random data in the hwrng_register() call itself
from commit d9e7972619. This doesn't play well with virtio -- the
DRIVER_OK bit is only set by
From: Todd Fujinaka todd.fujin...@intel.com
On some devices, the internal PLL circuit occasionally provides the
wrong clock frequency after power up. The probability of failure is less
than one failure per 1000 power cycles. When the failure occurs, the
internal clock frequency is around 1/20 of
From: Jeff Kirsher jeffrey.t.kirs...@intel.com
Date: Thu, 10 Jul 2014 01:47:15 -0700
From: Todd Fujinaka todd.fujin...@intel.com
On some devices, the internal PLL circuit occasionally provides the
wrong clock frequency after power up. The probability of failure is less
than one failure per
On (Wed) 09 Jul 2014 [12:18:36], Jason Cooper wrote:
On Sat, Jul 05, 2014 at 11:04:53AM +0530, Amit Shah wrote:
The hwrng core asks for random data in the hwrng_register() call itself
from commit d9e7972619. This doesn't play well with virtio -- the
DRIVER_OK bit is only set by virtio core
On Mon, Jul 07, 2014 at 11:52:41AM +0300, Cristian Stoica wrote:
This patch fixes a memory leak that appears when caam_jr module is unloaded.
Cc: stable@vger.kernel.org # 3.13+
Signed-off-by: Cristian Stoica cristian.sto...@freescale.com
Patch applied.
--
Email: Herbert Xu
On (Thu) 10 Jul 2014 [16:45:14], Herbert Xu wrote:
On Wed, Jul 09, 2014 at 12:18:36PM -0400, Jason Cooper wrote:
On Sat, Jul 05, 2014 at 11:04:53AM +0530, Amit Shah wrote:
The hwrng core asks for random data in the hwrng_register() call itself
from commit d9e7972619. This doesn't play
On Wed, Jul 09, 2014 at 10:36:26PM +, KY Srinivasan wrote:
Ok; I am concerned about older kernels that do not have no_write_same flag.
I suppose I can work directly with these Distros and give them a choice:
either implement
the no_write_same flag or filter the command in our driver. I
The hwrng core asks for random data in the hwrng_register() call itself
from commit d9e7972619. This doesn't play well with virtio -- the
DRIVER_OK bit is only set by virtio core on a successful probe, and
we're not yet out of our probe routine when this call is made. This
causes the host to not
Commit d9e7972619334 hwrng: add randomness to system from rng sources
added a call to rng_get_data() from the hwrng_register() function.
However, some rng devices need initialization before data can be read
from them.
This commit makes the call to rng_get_data() depend on no init fn
pointer being
On Wed, Jul 09, 2014 at 06:40:09PM +, KY Srinivasan wrote:
On Tue, Jul 08, 2014 at 05:46:51PM -0700, K. Y. Srinivasan wrote:
Correctly set SRB flags for all valid I/O directions. Some IHV drivers
on the Windows host require this.
What are IHV drivers?
If the target is a SAN
default:
vm_srb-data_in = UNKNOWN_TYPE;
- vm_srb-win8_extension.srb_flags = 0;
+ vm_srb-win8_extension.srb_flags |= (SRB_FLAGS_DATA_IN |
+ SRB_FLAGS_DATA_OUT);
This would usually be a command that
- .cmd_per_lun = 1,
+ .cmd_per_lun = 255,
.can_queue =STORVSC_MAX_IO_REQUESTS*STORVSC_MAX_TARGETS,
slave_configure immediately adjusts this down to STORVSC_MAX_IO_REQUESTS
(250), any reson to start out with the magic 255 here?
--
To unsubscribe from
From: Stefan Assmann sassm...@kpanic.de
To properly re-initialize SR-IOV it is necessary to reset the device
even if it is already down. Not doing this may result in Tx unit hangs.
Cc: stable stable@vger.kernel.org
Signed-off-by: Stefan Assmann sassm...@kpanic.de
Tested-by: Aaron Brown
On Thu, Jul 10, 2014 at 03:42:34PM +0530, Amit Shah wrote:
Commit d9e7972619334 hwrng: add randomness to system from rng sources
added a call to rng_get_data() from the hwrng_register() function.
However, some rng devices need initialization before data can be read
from them.
This commit
On 10 July 2014 16:45, Srivatsa S. Bhat sriva...@mit.edu wrote:
Looks good to me. But I think it would be better to move the invocation of
kobject_move() to update_policy_cpu() itself, so that update_policy_cpu()
will do all the work involved in updating the policy-cpu, as its name
suggests.
On 07/10/2014 10:49 AM, Viresh Kumar wrote:
This is only relevant to implementations with multiple clusters, where
clusters
have separate clock lines but all CPUs within a cluster share it.
Consider a dual cluster platform with 2 cores per cluster. During suspend we
start offlining CPUs
On 07/10/2014 04:50 PM, Viresh Kumar wrote:
On 10 July 2014 16:45, Srivatsa S. Bhat sriva...@mit.edu wrote:
Looks good to me. But I think it would be better to move the invocation of
kobject_move() to update_policy_cpu() itself, so that update_policy_cpu()
will do all the work involved in
On Wed, Jul 02, 2014 at 09:45:44AM +0200, Philipp Hahn wrote:
Hello Wei Liu,
On 27.06.2014 20:24, Philipp Hahn wrote:
On 27.06.2014 19:48, Philipp Hahn wrote: I guess we found the problem
ourselves: For thus removed skb's the
reference counter on the associated vif was not decremented,
On 10 July 2014 16:52, Srivatsa S. Bhat sriva...@mit.edu wrote:
I know.. That's why it makes even more sense to consolidate all the
work into one function. We can restructure cpufreq_nominate_new_policy_cpu()
such that the kobject_move() can be moved to update_policy_cpu().
Done.
--
To
On 07/10/2014 03:37 AM, Hugh Dickins wrote:
I do think that the most useful thing you could do at the moment,
is to switch away from running trinity on -next temporarily, and
run it instead on Linus's current git or on 3.16-rc4, but with
f00cdc6df7d7 reverted and my take 2 inserted in its
On 02/13/2014 12:55 PM, Jakub Jelinek wrote:
On Thu, Feb 13, 2014 at 03:37:08AM -0800, tip-bot for Steven Noonan wrote:
Commit-ID: a9f180345f5378ac87d80ed0bea55ba421d83859
Gitweb:
http://git.kernel.org/tip/a9f180345f5378ac87d80ed0bea55ba421d83859
Author: Steven Noonan
在 2014年7月10日，20:41，Viresh Kumar viresh.ku...@linaro.org 写道：
This is only relevant to implementations with multiple clusters, where
clusters
have separate clock lines but all CPUs within a cluster share it.
Consider a dual cluster platform with 2 cores per cluster. During suspend we
On Thu, Jul 10, 2014 at 08:12:18AM +0200, Mike Galbraith wrote:
On Mon, 2014-07-07 at 16:55 +0200, Mike Galbraith wrote:
Seems the below stable tagged rtmutex fixes won't go further back than
3.14 unless someone does the leg work of making them applicable.
Ergo, this series contains..
On Thu, 10 Jul 2014 09:16:00 -0700
Greg Kroah-Hartman gre...@linuxfoundation.org wrote:
On Thu, Jul 10, 2014 at 08:12:18AM +0200, Mike Galbraith wrote:
On Mon, 2014-07-07 at 16:55 +0200, Mike Galbraith wrote:
Seems the below stable tagged rtmutex fixes won't go further back than
3.14
On 07/10/2014 08:46 AM, Sasha Levin wrote:
On 07/10/2014 03:37 AM, Hugh Dickins wrote:
I do think that the most useful thing you could do at the moment,
is to switch away from running trinity on -next temporarily, and
run it instead on Linus's current git or on 3.16-rc4, but with
On Thu, 2014-07-10 at 09:16 -0700, Greg Kroah-Hartman wrote:
On Thu, Jul 10, 2014 at 08:12:18AM +0200, Mike Galbraith wrote:
On Mon, 2014-07-07 at 16:55 +0200, Mike Galbraith wrote:
Seems the below stable tagged rtmutex fixes won't go further back than
3.14 unless someone does the leg
On Thu, 10 Jul 2014, Sasha Levin wrote:
On 07/10/2014 08:46 AM, Sasha Levin wrote:
On 07/10/2014 03:37 AM, Hugh Dickins wrote:
I do think that the most useful thing you could do at the moment,
is to switch away from running trinity on -next temporarily, and
run it instead on Linus's
On Thu, 10 Jul 2014 19:40:21 +0200
Mike Galbraith umgwanakikb...@gmail.com wrote:
On Thu, 2014-07-10 at 09:16 -0700, Greg Kroah-Hartman wrote:
On Thu, Jul 10, 2014 at 08:12:18AM +0200, Mike Galbraith wrote:
On Mon, 2014-07-07 at 16:55 +0200, Mike Galbraith wrote:
Seems the below
On Thu, 10 Jul 2014, Sasha Levin wrote:
On 07/10/2014 01:55 PM, Hugh Dickins wrote:
And finally, (not) holding the i_mmap_mutex:
I don't understand what prompts you to show this particular task.
I imagine the dump shows lots of other tasks which are waiting to get an
i_mmap_mutex, and
Commit 75b57ecf9 refactored device tree nodes to use kobjects such that they
can be exposed via /sysfs. A secondary commit 0829f6d1f furthered this rework
by moving the kobect initialization logic out of of_node_add into its own
of_node_init function. The inital commit removed the existing
Commit 75b57ecf9 refactored device tree nodes to use kobjects such that they
can be exposed via /sysfs. A secondary commit 0829f6d1f furthered this rework
by moving the kobect initialization logic out of of_node_add into its own
of_node_init function. The inital commit removed the existing
On Thu, 10 Jul 2014, Steven Rostedt wrote:
On Thu, 10 Jul 2014 19:40:21 +0200
Mike Galbraith umgwanakikb...@gmail.com wrote:
On Thu, 2014-07-10 at 09:16 -0700, Greg Kroah-Hartman wrote:
On Thu, Jul 10, 2014 at 08:12:18AM +0200, Mike Galbraith wrote:
On Mon, 2014-07-07 at 16:55
On 07/10/2014 02:52 PM, Hugh Dickins wrote:
On Thu, 10 Jul 2014, Sasha Levin wrote:
On 07/10/2014 01:55 PM, Hugh Dickins wrote:
And finally, (not) holding the i_mmap_mutex:
I don't understand what prompts you to show this particular task.
I imagine the dump shows lots of other tasks
On Thu, 10 Jul 2014, Sasha Levin wrote:
On 07/10/2014 02:52 PM, Hugh Dickins wrote:
On Thu, 10 Jul 2014, Sasha Levin wrote:
On 07/10/2014 01:55 PM, Hugh Dickins wrote:
And finally, (not) holding the i_mmap_mutex:
I don't understand what prompts you to show this particular task.
I
On 07/10/2014 03:06 PM, Hugh Dickins wrote:
On Thu, 10 Jul 2014, Sasha Levin wrote:
On 07/10/2014 02:52 PM, Hugh Dickins wrote:
On Thu, 10 Jul 2014, Sasha Levin wrote:
On 07/10/2014 01:55 PM, Hugh Dickins wrote:
And finally, (not) holding the i_mmap_mutex:
I don't understand
On 07/10/2014 08:12 AM, Bu, Yitian wrote:
在 2014年7月10日，20:41，Viresh Kumar viresh.ku...@linaro.org 写道：
This is only relevant to implementations with multiple clusters, where
clusters
have separate clock lines but all CPUs within a cluster share it.
Consider a dual cluster platform with
From: Jeff Kirsher jeffrey.t.kirs...@intel.com
Date: Thu, 10 Jul 2014 03:29:39 -0700
From: Stefan Assmann sassm...@kpanic.de
To properly re-initialize SR-IOV it is necessary to reset the device
even if it is already down. Not doing this may result in Tx unit hangs.
Cc: stable
On Thu, 10 Jul 2014, Sasha Levin wrote:
On 07/10/2014 03:06 PM, Hugh Dickins wrote:
On Thu, 10 Jul 2014, Sasha Levin wrote:
On 07/10/2014 02:52 PM, Hugh Dickins wrote:
On Thu, 10 Jul 2014, Sasha Levin wrote:
On 07/10/2014 01:55 PM, Hugh Dickins wrote:
And finally, (not)
On 07/10/2014 01:50 PM, Tyrel Datwyler wrote:
Commit 75b57ecf9 refactored device tree nodes to use kobjects such that they
can be exposed via /sysfs. A secondary commit 0829f6d1f furthered this rework
by moving the kobect initialization logic out of of_node_add into its own
of_node_init
On 07/09/2014 10:35 PM, Daniel Vetter wrote:
This reverts commit 773875bfb6737982903c42d1ee88cf60af80089c.
It is very much needed and the lack of dithering has been reported by
a large list of people with various gen2/3 hardware.
Also, the original patch was complete non-sense since the
On Thu, 10 Jul 2014, Hugh Dickins wrote:
I'll pore over the new log. It does help to know that its base kernel
is more stable: thanks so much. But whether I can work out any more...
Actually, today's log is not much use to me: for a tenth of a second
it just shows NNN printk messages
-Original Message-
From: James Bottomley [mailto:jbottom...@parallels.com]
Sent: Wednesday, July 9, 2014 3:27 PM
To: KY Srinivasan
Cc: linux-ker...@vger.kernel.org; m...@mkp.net; h...@infradead.org;
de...@linuxdriverproject.org; a...@canonical.com; stable@vger.kernel.org;
-Original Message-
From: Christoph Hellwig [mailto:h...@infradead.org]
Sent: Thursday, July 10, 2014 3:25 AM
To: KY Srinivasan
Cc: linux-ker...@vger.kernel.org; de...@linuxdriverproject.org;
oher...@suse.com; jbottom...@parallels.com; h...@infradead.org;
jasow...@redhat.com;
On Thu, 2014-07-10 at 21:02 +, KY Srinivasan wrote:
-Original Message-
From: James Bottomley [mailto:jbottom...@parallels.com]
Sent: Wednesday, July 9, 2014 3:27 PM
To: KY Srinivasan
Cc: linux-ker...@vger.kernel.org; m...@mkp.net; h...@infradead.org;
-Original Message-
From: Christoph Hellwig [mailto:h...@infradead.org]
Sent: Thursday, July 10, 2014 3:17 AM
To: KY Srinivasan
Cc: Christoph Hellwig; linux-ker...@vger.kernel.org;
de...@linuxdriverproject.org; oher...@suse.com;
jbottom...@parallels.com; jasow...@redhat.com;
This is a note to let you know that I've just added the patch titled
serial: core: Preserve termios c_cflag for console resume
to my tty git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
in the tty-next branch.
The patch will show up in the
This is a note to let you know that I've just added the patch titled
serial: Test for no tx data on tx restart
to my tty git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
in the tty-linus branch.
The patch will show up in the next release of
在 2014年7月11日，3:26，Saravana Kannan skan...@codeaurora.org 写道：
On 07/10/2014 08:12 AM, Bu, Yitian wrote:
在 2014年7月10日，20:41，Viresh Kumar viresh.ku...@linaro.org 写道：
This is only relevant to implementations with multiple clusters, where
clusters
have separate clock lines but all CPUs
Commit 0e2e24e5dc(aio: fix kernel memory disclosure in io_getevents()
introduced in v3.10) is the same as bee3f7b818(aio: fix kernel memory
disclosure in io_getevents() introduced in v3.10), it seems a mistake
here, so revert the duplicate one.
Signed-off-by: Gu Zheng guz.f...@cn.fujitsu.com
---
55 matches
Mail list logo
