2017-09-19 20:36 GMT+09:00 Cao jin :
> It has:
> 1. Move comments close to what it want to comment.
> 2. Comments cleanup & improvement.
>
> Signed-off-by: Cao jin
> ---
Applied to linux-kbuild/kbuild.
--
Best Regards
Masahiro Yamada
Add a glossary of terms for V4L2, as several concepts are complex
enough to cause misunderstandings.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/v4l/glossary.rst | 167 ++
Documentation/media/uapi/v4l/v4l2.rst | 1 +
2 files changed, 168 in
When we added support for omap3, back in 2010, we added a new
type of V4L2 devices that aren't fully controlled via the V4L2
device node.
Yet, we have never clearly documented in the V4L2 specification
the differences between the two types.
Let's document them based on the the current implementat
The documentation doesn't mention if vdev-centric hardware
control would have subdev API or not.
Add a notice about that, reflecting the current status, where
three drivers use it, in order to support some subdev-specific
controls.
Signed-off-by: Mauro Carvalho Chehab
Acked-by: Sakari Ailus
Ack
As both vdev-centric and MC-centric devices may implement the
same APIs, we need a flag to allow userspace to distinguish
between them.
Signed-off-by: Mauro Carvalho Chehab
Acked-by: Sakari Ailus
Acked-by: Hans Verkuil
---
Documentation/media/uapi/v4l/open.rst| 7 +++
Documenta
Right now, only kAPI documentation describes the device naming.
However, such description is needed at the uAPI too. Add it,
and describe how to get an unique identify for a given device.
Signed-off-by: Mauro Carvalho Chehab
Acked-by: Hans Verkuil
Acked-by: Sakari Ailus
---
Documentation/media
minor numbers use to range between 0 to 255, but that
was changed a long time ago. While it still applies when
CONFIG_VIDEO_FIXED_MINOR_RANGES, when the minor number is
dynamically allocated, this may not be true. In any case,
this is not relevant, as udev will take care of it.
So, remove this use
As we now have a glossary, some terms used on open.rst
require adjustments.
Acked-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/v4l/open.rst | 25 +
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/Documentation/media/u
On Kernel 2.6.39, the omap3 driver was introduced together with a new way
to control complex V4L2 devices used on embedded systems, but this was
never documented, as the original idea were to have "soon" support for
standard apps to use it as well, via libv4l, but that didn't happen so far.
Also,
Hi Alan,
On Tue, Oct 10, 2017 at 10:08:40AM +0100, Alan Cox wrote:
> > Would it make sense to first get the other drivers to upstream and
> > then see what's the status of atomisp?
>
> Agreed
>
> > the board specific information from firmware is conveyed to the
> > sensor drivers will change to
On 10/09, Andrew Morton wrote:
>
> > @@ -240,17 +230,11 @@ void zap_pid_ns_processes(struct pid_namespace
> > *pid_ns)
> > *
> > */
> > read_lock(&tasklist_lock);
> > - nr = next_pidmap(pid_ns, 1);
> > - while (nr > 0) {
> > - rcu_read_lock();
> > -
> > - task
2017-10-04 12:56 GMT+09:00 Masahiro Yamada :
> Since commit 5e53879008b9 ("sparc,sparc64: unify Makefile"), hdr-arch
> and SRCARCH always match.
>
> Signed-off-by: Masahiro Yamada
Applied to linux-kbuild/kbuild.
--
Best Regards
Masahiro Yamada
2017-10-04 12:56 GMT+09:00 Masahiro Yamada :
> The first "_all" occurrence around line 120 is only visible when
> KBUILD_SRC is unset.
>
> If O=... is specified, the working directory is relocated, then the
> only second occurrence around line 193 is visible, that is not set
> to PHONY.
>
> Move th
On Tue 10-10-17 19:58:53, Tetsuo Handa wrote:
> Commit 5d17a73a2ebeb8d1 ("vmalloc: back off when the current task is
> killed") revealed two bugs [1] [2] that were not ready to fail vmalloc()
> upon SIGKILL. But since the intent of that commit was to avoid unlimited
> access to memory reserves, we
On Mon, Oct 09, 2017 at 04:18:10PM -0700, Darren Hart wrote:
> I'm not sure how we would deal with it in the trees. Best to note this during
> the merge window - whichever goes in second. Test merge will identify the
> merge
> conflict, and we can include a note to Linus on the preference.
That
On Tue, Oct 10, 2017 at 11:23:32AM +0100, Mark Rutland wrote:
> On Tue, Oct 10, 2017 at 11:15:39AM +0100, Sudeep Holla wrote:
> > (+Mark, Grant)
> >
> > On 09/10/17 18:16, Chris Metcalf wrote:
> > > The Mellanox BlueField SoC firmware supports a safe upgrade mode as
> > > part of the flow where u
On Tue, Oct 10, 2017 at 05:14:08PM +0800, Dongli Zhang wrote:
> After guest live migration on xen, steal time in /proc/stat
> (cpustat[CPUTIME_STEAL]) might decrease because steal returned by
> paravirt_steal_clock() might be less than this_rq()->prev_steal_time.
So why not fix paravirt_steal_cloc
On 10/10, Oleg Nesterov wrote:
>
> On 10/09, Tycho Andersen wrote:
> > Hi,
> >
> > It looks like eb23aa031 ("exec: binfmt_misc: remove the confusing
> > e->interp_file != NULL checks") uncovered a bug for me (see the trace below,
> > which I'm afraid isn't very helpful).
>
> Well, I think this comm
Michal Hocko writes:
> From: Michal Hocko
>
> Memory offlining can fail just too eagerly under a heavy memory pressure.
>
> [ 5410.336792] page:ea22a646bd00 count:255 mapcount:252
> mapping:88ff926c9f38 index:0x3
> [ 5410.336809] flags: 0x9855fe40010048(uptodate|active|mappedtodisk)
> [
On Sun, Oct 08, 2017 at 11:33:31PM +0100, Christos Gkekas wrote:
> Variable did_old is unsigned so checking whether it is greater or equal
> to zero is not necessary.
>
> Signed-off-by: Christos Gkekas
> ---
> drivers/iommu/intel-iommu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
A
On 21 September 2017 at 11:44, Adrian Hunter wrote:
> On 21/09/17 12:01, Ulf Hansson wrote:
>> On 13 September 2017 at 13:40, Adrian Hunter wrote:
>>> Hi
>>>
>>> Here is V8 of the hardware command queue patches without the software
>>> command queue patches, now using blk-mq and now with blk-mq s
FYI, we noticed the following commit (built with gcc-4.8):
commit: 81d387190039c14edac8de2b3ec789beb899afd9 ("x86/kconfig: Consolidate
unwinders into multiple choice selection")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: qemu-syste
On Mon, Oct 09, 2017 at 01:10:01AM +0900, Masahiro Yamada wrote:
> Reducing the header dependency will help for speeding the kernel
> build, suppressing unnecessary recompile of objects during
> git-bisect'ing, etc.
Well, does it? You could provide measurements showing before/after
time to compil
On Tue, 10 Oct 2017 13:20:14 +0200,
Andrey Konovalov wrote:
>
> On Tue, Oct 10, 2017 at 12:10 AM, Takashi Iwai wrote:
> > On Mon, 09 Oct 2017 19:50:39 +0200,
> > Andrey Konovalov wrote:
> >>
> >> Hi!
> >>
> >> I've got the following report while fuzzing the kernel with syzkaller.
> >>
> >> On com
On 2017/10/10 19:33, Peter Zijlstra wrote:
No, this _cannot_ be right. The whole point of the @task argument was to
deliver the event multiple times -- maybe not to the same event, but it
needs to be delivered multiple times in some cases. Therefore this is
broken.
But now you've got me looking
On 10/10/2017 10:06 AM, Prasad Sodagudi wrote:
> In LLVM __ubsan_handle_type_mismatch handler is renamed to
> __ubsan_handle_type_mismatch_v1. Add support for
> __ubsan_handle_type_mismatch_v1 handler to avoid compilation
> issues with latest llvm tool chain. Also keeping
> __ubsan_handle_type_mis
On Fri, Oct 06, 2017 at 05:51:31PM +0200, srinivas.kandaga...@linaro.org wrote:
> From: Sagar Dharia
>
> Slimbus devices use value-element, and information elements to
> control device parameters (e.g. value element is used to represent
> gain for codec, information element is used to represent i
On Mon, Oct 09, 2017 at 02:52:53PM -0700, David Rientjes wrote:
> On Thu, 5 Oct 2017, Roman Gushchin wrote:
>
> > Traditionally, the OOM killer is operating on a process level.
> > Under oom conditions, it finds a process with the highest oom score
> > and kills it.
> >
> > This behavior doesn't
On Tue, Oct 10, 2017 at 12:58 PM, Leif Lindholm
wrote:
>
> On Tue, Oct 10, 2017 at 11:23:32AM +0100, Mark Rutland wrote:
>> On Tue, Oct 10, 2017 at 11:15:39AM +0100, Sudeep Holla wrote:
>> > (+Mark, Grant)
>> >
>> > On 09/10/17 18:16, Chris Metcalf wrote:
>> > > The Mellanox BlueField SoC firmware
On 2017/10/10 下午5:00, Liang Chen wrote:
> mutex_destroy does nothing most of time, but it's better to call
> it to make the code future proof and it also has some meaning
> for like mutex debug.
>
> As Coly pointed out in a previous review, bcache_exit() may not be
> able to handle all the referen
On 10/10/2017 02:46, Ming Lei wrote:
> > I tested this series for the SAS controller on HiSilicon hip07 platform as I
> > am interested in enabling MQ for this driver. Driver is
> > ./drivers/scsi/hisi_sas/.
> >
> > So I found that that performance is improved when enabling default SCSI_MQ
> > wi
On Tue 10-10-17 23:05:08, Michael Ellerman wrote:
> Michal Hocko writes:
>
> > From: Michal Hocko
> >
> > Memory offlining can fail just too eagerly under a heavy memory pressure.
> >
> > [ 5410.336792] page:ea22a646bd00 count:255 mapcount:252
> > mapping:88ff926c9f38 index:0x3
> > [ 54
On 10/10/17 15:12, Ulf Hansson wrote:
> On 21 September 2017 at 11:44, Adrian Hunter wrote:
>> On 21/09/17 12:01, Ulf Hansson wrote:
>>> On 13 September 2017 at 13:40, Adrian Hunter
>>> wrote:
Hi
Here is V8 of the hardware command queue patches without the software
command qu
On 10/10/2017 07:08 PM, Tetsuo Handa wrote:
Wei Wang wrote:
On 10/09/2017 11:20 PM, Michael S. Tsirkin wrote:
On Sat, Sep 30, 2017 at 12:05:52PM +0800, Wei Wang wrote:
+static inline void xb_set_page(struct virtio_balloon *vb,
+ struct page *page,
+
On Mon 2017-10-02 11:56:48, Joe Lawrence wrote:
> When an incoming module is considered for livepatching by
> klp_module_coming(), it iterates over multiple patches and multiple
> kernel objects in this order:
>
> list_for_each_entry(patch, &klp_patches, list) {
> klp_for_each_
Hi John,
On Tue, Oct 10, 2017 at 01:24:52PM +0100, John Garry wrote:
> It's using cfq (for non-mq) and mq-deadline (obviously for mq).
Please be aware that cfq and mq-deadline are _not_ comparable, for a realistic
comparasion please use deadline and mq-deadline or cfq and bfq.
> root@(none)$ pwd
Thanks for the review comments.
On 10/10/17 11:05, Charles Keepax wrote:
On Fri, Oct 06, 2017 at 05:51:30PM +0200, srinivas.kandaga...@linaro.org wrote:
From: Sagar Dharia
SLIMbus (Serial Low Power Interchip Media Bus) is a specification
developed by MIPI (Mobile Industry Processor Interface)
On Tue, Oct 10, 2017 at 12:50 PM, Oleg Nesterov wrote:
> On 10/09, Andrew Morton wrote:
>>
>> > @@ -240,17 +230,11 @@ void zap_pid_ns_processes(struct pid_namespace
>> > *pid_ns)
>> > *
>> > */
>> > read_lock(&tasklist_lock);
>> > - nr = next_pidmap(pid_ns, 1);
>> > - while (nr
Thanks for your review comments,
On 10/10/17 11:45, Vinod Koul wrote:
On Fri, Oct 06, 2017 at 05:51:30PM +0200, srinivas.kandaga...@linaro.org wrote:
From: Sagar Dharia
SLIMbus (Serial Low Power Interchip Media Bus) is a specification
developed by MIPI (Mobile Industry Processor Interface) al
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 529a86e063e9ff625c4ff247d8aa17d8072444fb
commit: d90cb7f852034e5bf50158b34047effa453a9836 drm/i915: Add SW_SYNC to our
recommend testing Kconfig
date: 8 weeks ago
config: x86_64-randconfig-s2-10101944 (att
> Il giorno 10 ott 2017, alle ore 14:34, Johannes Thumshirn
> ha scritto:
>
> Hi John,
>
> On Tue, Oct 10, 2017 at 01:24:52PM +0100, John Garry wrote:
>> It's using cfq (for non-mq) and mq-deadline (obviously for mq).
>
> Please be aware that cfq and mq-deadline are _not_ comparable, for a re
On Tuesday 19 September 2017 11:45 AM, Vignesh R wrote:
>
> This series adds support for TI ECAP PWM IP present in 66AK2G SoC.
> Resending based on today's linux-next.
>
>
> Vignesh R (3):
> ARM: dts: keystone-k2g: Add ECAP PWM DT nodes
> ARM: dts: keystone-k2g-evm: Enable PWM ECAP0
> AR
On 10/10/2017 21:26, Peng Hao wrote:
> When freeing mmapped kvm_run several pages, the pages will have page
> flags PG_dirty and PG_referenced. It will result to bad page report
> when allocating pages.
> I just encounter once like this;
> BUG: Bad page state in process qemu-system-x86 pfn:81fc5d
On Tue, Oct 10, 2017 at 12:59:26PM +0200, Ingo Molnar wrote:
>
> (Cc:-ed more gents involved in kernel/sched/cputime.c work. Full patch quoted
> below.)
>
> * Dongli Zhang wrote:
>
> > After guest live migration on xen, steal time in /proc/stat
> > (cpustat[CPUTIME_STEAL]) might decrease becau
On 10/10, Eryu Guan wrote:
>
> inode->i_private is assigned by a Node pointer only after
> registering a new binary format, so it could be NULL if we only
> mount binfmt_misc but don't register any format,
^
Not really, I 'think... I mean, the proble
Michal Hocko wrote:
> On Tue 10-10-17 19:58:53, Tetsuo Handa wrote:
> > Commit 5d17a73a2ebeb8d1 ("vmalloc: back off when the current task is
> > killed") revealed two bugs [1] [2] that were not ready to fail vmalloc()
> > upon SIGKILL. But since the intent of that commit was to avoid unlimited
> >
On Tue, Oct 10, 2017 at 10:54:14AM +0100, Mark Rutland wrote:
> On Mon, Oct 09, 2017 at 12:51:12PM -0700, Paul E. McKenney wrote:
> > On Mon, Oct 09, 2017 at 07:28:50PM +0100, Mark Rutland wrote:
> > > diff --git
> > > a/tools/testing/selftests/rcutorture/formal/srcu-cbmc/src/barriers.h
> > > b/t
On 10/07/2017 06:36 PM, Levin, Alexander (Sasha Levin) wrote:
> From: Jan Beulich
>
> [ Upstream commit 4fed1b125eb6252bde478665fc05d4819f774fa8 ]
>
> A negative return value indicates an error; in fact the function at
> present won't ever return zero.
>
> Signed-off-by: Jan Beulich
> Reviewed-by
On Tue, Oct 10, 2017 at 07:58:53PM +0900, Tetsuo Handa wrote:
> Commit 5d17a73a2ebeb8d1 ("vmalloc: back off when the current task is
> killed") revealed two bugs [1] [2] that were not ready to fail vmalloc()
> upon SIGKILL. But since the intent of that commit was to avoid unlimited
> access to memo
On Tue, Oct 10, 2017 at 02:42:01PM +0200, Stanislaw Gruszka wrote:
> > > + u64 steal, steal_time;
> > > + s64 steal_delta;
> > > +
> > > + steal_time = paravirt_steal_clock(smp_processor_id());
> > > + steal = steal_delta = steal_time - this_rq()->prev_steal_time;
>
SMBUS_BLOCK_DATA transactions might fail due to a race condition with
the IMC (Integrated Micro Controller), even when the IMC semaphore
is used.
This bug has been reported and confirmed by AMD, who suggested as a
solution an IMC firmware upgrade (obtained via BIOS update) and
disabling the IMC du
When both user ports are joined to the same bridge, the normal
HW MAC learning is enabled. This means that unicast traffic is forwarded
in HW.
If one of the user ports leave the bridge,
the ports goes back to the initial separated operation.
Port separation relies on disabled HW MAC learning. Hen
Prepare for next patch:
Move tag setup from lan9303_separate_ports() to new function
lan9303_setup_tagging()
Signed-off-by: Egil Hjelmeland
---
drivers/net/dsa/lan9303-core.c | 42 +-
1 file changed, 25 insertions(+), 17 deletions(-)
diff --git a/drivers/
This series add basic offloading of unicast traffic to the lan9303
DSA driver.
Review welcome!
Changes v1 -> v2:
- Patch 1: Codestyle linting.
- Patch 2: Remember SWE_PORT_STATE while not bridged.
Added constant LAN9303_SWE_PORT_MIRROR_DISABLED.
Egil Hjelmeland (2):
net: dsa: l
The core GICv4 code has been merged in 4.14, but there is some
additional nails to be hammered on that coffin, and this is what
this short series tries to achieve.
The first three patches have been posted before, and implement a
workaround for the HiSilicon Hip07 (aka D05) platform.
The following
Sending VINVALL to all ITSs is completely pointless, as all
we're trying to achieve is to tell the redistributor that
the property table for this VPE should be invalidated.
Let's issue the command on the first valid ITS and be done with it.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/irq-gi
As we're about to make use of the maximum number of ITSs in
a GICv4 system, let's make this value global (and rename it to
GICv4_ITS_LIST_MAX).
Signed-off-by: Marc Zyngier
---
drivers/irqchip/irq-gic-v3-its.c | 10 ++
include/linux/irqchip/arm-gic-v4.h | 6 ++
2 files changed, 8 i
We so far allocate the doorbell interrupts without taking any
special measure regarding the affinity of these interrupts. We
simply move them around as required when the vcpu gets scheduled
on a different CPU.
But that's counting without userspace (and the evil irqbalance) that
can try and move th
If the ITS stops processing commands, we're pretty much toasted
as we cannot update the configuration anymore (and we're not
even sure that the ITS still translates interrups).
If that happens, let's dump some basic information about the
state of affairs before moving on.
Signed-off-by: Marc Zyng
In order to be able to issue command variants depending on
how broken an ITS is, let's pass the its pointer to all
command building primitives.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/irq-gic-v3-its.c | 58 ++--
1 file changed, 38 insertions(+), 20 del
So far, we map all VPEs on all ITSs. While this is not wrong,
this is quite a big hammer, as moving a VPE around requires
all ITSs to be synchronized. Needles to say, this is an
expensive proposition.
Instead, let's switch to a mode where we issue VMAPP commands
only on ITSs that are actually invo
At boot time, we enumerate all the GICv4-capable ITSs, and build
a mask of the available ITSs. Take this opportunity to store
the ITS number in the its_node structure so that we can use it
at a later time.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/irq-gic-v3-its.c | 3 +++
1 file changed,
Currently, its_send_vmapp operates on all ITSs. As we're about
to try and limit the amount of commands we send to ITSs that are
not involved in dealing with a given VM, let's redefine that
primitive so that it takes a target ITS as a parameter.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/irq
Currently, its_send_vinvall operates on all ITSs. As we're about
to try and limit the amount of commands we send to ITSs that are
not involved in dealing with a given VM, let's redefine that
primitive so that it takes a target ITS as a parameter.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/i
On Tue, Oct 10, 2017 at 05:47:12AM -0700, Paul E. McKenney wrote:
> On Tue, Oct 10, 2017 at 10:54:14AM +0100, Mark Rutland wrote:
> > On Mon, Oct 09, 2017 at 12:51:12PM -0700, Paul E. McKenney wrote:
> > > On Mon, Oct 09, 2017 at 07:28:50PM +0100, Mark Rutland wrote:
> > > > diff --git
> > > > a/t
The ITSes on the Hip07 (as present in the Huawei D05) are broken when
it comes to addressing the redistributors, and need to be explicitely
told to address the VLPI page instead of the redistributor base address.
So let's add yet another quirk, fixing up the target address
in the command stream.
2017-10-10 21:18 GMT+09:00 Matthew Wilcox :
> On Mon, Oct 09, 2017 at 01:10:01AM +0900, Masahiro Yamada wrote:
>> Reducing the header dependency will help for speeding the kernel
>> build, suppressing unnecessary recompile of objects during
>> git-bisect'ing, etc.
>
> Well, does it? You could prov
On Tue, Oct 10, 2017 at 01:34:48PM +0100, Srinivas Kandagatla wrote:
> Thanks for the review comments.
>
> On 10/10/17 11:05, Charles Keepax wrote:
> > On Fri, Oct 06, 2017 at 05:51:30PM +0200, srinivas.kandaga...@linaro.org
> > wrote:
> > > +Required property for SLIMbus child node if it is pres
Thanks for the review comments,
On 10/10/17 13:19, Charles Keepax wrote:
On Fri, Oct 06, 2017 at 05:51:31PM +0200, srinivas.kandaga...@linaro.org wrote:
From: Sagar Dharia
Slimbus devices use value-element, and information elements to
control device parameters (e.g. value element is used to r
On Tue, 2017-10-10 at 13:58 +0300, Joonas Lahtinen wrote:
> On Tue, 2017-10-10 at 17:50 +0800, Tina Zhang wrote:
> > GEM proxy is a kind of GEM, whose backing physical memory is pinned
> > and produced by guest VM and is used by host as read only. With GEM
> > proxy, host is able to access guest ph
On 10/10/17 12:05, Ulf Hansson wrote:
> On 29 September 2017 at 15:42, Sudeep Holla wrote:
>> This patch hooks up the support for device power domain provided by
>> SCMI using the Linux generic power domain infrastructure.
>>
>> Cc: Kevin Hilman
>> Cc: Ulf Hansson
>> Signed-off-by: Sudeep Holl
On 09/10/2017 21:33, David Kozub wrote:
> On Mon, 9 Oct 2017, Daniel Lezcano wrote:
>
>> On 07/10/2017 23:26, David Kozub wrote:
>>> Hi all,
>>>
>>> booting up kernel 4.14-rc3 with CS5535_CLOCK_EVENT_SRC on an ALIX 2c3
>>> (http://pcengines.ch/alix2c3.htm) dies with:
>>>
>>> [ 2.313086] cs5535-
On Tue, Oct 10, 2017 at 01:33:21PM +0200, Peter Zijlstra wrote:
> But now you've got me looking at 75e8387685f6, which also looks
> completely insane.
The reason I insta stumbled on that patch is that it only addresses the
ftrace situation and doesn't mention the other _5_ places that use this
int
[...]
I have also run some test on my ux500 board and enabling the blkmq
path via the new MMC Kconfig option. My idea was to run some iozone
comparisons between the legacy path and the new blkmq path, but I just
couldn't get to that point because of the following errors.
>
Wei Wang wrote:
> > And even if we could remove balloon_lock, you still cannot use
> > __GFP_DIRECT_RECLAIM at xb_set_page(). I think you will need to use
> > "whether it is safe to wait" flag from
> > "[PATCH] virtio: avoid possible OOM lockup at virtballoon_oom_notify()" .
>
> Without the lock b
To reduce the memory footprints of the driver in kdump kernel,
we have made below driver setting when system boots in to kdump kernel,
1. Used single MSI-x vector.
2. Disable RDPQ mode.
3. Set sg_table_size to 32 by default.
4) Set SCSI IO Queue depth to 200.
Signed-off-by: Sreekanth Reddy
---
Fixed below memory leak in driver,
* While removing Expander devices - we are removing expander
device entry from the list before freeing it's child devices,
so while freeing child device we are finding its parent device
node as NULL and so we are not freeing the child device's
allocated data
Phase15 driver enhancements and fixes.
Sreekanth Reddy (10):
mpt3sas: Processing of Cable Exception events
mpt3sas: Fixed memory leaks in driver
mpt3sas: Reduce memory footprints in kdump kernel
mpt3sas: Fix removal and addition of vSES device during host reset
mpt3sas: Fix IO error occu
Earlier Active Cable Exception event with reason code
"Cable Degraded (0x02))" was added only for Active Cable,
Now this event is extended to Passive cable too.
So re-arranged display message accordingly.
Also added Cable Exception Event even for SAS3008 & SAS3108 HBAs
(i.e. MPI 2.5 spec supportin
Whenever IO for raid volume fails with IOCStatus
"MPI2_IOCSTATUS_SCSI_IOC_TERMINATED"and SCSIStatus equal to
"(MPI2_SCSI_STATE_TERMINATED | MPI2_SCSI_STATE_NO_SCSI_STATUS)"
then return the IO to SML with "DID_RESET"
(i.e. retry the IO infinite times) host bytes.
Earlier driver is returning the
On Tue, 10 Oct 2017 12:58:51 +0530 Christina Jacob
wrote:
> The patch below implements port to port forwarding through route table and arp
> table lookup for ipv4 packets using bpf_redirect helper function and lpm_trie
> map. This has an improved performance over the normal kernel stack ip
>
Enclosure handles are not updated after host reset.
As a result, driver device structure is holding previously
assigned enclosure handle which is different from the
enclosure handle populated in the corresponding device page.
Modified the driver to update devices enclosure handles after
host re
Updated MPI headers to v2.00.48
Signed-off-by: Sreekanth Reddy
---
drivers/scsi/mpt3sas/mpi/mpi2.h | 43 ++-
drivers/scsi/mpt3sas/mpi/mpi2_cnfg.h | 564 +--
drivers/scsi/mpt3sas/mpi/mpi2_init.h | 11 +-
drivers/scsi/mpt3sas/mpi/mpi2_ioc.h | 282 +++
Bump mpt3sas driver version to v16.100.00.00
Signed-off-by: Sreekanth Reddy
---
drivers/scsi/mpt3sas/mpt3sas_base.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/mpt3sas/mpt3sas_base.h
b/drivers/scsi/mpt3sas/mpt3sas_base.h
index 75d90f2..0fe3969 100644
---
On Tue, Oct 10, 2017 at 02:08:11PM +0300, Nikolay Borisov wrote:
>
>
> On 10.10.2017 13:48, Rakesh Pandit wrote:
> > Commit a53f4f8e9c8eb ("btrfs: Don't call btrfs_start_transaction() on
> > frozen fs to avoid deadlock.") started using internal calls and we
> > replace them with more suitable one
Adding PNP ID of Mercator i.e. SAS3616 HBA device.
Its device ID is 0xD1 and vendor ID is 0x1000.
Signed-off-by: Sreekanth Reddy
---
drivers/scsi/mpt3sas/mpt3sas_scsih.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/scsi/mpt3sas/mpt3sas_scsih.c
b/drivers/scsi/mpt3sas/mpt3sas_
Display chassis slot information along with other drive location parameters
such as slot number and connector name in the logs; if chassis slot
validity bit is set in 'SAS Enclosure Page 0' while adding the drive.
Signed-off-by: Sreekanth Reddy
---
drivers/scsi/mpt3sas/mpt3sas_base.h | 4 +
Hi Jacob,
On Thu, Oct 05, 2017 at 04:03:29PM -0700, Jacob Pan wrote:
> +int iommu_unbind_pasid_table(struct iommu_domain *domain, struct device *dev)
> +{
> + if (unlikely(!domain->ops->unbind_pasid_table))
> + return -EINVAL;
> +
> + return domain->ops->unbind_pasid_table(doma
On 10/08/2017 10:58 PM, Zhenzhong Duan wrote:
> As xen_cpuhp_setup is called by PV and PVHVM, the name of "x86/xen/hvm_guest"
> is confusing.
>
> Signed-off-by: Zhenzhong Duan
Reviewed-by: Boris Ostrovsky
Applied to for-linus-4.14c.
-boris
For Dev Handles who value is less than hba's phys count number
driver will return HBA sas address value as a sas address.
So for Virtual SES device also driver was returning HBA sas address instead
of Virtual SES sas address. So now updated the driver to return
Virtual SES's sas address for Virt
2017-10-06 17:51 GMT+02:00 Romain Izard :
>
> Certain cipher modes like CTS expect the IV (req->info) of
> ablkcipher_request (or equivalently req->iv of skcipher_request) to
> contain the last ciphertext block when the {en,de}crypt operation is done.
>
> Fix this issue for the Atmel AES hardware e
On Tue, Oct 10, 2017 at 09:56:22PM +0900, Masahiro Yamada wrote:
> One refactoring alone does not produce much benefits,
> but making continuous efforts will disentangle the knotted threads.
> Of course, this might be a pipe dream...
A lot of people have had that dream, and some of those refactori
On Thu, Oct 05, 2017 at 04:03:30PM -0700, Jacob Pan wrote:
> + pdev = to_pci_dev(dev);
> + if (!pci_find_ext_capability(pdev, PCI_EXT_CAP_ID_PRI))
> + return -EINVAL;
> + sid = PCI_DEVID(bus, devfn);
Okay, you search for the PRI capability ...
> +
> + info = dev->archda
On Tue, Oct 10, 2017 at 01:48:05PM +0300, Rakesh Pandit wrote:
> Commit a53f4f8e9c8eb ("btrfs: Don't call btrfs_start_transaction() on
> frozen fs to avoid deadlock.") started using internal calls and we
> replace them with more suitable ones.
>
> Signed-off-by: Rakesh Pandit
> ---
> fs/btrfs/su
Hi Patrick,
On Tue, 2017-10-10 at 10:24 +, Patrick Brünn wrote:
> Hi Philipp,
>
> since commit 790cb4c7c9545953d22d3d425e49b36a711bae5b my display on CX9020 (a
> i.MX53 based machine) stopped working:
>
> # dmesg | grep -i drm
> [0.141829] [drm] Supports vblank timestamp caching Rev 2
On 10/10/2017 at 13:09:35 +0300, Claudiu Beznea wrote:
> Hi,
>
> This series contains fixes and enhancements for Atmel/Microchip boards,
> mainly for SoM1-EK board, SAMA5D2 Xplained board and SAM9x5 boards.
> Please accept them for 4.15.
>
> Thank you,
> Claudiu Beznea
>
> Changes since v1:
> -
When enable CONFIG_RTC_DRV_DS1374_WDT use as watchdog,
in suspend mode, watchdog is still working but no daemon
patting the watchdog. The system will reboot if timeout.
Add support suspend/resume for watchdog.
suspend: disable the watchdog
resume: disable existing watchdog, reload watchdog timer,
This is a patch to the radio-bcm2048.c file that fixes up
a warning found by the checkpatch.pl tool.
Signed-off-by: Branislav Radocaj
---
[1]: https://marc.info/?l=linux-driver-devel&m=150331308401055&w=2
Changes in v2:
Removed unused 'size' argument from property_read macro.
In property_write
On Thu, Oct 05, 2017 at 04:03:31PM -0700, Jacob Pan wrote:
> +int iommu_invalidate(struct iommu_domain *domain,
> + struct device *dev, struct tlb_invalidate_info *inv_info)
This name is way too generic, it should at least be called
iommu_svm_invalidate() or something like that. With t
Hi!
I've got the following report while fuzzing the kernel with syzkaller.
On commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f (4.14-rc4).
It seems that priv ends up being NULL.
usb 1-1: New USB device found, idVendor=0557, idProduct=2009
usb 1-1: New USB device strings: Mfr=204, Product=1, Seri
301 - 400 of 1503 matches
Mail list logo
