> "Arnd" == Arnd Bergmann writes:
Arnd> Shifting a dma_addr_t right by 32 bits causes a compile-time
Arnd> warning when that type is only 32 bit wide:
Arnd> drivers/scsi/aacraid/src.c: In function 'aac_src_start_adapter':
Arnd> drivers/scsi/aacraid/src.c:414:29: error: right
In order to manage server systems, there is typically another processor
known as a BMC (Baseboard Management Controller) which is responsible
for powering the server and other various elements, sometimes fans,
often the system flash.
The Aspeed BMC family which is what is used on OpenPOWER
> "Arnd" == Arnd Bergmann writes:
Arnd> Shifting a dma_addr_t right by 32 bits causes a compile-time
Arnd> warning when that type is only 32 bit wide:
Arnd> drivers/scsi/aacraid/src.c: In function 'aac_src_start_adapter':
Arnd> drivers/scsi/aacraid/src.c:414:29: error: right shift count >=
In order to manage server systems, there is typically another processor
known as a BMC (Baseboard Management Controller) which is responsible
for powering the server and other various elements, sometimes fans,
often the system flash.
The Aspeed BMC family which is what is used on OpenPOWER
On Tue, 2017-02-07 at 14:25 -0800, Christoph Hellwig wrote:
> On Tue, Feb 07, 2017 at 11:01:29PM +0200, Amir Goldstein wrote:
> > Project id's are not exactly "subtree" semantic, but inheritance
> > semantics,
> > which is not the same when non empty directories get their project
> > id changed.
>
On Tue, 2017-02-07 at 14:25 -0800, Christoph Hellwig wrote:
> On Tue, Feb 07, 2017 at 11:01:29PM +0200, Amir Goldstein wrote:
> > Project id's are not exactly "subtree" semantic, but inheritance
> > semantics,
> > which is not the same when non empty directories get their project
> > id changed.
>
From: Omar Sandoval
Since KERN_CONT became meaningful again, lockdep stack traces have had
annoying extra newlines, like this:
[5.561122] -> #1 (B){+.+...}:
[5.561528]
[5.561532] [] lock_acquire+0xc3/0x210
[5.562178]
[5.562181] [] mutex_lock_nested+0x74/0x6d0
From: Omar Sandoval
Since KERN_CONT became meaningful again, lockdep stack traces have had
annoying extra newlines, like this:
[5.561122] -> #1 (B){+.+...}:
[5.561528]
[5.561532] [] lock_acquire+0xc3/0x210
[5.562178]
[5.562181] [] mutex_lock_nested+0x74/0x6d0
[5.562861]
Currently CONFIG_TIMER_STATS exposes process information across namespaces:
kernel/time/timer_list.c print_timer():
SEQ_printf(m, ", %s/%d", tmp, timer->start_pid);
/proc/timer_list:
#11: <>, hrtimer_wakeup, S:01, do_nanosleep, cron/2570
Given that the tracer can give
Currently CONFIG_TIMER_STATS exposes process information across namespaces:
kernel/time/timer_list.c print_timer():
SEQ_printf(m, ", %s/%d", tmp, timer->start_pid);
/proc/timer_list:
#11: <>, hrtimer_wakeup, S:01, do_nanosleep, cron/2570
Given that the tracer can give
On Tue 07 Feb 05:10 PST 2017, Stanimir Varbanov wrote:
> * firmware loader
>
I like the way this turns out, just some style comments below.
[..]
> diff --git a/drivers/media/platform/qcom/venus/firmware.c
> b/drivers/media/platform/qcom/venus/firmware.c
> new file mode 100644
> index
On Tue 07 Feb 05:10 PST 2017, Stanimir Varbanov wrote:
> * firmware loader
>
I like the way this turns out, just some style comments below.
[..]
> diff --git a/drivers/media/platform/qcom/venus/firmware.c
> b/drivers/media/platform/qcom/venus/firmware.c
> new file mode 100644
> index
This provides access to the mbox registers on the ast2400 and ast2500
SoCs.
This driver allows arbitrary reads and writes to the 16 data registers as
the other end may have configured the mbox hardware to provide an
interrupt when a specific register gets written to.
Signed-off-by: Cyril Bur
This provides access to the mbox registers on the ast2400 and ast2500
SoCs.
This driver allows arbitrary reads and writes to the 16 data registers as
the other end may have configured the mbox hardware to provide an
interrupt when a specific register gets written to.
Signed-off-by: Cyril Bur
hi. not sure how helpful this really is.
6266.001262] general protection fault: [#1] SMP
6266.001306] Modules linked in: sha1_ssse3 twofish_generic
twofish_x86_64_3way twofish_x86_64 twofish_common serpent_sse2_x86_64
serpent_generic nls_iso8859_1 nls_cp437 pcrypt crypto_user msr drbg
hi. not sure how helpful this really is.
6266.001262] general protection fault: [#1] SMP
6266.001306] Modules linked in: sha1_ssse3 twofish_generic
twofish_x86_64_3way twofish_x86_64 twofish_common serpent_sse2_x86_64
serpent_generic nls_iso8859_1 nls_cp437 pcrypt crypto_user msr drbg
On 02/07/2017 09:55 AM, Ross Lagerwall wrote:
> This fixes a crash when running out of grant refs when creating many
> queues across many netdevs.
>
> * If creating queues fails (i.e. there are no grant refs available),
> call xenbus_dev_fatal() to ensure that the xenbus device is set to the
>
On 02/07/2017 09:55 AM, Ross Lagerwall wrote:
> This fixes a crash when running out of grant refs when creating many
> queues across many netdevs.
>
> * If creating queues fails (i.e. there are no grant refs available),
> call xenbus_dev_fatal() to ensure that the xenbus device is set to the
>
On Tue, Feb 7, 2017 at 3:24 PM, Kees Cook wrote:
> On Tue, Feb 7, 2017 at 2:48 PM, Thomas Gleixner wrote:
>> On Fri, 3 Feb 2017, Kees Cook wrote:
>>
>>> On Fri, Feb 3, 2017 at 2:29 PM, Xing Gao wrote:
>>> > Dear Thomas and Kees,
>>>
On Tue, Feb 7, 2017 at 3:24 PM, Kees Cook wrote:
> On Tue, Feb 7, 2017 at 2:48 PM, Thomas Gleixner wrote:
>> On Fri, 3 Feb 2017, Kees Cook wrote:
>>
>>> On Fri, Feb 3, 2017 at 2:29 PM, Xing Gao wrote:
>>> > Dear Thomas and Kees,
>>> >
>>> > I posted a bug report on bugzilla, and John asked me
On Tue, Feb 7, 2017 at 6:10 PM, Jan Kiszka wrote:
> Use pci_alloc_irq_vectors to enable MSI when available. At least the
> XR17V352 supports this.
>
FWIW:
Reviewed-by: Andy Shevchenko
> Signed-off-by: Jan Kiszka
> ---
On Tue, Feb 7, 2017 at 6:10 PM, Jan Kiszka wrote:
> Use pci_alloc_irq_vectors to enable MSI when available. At least the
> XR17V352 supports this.
>
FWIW:
Reviewed-by: Andy Shevchenko
> Signed-off-by: Jan Kiszka
> ---
> drivers/tty/serial/8250/8250_exar.c | 8 +++-
> 1 file changed, 7
The SECCOMP_RET_KILL filter return code has always killed the current
thread, not the entire process. Changing this as a side-effect of dumping
core isn't a safe thing to do (a few test suites have already flagged this
behavioral change). Instead, restore the RET_KILL semantics, but still
dump
The SECCOMP_RET_KILL filter return code has always killed the current
thread, not the entire process. Changing this as a side-effect of dumping
core isn't a safe thing to do (a few test suites have already flagged this
behavioral change). Instead, restore the RET_KILL semantics, but still
dump
On Tue, Feb 7, 2017 at 2:48 PM, Thomas Gleixner wrote:
> On Fri, 3 Feb 2017, Kees Cook wrote:
>
>> On Fri, Feb 3, 2017 at 2:29 PM, Xing Gao wrote:
>> > Dear Thomas and Kees,
>> >
>> > I posted a bug report on bugzilla, and John asked me to send it the
On Tue, Feb 7, 2017 at 2:48 PM, Thomas Gleixner wrote:
> On Fri, 3 Feb 2017, Kees Cook wrote:
>
>> On Fri, Feb 3, 2017 at 2:29 PM, Xing Gao wrote:
>> > Dear Thomas and Kees,
>> >
>> > I posted a bug report on bugzilla, and John asked me to send it the lkml.
>> >
>> > Here is the link,
On Tue, Feb 7, 2017 at 6:10 PM, Jan Kiszka wrote:
> Those are exar-based, too.
Exar-based
> With the required refactoring of the code to fit into 8250_exar, we
> automatically fix the same issue pci_xr17v35x_setup had before: 8XMODE,
> FCTL, TXTRG and RXTRG were always
On Tue, Feb 7, 2017 at 6:10 PM, Jan Kiszka wrote:
> Those are exar-based, too.
Exar-based
> With the required refactoring of the code to fit into 8250_exar, we
> automatically fix the same issue pci_xr17v35x_setup had before: 8XMODE,
> FCTL, TXTRG and RXTRG were always only set for port 0. Now
Hi Andrew,
On Tue, 7 Feb 2017 15:15:08 -0800 Andrew Morton
wrote:
>
> That patch has a string of fixes and I think we have that fixed up.
> I'll be doing another mmotm in a few minutes...
Excellent, thanks.
--
Cheers,
Stephen Rothwell
Hi Andrew,
On Tue, 7 Feb 2017 15:15:08 -0800 Andrew Morton
wrote:
>
> That patch has a string of fixes and I think we have that fixed up.
> I'll be doing another mmotm in a few minutes...
Excellent, thanks.
--
Cheers,
Stephen Rothwell
Hmm.
Looks ok, except I think we migth want to go even further:
On Tue, Feb 7, 2017 at 2:44 PM, Omar Sandoval wrote:
>
> Since KERN_CONT became meaningful again, lockdep stack traces have
> looked like this:
[ removed really ugly trace ]
> This is what it should look
Hmm.
Looks ok, except I think we migth want to go even further:
On Tue, Feb 7, 2017 at 2:44 PM, Omar Sandoval wrote:
>
> Since KERN_CONT became meaningful again, lockdep stack traces have
> looked like this:
[ removed really ugly trace ]
> This is what it should look like:
>
> [6.650322]
The mm-of-the-moment snapshot 2017-02-07-15-20 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
The mm-of-the-moment snapshot 2017-02-07-15-20 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
From: "Edward A. James"
Add functions to send SCOM operations over I2C bus. The BMC can
communicate with the Power8 host processor over I2C, but needs to use SCOM
operations in order to access the OCC register space.
Signed-off-by: Edward A. James
From: "Edward A. James"
Add functions to send SCOM operations over I2C bus. The BMC can
communicate with the Power8 host processor over I2C, but needs to use SCOM
operations in order to access the OCC register space.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
On Wed, 8 Feb 2017 10:08:03 +1100 Stephen Rothwell
wrote:
> Hi Andrew,
>
> After merging the akpm-current tree, today's linux-next build (arm
> allnoconfig, bfin (most, if not all, configs) and many others) failed
> like this:
>
> mm/nommu.c:1201:15: error: conflicting
On Wed, 8 Feb 2017 10:08:03 +1100 Stephen Rothwell
wrote:
> Hi Andrew,
>
> After merging the akpm-current tree, today's linux-next build (arm
> allnoconfig, bfin (most, if not all, configs) and many others) failed
> like this:
>
> mm/nommu.c:1201:15: error: conflicting types for 'do_mmap'
>
From: "Edward A. James"
Add core support for polling the OCC for it's sensor data and parsing that
data into sensor-specific information.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hwmon/occ| 40
From: "Edward A. James"
Add core support for polling the OCC for it's sensor data and parsing that
data into sensor-specific information.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hwmon/occ| 40
MAINTAINERS| 7 +
From: "Edward A. James"
Add a generic mechanism to expose the sensors provided by the OCC in
sysfs.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hwmon/occ | 62 +++
From: "Edward A. James"
Add a generic mechanism to expose the sensors provided by the OCC in
sysfs.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hwmon/occ | 62 +++
drivers/hwmon/occ/Makefile| 2 +-
drivers/hwmon/occ/occ_sysfs.c | 251
From: "Edward A. James"
This patchset adds a hwmon driver to support the OCC (On-Chip Controller)
on the IBM POWER8 and POWER9 processors, from a BMC (Baseboard Management
Controller). The OCC is an embedded processor that provides real time
power and thermal monitoring.
The
From: "Edward A. James"
This patchset adds a hwmon driver to support the OCC (On-Chip Controller)
on the IBM POWER8 and POWER9 processors, from a BMC (Baseboard Management
Controller). The OCC is an embedded processor that provides real time
power and thermal monitoring.
The driver provides an
Simple cleanup to use the new APIs.
Signed-off-by: Christoph Hellwig
---
drivers/block/cciss.c | 54 ++-
drivers/block/cciss.h | 6 ++
2 files changed, 17 insertions(+), 43 deletions(-)
diff --git a/drivers/block/cciss.c
Simple cleanup to use the new APIs.
Signed-off-by: Christoph Hellwig
---
drivers/block/cciss.c | 54 ++-
drivers/block/cciss.h | 6 ++
2 files changed, 17 insertions(+), 43 deletions(-)
diff --git a/drivers/block/cciss.c
From: "Edward A. James"
Add functions to parse the data structures that are specific to the OCC on
the POWER8 processor. These are the sensor data structures, including
temperature, frequency, power, and "caps."
Signed-off-by: Edward A. James
From: "Edward A. James"
Add functions to parse the data structures that are specific to the OCC on
the POWER8 processor. These are the sensor data structures, including
temperature, frequency, power, and "caps."
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
And the real patch after compile fixing it is here of course:
diff --git a/drivers/target/target_core_internal.h
b/drivers/target/target_core_internal.h
index 9ab7090f7c83..96c38f30069d 100644
--- a/drivers/target/target_core_internal.h
+++ b/drivers/target/target_core_internal.h
@@ -152,6
And the real patch after compile fixing it is here of course:
diff --git a/drivers/target/target_core_internal.h
b/drivers/target/target_core_internal.h
index 9ab7090f7c83..96c38f30069d 100644
--- a/drivers/target/target_core_internal.h
+++ b/drivers/target/target_core_internal.h
@@ -152,6
From: "Edward A. James"
Add code to tie the hwmon sysfs code and the POWER8 OCC code together, as
well as probe the entire driver from the I2C bus. I2C is the communication
method between the BMC and the P8 OCC.
Signed-off-by: Edward A. James
From: "Edward A. James"
Add code to tie the hwmon sysfs code and the POWER8 OCC code together, as
well as probe the entire driver from the I2C bus. I2C is the communication
method between the BMC and the P8 OCC.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
Acked-by: Rob
Hi Benoit,
On Tuesday 07 Feb 2017 07:36:48 Benoit Parrot wrote:
> Laurent Pinchart wrote on Tue [2017-Feb-07 12:26:32 +0200]:
> > On Monday 06 Feb 2017 15:10:46 Steve Longerbeam wrote:
> >> On 02/06/2017 02:33 PM, Laurent Pinchart wrote:
> >>> On Monday 06 Feb 2017 10:50:22 Hans Verkuil wrote:
>
Hi Benoit,
On Tuesday 07 Feb 2017 07:36:48 Benoit Parrot wrote:
> Laurent Pinchart wrote on Tue [2017-Feb-07 12:26:32 +0200]:
> > On Monday 06 Feb 2017 15:10:46 Steve Longerbeam wrote:
> >> On 02/06/2017 02:33 PM, Laurent Pinchart wrote:
> >>> On Monday 06 Feb 2017 10:50:22 Hans Verkuil wrote:
>
The kernel emits a lot of warnings about unexpected IRQs when
an appropriate driver is not presented. It happens because all
interrupts in the core controller are enabled by default after
reset. It would be wise to keep all interrupts masked by default.
Thus disable all local and common
From: "Edward A. James"
Add functions to parse the data structures that are specific to the OCC on
the POWER9 processor. These are the sensor data structures, including
temperature, frequency, power, and "caps."
Signed-off-by: Edward A. James
The kernel emits a lot of warnings about unexpected IRQs when
an appropriate driver is not presented. It happens because all
interrupts in the core controller are enabled by default after
reset. It would be wise to keep all interrupts masked by default.
Thus disable all local and common
From: "Edward A. James"
Add functions to parse the data structures that are specific to the OCC on
the POWER9 processor. These are the sensor data structures, including
temperature, frequency, power, and "caps."
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
On 02/07/2017 01:55 PM, AbdAllah-MEZITI wrote:
> In C a static pointer will be initialized to NULL.
> The §6.7.8 of the ISO/IEC 9899:1999 (E) document says that:
> If an object that has static storage duration is not initialized
> explicitly, then:
> __ if it has pointer type, it is initialized
On 02/07/2017 01:55 PM, AbdAllah-MEZITI wrote:
> In C a static pointer will be initialized to NULL.
> The §6.7.8 of the ISO/IEC 9899:1999 (E) document says that:
> If an object that has static storage duration is not initialized
> explicitly, then:
> __ if it has pointer type, it is initialized
tree, please drop us a note
to help improve the system]
url:
https://github.com/0day-ci/linux/commits/eajames-linux-vnet-ibm-com/drivers-hwmon-Add-On-Chip-Controller-driver/20170207-043353
base:
https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-next
config: openrisc
tree, please drop us a note
to help improve the system]
url:
https://github.com/0day-ci/linux/commits/eajames-linux-vnet-ibm-com/drivers-hwmon-Add-On-Chip-Controller-driver/20170207-043353
base:
https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-next
config: openrisc
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
allnoconfig, bfin (most, if not all, configs) and many others) failed
like this:
mm/nommu.c:1201:15: error: conflicting types for 'do_mmap'
mm/nommu.c:1580:5: error: conflicting types for 'do_munmap'
mm/nommu.c:1638:1:
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
allnoconfig, bfin (most, if not all, configs) and many others) failed
like this:
mm/nommu.c:1201:15: error: conflicting types for 'do_mmap'
mm/nommu.c:1580:5: error: conflicting types for 'do_munmap'
mm/nommu.c:1638:1:
On Tue, Feb 07, 2017 at 01:17:49PM +, Nicholas A. Bellinger wrote:
> - list_del(>acl_list);
> + list_del_init(>acl_list);
All these list_del_init changes don't make sense to me - the whole target
code never does a list_empty check on ->acl_list.
Looking further I think all nacls
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/mellanox/mlxsw/switchx2.c |
On Tue, Feb 07, 2017 at 01:17:49PM +, Nicholas A. Bellinger wrote:
> - list_del(>acl_list);
> + list_del_init(>acl_list);
All these list_del_init changes don't make sense to me - the whole target
code never does a list_empty check on ->acl_list.
Looking further I think all nacls
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/mellanox/mlxsw/switchx2.c | 47
The DYNAMIC_FTRACE_WITH_REGS configuration makes it possible for a ftrace
operation to specify if registers need to saved/restored by the ftrace handler.
This is needed by kgraft and possibly other ftrace-based tools, and the ARM
architecture is currently lacking this feature. It would also be the
The DYNAMIC_FTRACE_WITH_REGS configuration makes it possible for a ftrace
operation to specify if registers need to saved/restored by the ftrace handler.
This is needed by kgraft and possibly other ftrace-based tools, and the ARM
architecture is currently lacking this feature. It would also be the
Dear Concern,
I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a
Film Corporation Located in the United State, is Soliciting for the
Right to use Your Photo/Face and Personality as One of the Semi -Major
Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story
of
Dear Concern,
I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a
Film Corporation Located in the United State, is Soliciting for the
Right to use Your Photo/Face and Personality as One of the Semi -Major
Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story
of
So I used to use this "feature" as a hack to see if something was
running in a k8s cluster or not because fluentd gives a lot of things
away. Runc basically decided to mask this file so it stopped happening
though. But I think namespace aware is the right decision.
On Tue, Feb 7, 2017 at 2:48 PM
So I used to use this "feature" as a hack to see if something was
running in a k8s cluster or not because fluentd gives a lot of things
away. Runc basically decided to mask this file so it stopped happening
though. But I think namespace aware is the right decision.
On Tue, Feb 7, 2017 at 2:48 PM
On Tue, 2017-02-07 at 20:56 +0100, SF Markus Elfring wrote:
> diff --git a/drivers/hid/hid-debug.c b/drivers/hid/hid-debug.c
[]
> @@ -614,19 +614,18 @@ void hid_dump_field(struct hid_field *field, int n,
> struct seq_file *f) {
> tab(n, f); seq_printf(f, "Report Size(%u)\n",
On Tue, 2017-02-07 at 20:56 +0100, SF Markus Elfring wrote:
> diff --git a/drivers/hid/hid-debug.c b/drivers/hid/hid-debug.c
[]
> @@ -614,19 +614,18 @@ void hid_dump_field(struct hid_field *field, int n,
> struct seq_file *f) {
> tab(n, f); seq_printf(f, "Report Size(%u)\n",
Looks fine,
Reviewed-by: Christoph Hellwig
Looks fine,
Reviewed-by: Christoph Hellwig
Dear Concern,
I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a
Film Corporation Located in the United State, is Soliciting for the
Right to use Your Photo/Face and Personality as One of the Semi -Major
Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story
of
Dear Concern,
I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a
Film Corporation Located in the United State, is Soliciting for the
Right to use Your Photo/Face and Personality as One of the Semi -Major
Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story
of
On Tue, Feb 7, 2017 at 6:09 PM, Jan Kiszka wrote:
> So far, pci_xr17v35x_setup always initialized 8XMODE, FCTR & Co. for
> port 0 because it used the address of that port instead of moving the
> pointer according to the port number. Fix this and remove the unneeded
>
On Tue, Feb 7, 2017 at 6:09 PM, Jan Kiszka wrote:
> So far, pci_xr17v35x_setup always initialized 8XMODE, FCTR & Co. for
> port 0 because it used the address of that port instead of moving the
> pointer according to the port number. Fix this and remove the unneeded
> temporary ioremap by moving
On Fri, 3 Feb 2017, Kees Cook wrote:
> On Fri, Feb 3, 2017 at 2:29 PM, Xing Gao wrote:
> > Dear Thomas and Kees,
> >
> > I posted a bug report on bugzilla, and John asked me to send it the lkml.
> >
> > Here is the link, https://bugzilla.kernel.org/show_bug.cgi?id=193921
> >
On Fri, 3 Feb 2017, Kees Cook wrote:
> On Fri, Feb 3, 2017 at 2:29 PM, Xing Gao wrote:
> > Dear Thomas and Kees,
> >
> > I posted a bug report on bugzilla, and John asked me to send it the lkml.
> >
> > Here is the link, https://bugzilla.kernel.org/show_bug.cgi?id=193921
> >
> > Please cc to me
From: Omar Sandoval
Since KERN_CONT became meaningful again, lockdep stack traces have
looked like this:
[5.561122] -> #1 (B){+.+...}:
[5.561528]
[5.561532] [] lock_acquire+0xc3/0x210
[5.562178]
[5.562181] [] mutex_lock_nested+0x74/0x6d0
[5.562861]
[
From: Omar Sandoval
Since KERN_CONT became meaningful again, lockdep stack traces have
looked like this:
[5.561122] -> #1 (B){+.+...}:
[5.561528]
[5.561532] [] lock_acquire+0xc3/0x210
[5.562178]
[5.562181] [] mutex_lock_nested+0x74/0x6d0
[5.562861]
[5.562880] []
On Tue, Feb 7, 2017 at 6:10 PM, Jan Kiszka wrote:
> According to the XR17V352 manual, bit 4 is IrDA control and bit 5 for
> 485. Fortunately, no driver used them so far.
RS-485
>
FWIW:
Reviewed-by: Andy Shevchenko
> Signed-off-by: Jan Kiszka
On Tue, Feb 7, 2017 at 6:10 PM, Jan Kiszka wrote:
> According to the XR17V352 manual, bit 4 is IrDA control and bit 5 for
> 485. Fortunately, no driver used them so far.
RS-485
>
FWIW:
Reviewed-by: Andy Shevchenko
> Signed-off-by: Jan Kiszka
> ---
> include/uapi/linux/serial_reg.h | 4 ++--
On Tue, Feb 07, 2017 at 11:01:29PM +0200, Amir Goldstein wrote:
> Project id's are not exactly "subtree" semantic, but inheritance semantics,
> which is not the same when non empty directories get their project id changed.
> Here is a recap:
> https://lwn.net/Articles/623835/
Yes - but if we
On Tue, Feb 07, 2017 at 01:17:48PM +, Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger
>
> This patch fixes a bug where incoming task management requests
> can be explicitly aborted during an active LUN_RESET, but who's
> struct work_struct are canceled in-flight
On Tue, Feb 07, 2017 at 11:01:29PM +0200, Amir Goldstein wrote:
> Project id's are not exactly "subtree" semantic, but inheritance semantics,
> which is not the same when non empty directories get their project id changed.
> Here is a recap:
> https://lwn.net/Articles/623835/
Yes - but if we
On Tue, Feb 07, 2017 at 01:17:48PM +, Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger
>
> This patch fixes a bug where incoming task management requests
> can be explicitly aborted during an active LUN_RESET, but who's
> struct work_struct are canceled in-flight before execution.
>
On Tue, Feb 07, 2017 at 01:17:46PM +, Nicholas A. Bellinger wrote:
> + if (orig->se_lun_acl != NULL) {
> + pr_warn_ratelimited("Detected existing explicit"
> + " se_lun_acl->se_lun_group reference for %s"
> +
On Tue, Feb 07, 2017 at 01:17:46PM +, Nicholas A. Bellinger wrote:
> + if (orig->se_lun_acl != NULL) {
> + pr_warn_ratelimited("Detected existing explicit"
> + " se_lun_acl->se_lun_group reference for %s"
> +
From: Alexander Usyskin
Parallel reads from multiple threads on a file descriptor
are not well defined and racy. It is safer to return to original
behavior and simply fail the additional read.
The solution is to remove request for next read credit.
Cc:
From: Alexander Usyskin
Parallel reads from multiple threads on a file descriptor
are not well defined and racy. It is safer to return to original
behavior and simply fail the additional read.
The solution is to remove request for next read credit.
Cc: #4.9
Fixes: ff1586a7ea57 ("mei: enqueue
On Tue, Feb 7, 2017 at 6:09 PM, Jan Kiszka wrote:
> pcim_iomap_table only returns the table of mapping, it does not perform
> them. For that, we need to call pcim_iomap, but only if that mapping was
> not done before.
Basically by this change you answered to one of my
On Tue, Feb 7, 2017 at 6:09 PM, Jan Kiszka wrote:
> pcim_iomap_table only returns the table of mapping, it does not perform
> them. For that, we need to call pcim_iomap, but only if that mapping was
> not done before.
Basically by this change you answered to one of my question during review.
On 02/07/2017 12:51 PM, Boris Ostrovsky wrote:
> On 01/24/2017 11:23 AM, Juergen Gross wrote:
>> On 24/01/17 14:47, Boris Ostrovsky wrote:
>>> On 01/23/2017 01:59 PM, Boris Ostrovsky wrote:
On 01/23/2017 05:09 AM, Juergen Gross wrote:
> Handling of multiple concurrent Xenstore accesses
On 02/07/2017 12:51 PM, Boris Ostrovsky wrote:
> On 01/24/2017 11:23 AM, Juergen Gross wrote:
>> On 24/01/17 14:47, Boris Ostrovsky wrote:
>>> On 01/23/2017 01:59 PM, Boris Ostrovsky wrote:
On 01/23/2017 05:09 AM, Juergen Gross wrote:
> Handling of multiple concurrent Xenstore accesses
301 - 400 of 1886 matches
Mail list logo