On Sat, Jul 09, 2016 at 10:56:55AM -0700, Joe Perches wrote:
> defconfigs both with and without CONFIG_PRINTK build
> properly with the proposed change to this specific patch.
Did you try latest tip/master?
> Borislav, your delightful personality always impresses.
> Never change.
What goes aroun
Sunrise Point PCH with SPS Firmware doesn't expose working
MEI interface, we need to quirk it out.
Cc: #4.4+
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/pci-me.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/mei/pci-me.c b/drivers/misc/mei/pci-me.c
index
On Sat, Jul 9, 2016 at 10:36 AM, Brooks Moses wrote:
> I've been attempting to qualify the Linux 4.5.2 user-space headers for
> a toolchain release, and ran into what looks like a missing include
> file in include/uapi/linux/errqueue.h. In particular,
> https://github.com/torvalds/linux/commit/f2
On Fri, Jul 08, 2016 at 10:13:08PM -0500, Eric W. Biederman wrote:
> "W. Trevor King" writes:
>
> > On Thu, Jul 07, 2016 at 08:01:52AM -0700, James Bottomley wrote:
> >> In theory, we could get nsfs to show this information as an option
> >> (just add a show_options entry to the superblock ops),
Hi,
[auto build test ERROR on linux-nvdimm/libnvdimm-for-next]
[also build test ERROR on v4.7-rc6 next-20160708]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Dan-Williams/replace-pcommit-with-
On Tue, 5 Jul 2016 14:55:09 -0300
Mauro Carvalho Chehab wrote:
> I hope you don't mind. I'm merging those three patches on my tree
> (for now, they're on an experimental tree that I can easily rebase, if
> needed). If OK for you, my plan is to merge it on a separate branch,
> together with the ot
On 10 July 2016 06:26:39 CEST, "Paul E. McKenney"
wrote:
>Hello!
>
>So I ran a quick benchmark which showed stair-step results. I
>immediately
>thought "Ah, this is due to CPU 0 and 1, 2 and 3, 4 and 5, and 6 and 7
>being threads in a core." Then I thought "Wait, this is an x86!"
>Then I dump
On Sat, Jul 9, 2016 at 9:47 PM, kbuild test robot wrote:
> Hi,
>
> [auto build test ERROR on linux-nvdimm/libnvdimm-for-next]
> [also build test ERROR on next-20160708]
> [cannot apply to v4.7-rc6]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the syst
On 7/8/2016 6:43 PM, Markus Mayer wrote:
This series introduces a family of generic string case conversion
functions. This kind of functionality is needed in several places in
the kernel. Right now, everybody seems to be implementing their own
copy of this functionality.
Based on the discussion
Hi,
[auto build test ERROR on linux-nvdimm/libnvdimm-for-next]
[also build test ERROR on next-20160708]
[cannot apply to v4.7-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Dan-Williams/rep
Hello!
So I ran a quick benchmark which showed stair-step results. I immediately
thought "Ah, this is due to CPU 0 and 1, 2 and 3, 4 and 5, and 6 and 7
being threads in a core." Then I thought "Wait, this is an x86!"
Then I dumped out cpu*/topology/thread_siblings_list, getting the following:
On 9 July 2016 at 20:13, Chris Metcalf wrote:
> On 7/8/2016 6:43 PM, Markus Mayer wrote:
>>
>> This series introduces a family of generic string case conversion
>> functions. This kind of functionality is needed in several places in
>> the kernel. Right now, everybody seems to be implementing thei
On Thu, Jul 07, 2016 at 09:30:19PM +0200, Alexander Gordeev wrote:
> On Mon, Jul 04, 2016 at 05:39:33PM +0900, Christoph Hellwig wrote:
> > @@ -1575,6 +1546,7 @@ static int nvme_dev_add(struct nvme_dev *dev)
> > dev->tagset.cmd_size = nvme_cmd_size(dev);
> > dev->tagset.flag
On Thu, Jul 07, 2016 at 01:05:01PM +0200, Alexander Gordeev wrote:
> irq_create_affinity_mask() bails out with no affinity in case of single
> vector, but alloc_descs() (see below (*)) assigns the whole affinity
> mask. It should be consistent instead.
I don't understand the comment. If we only h
On Wed, Jul 06, 2016 at 10:05:45AM +0200, Alexander Gordeev wrote:
> > + pci_enable_msi, pci_enable_msi_range, pci_enable_msi_exact,
> > pci_disable_msi,
> > + pci_msi_vec_count, pci_enable_msix_range, pci_enable_msix_exact,
> > + pci_disable_msix, pci_msix_vec_count
>
> Description of these func
On Sat, 2016-07-09 at 02:45 +0200, Rafael J. Wysocki wrote:
> On Friday, July 08, 2016 12:39:07 PM Srinivas Pandruvada wrote:
> > On Fri, 2016-07-08 at 20:42 +0200, Jan Kiszka wrote:
> > > If MSR_CONFIG_TDP_CONTROL is locked, we currently try to address
> > > some
> > > MSR 0x8648 or so. Mask o
On Mon, Jul 04, 2016 at 11:35:28AM +0200, Alexander Gordeev wrote:
> > mq_map is initialized to zero already, so we don't really need the
> > assignment for queue 0. The reason why this check exists is because
> > we start with queue = -1 and we never want to assignment -1 to mq_map.
>
> Would th
We were needlessly converting nfit_mem_init() errors to -ENOMEM.
Signed-off-by: Dan Williams
---
drivers/acpi/nfit.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/acpi/nfit.c b/drivers/acpi/nfit.c
index d79837b9d07e..f8c1a850effc 100644
--- a/drivers/acpi/nf
Before enabling use of flush hints for pmem regions, we need to make
sure they are always associated. Move the initialization of nfit_flush
out of the block-window specific init path to the general init path.
Cc: Ross Zwisler
Signed-off-by: Dan Williams
---
drivers/acpi/nfit.c | 17 -
In preparation for generically mapping flush hint addresses for both the
BLK and PMEM use case, provide a generic / reference counted mapping
api. Given the fact that a dimm may belong to multiple regions (PMEM
and BLK), the flush hint addresses need to be held valid as long as any
region associat
Sample nfit data to test the kernel's handling of the multiple
flush-hint case.
Signed-off-by: Dan Williams
---
tools/testing/nvdimm/test/nfit.c | 55 +++---
1 file changed, 33 insertions(+), 22 deletions(-)
diff --git a/tools/testing/nvdimm/test/nfit.c b/tools
Now that all shared mappings are handled by devm_nvdimm_memremap() we no
longer need nfit_spa_map() nor do we need to trigger a callback to the
bus provider at region disable time.
Signed-off-by: Dan Williams
---
drivers/acpi/nfit.c | 146 --
dri
When the NFIT provides multiple flush hint addresses per-dimm it is
expressing that the platform is capable of processing multiple flush
requests in parallel. There is some fixed cost per flush request, let
the cost be shared in parallel on multiple cpus.
Since there may not be enough flush hint
nd_region device driver data will be used in the namespace i/o path.
Re-order nd_region_remove() to ensure this data stays live across
namespace device removal
Signed-off-by: Dan Williams
---
drivers/nvdimm/region.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers
Commit writes to media on system shutdown or pmem driver unload.
Signed-off-by: Dan Williams
---
drivers/nvdimm/bus.c | 16
drivers/nvdimm/pmem.c |8
include/linux/nd.h|1 +
3 files changed, 25 insertions(+)
diff --git a/drivers/nvdimm/bus.c b/drivers/nv
Given that nvdimm_flush() has higher overhead than wmb_pmem() (pointer
chasing through nd_region), and that we otherwise assume a platform has
ADR capability when flush hints are not present, move nvdimm_flush() to
REQ_FLUSH context.
Cc: Ross Zwisler
Signed-off-by: Dan Williams
---
drivers/nvdi
Flushing posted-write queues is now deferred to REQ_FLUSH context, or
otherwise handled by an ADR event at the platform level.
Cc: Ross Zwisler
Signed-off-by: Dan Williams
---
fs/dax.c |7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/fs/dax.c b/fs/dax.c
index 761495b
nvdimm_flush() is a replacement for the x86 'pcommit' instruction. It is
an optional write flushing mechanism that an nvdimm bus can provide for
the pmem driver to consume. In the case of the NFIT nvdimm-bus-provider
nvdimm_flush() is implemented as a series of flush-hint-address [1]
writes to ea
This reverts commit 8b3e34e46aca9b6d349b331cd9cf71ccbdc91b2e.
Given the deprecation of the pcommit instruction, revert its usage as a
vm exit source in kvm.
Cc: Xiao Guangrong
Cc: Paolo Bonzini
Cc: Ross Zwisler
Signed-off-by: Dan Williams
---
arch/x86/include/asm/vmx.h |1 -
arch/x8
nsio_rw_bytes() is used to write info block metadata to the namespace,
so it should trigger a flush after every write. Replace wmb_pmem() with
nvdimm_flush() in this path.
Cc: Ross Zwisler
Signed-off-by: Dan Williams
---
drivers/nvdimm/claim.c |2 +-
1 file changed, 1 insertion(+), 1 delet
The pcommit instruction is being deprecated in favor of either ADR
(asynchronous DRAM refresh: flush-on-power-fail) at the platform level, or
posted-write-queue flush addresses as defined by the ACPI 6.x NFIT (NVDIMM
Firmware Interface Table).
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter An
The __pmem address space was meant to annotate codepaths that touch
persistent memory and need to coordinate a call to wmb_pmem(). Now that
wmb_pmem() is gone, there is little need to keep this annotation.
Cc: Christoph Hellwig
Cc: Ross Zwisler
Signed-off-by: Dan Williams
---
Documentation/fi
All users have been replaced with flushing in the pmem driver.
Cc: Ross Zwisler
Signed-off-by: Dan Williams
---
arch/x86/include/asm/pmem.h | 36 ++---
include/linux/pmem.h| 47 ---
2 files changed, 6 insertions(+),
Changes since v1 [1]:
1/ Move flush address data from nvdimm_drvdata to nd_region_data (Greg,
Toshi)
2/ Add more detail to cover letter and patch descriptions (Linda, Jeff)
3/ Account for s/REQ_FLUSH/REQ_PREFLUSH/ rename pending in -next.
4/ Add a directed flush at pmem ->remove() and ->shut
In preparation for triggering flushes of a DIMM's writes-posted-queue
(WPQ) via the pmem driver move mapping of flush hint addresses to the
region driver. Since this uses devm_nvdimm_memremap() the flush
addresses will remain mapped while any region to which the dimm belongs
is active.
We need to
On Fri, Apr 08, 2016 at 08:35:43PM +0200, Denys Vlasenko wrote:
> This function compiles to 2554 bytes of machine code.
> In C, the function is almost 200 lines long.
>
> It has only one callsite, but forced inlining that much code
> makes gcc generate significantly worse code. Let gcc itself deci
Hi,
On Tue, May 31, 2016 at 07:41:23AM +0200, Julia Lawall wrote:
> On Mon, 30 May 2016, Ezequiel Garcia wrote:
> > On 28 May 2016 at 13:41, Amitoj Kaur Chawla wrote:
> > > Replace if condition and BUG() with a BUG_ON having the conditional
> > > expression of the if statement as argument.
[...]
From: Rafael J. Wysocki
On Intel hardware, native_play_dead() uses mwait_play_dead() by
default and only falls back to the other methods if that fails.
That also happens during resume from hibernation, when the restore
(boot) kernel runs disable_nonboot_cpus() to take all of the CPUs
except for t
On Fri, Jul 08, 2016 at 10:36:39AM -0700, Florian Fainelli wrote:
> Change the BUG_ON() condition in brcmnand_send_cmd() which checks for
> the interrupt status "controller ready" bit to a WARN_ON.
>
> There is no good reason to kill the system when this condition occur
> because we could have sys
On Saturday, July 09, 2016 11:44:47 AM Hanjun Guo wrote:
> On 2016/7/8 21:22, Lorenzo Pieralisi wrote:
> > On Thu, Jul 07, 2016 at 03:58:04PM +0200, Rafael J. Wysocki wrote:
> >
> > [...]
> >
> >>> Anyway let's avoid these petty arguments, I agree there must be some
> >>> sort of ARM64 ACPI maintai
In practice, devices sometimes return frames larger than current buffer
size, leading to failure in solo_send_desc().
It is not clear which minimal increase in buffer size would be enough,
so this patch doubles it, this should be safely assumed as sufficient.
Signed-off-by: Andrey Utkin
---
driv
To detect whether khugepaged swapin worthwhile, this patch checks
the amount of young pages. There should be at least half of
HPAGE_PMD_NR to swapin.
Signed-off-by: Ebru Akagunduz
Suggested-by: Minchan Kim
---
Changes in v2:
- Don't change thp design, only notice amount of young
pages, if kh
After fixing swapin issues, comment lines stayed as in old version.
This patch updates the comments.
Signed-off-by: Ebru Akagunduz
Cc: Hillf Danton
---
Changes in v2:
- Newly created in this version.
Changes in v3:
- Replace Reported-by with Cc (Hillf Danton)
- Remove RFC tag (Hillf Danton)
This patch series fixes comment inconsistency and supplies to decide
to swapin looking the amount of young pages.
Changes in v2:
- Don't change thp design, notice young pages
if needs to swapin
- Add comment line fixing patch
Changes in v3:
- Remove revert patch (allocstall), the patch auto
On Wed, Jul 6, 2016 at 8:07 PM, Tai Nguyen wrote:
> Signed-off-by: Tai Nguyen
> ---
> Documentation/perf/xgene-pmu.txt | 48 ++
> drivers/perf/Kconfig |7 +
> drivers/perf/Makefile|1 +
> drivers/perf/xgene_pmu.c | 1398
> +++
I came across the following issue in kernel 3.16 (Ubuntu 14.04) which
was then reproduced in kernels 4.4 LTS:
After a couple of of memcg oom-kills in a cgroup, a syscall in
*another* process in the same cgroup hangs indefinitely.
Reproducing:
# mkdir -p strace_run
# mkdir /sys/fs/cgroup/memory/1
Am Samstag, 9. Juli 2016, 11:38:00 schrieb William.wu:
> Dear Heiko & Balbi，
>
> On 2016/7/8 21:29, Felipe Balbi wrote:
> > Hi,
> >
> > Heiko Stuebner writes:
> >> Am Donnerstag, 7. Juli 2016, 10:54:24 schrieb William Wu:
> >>> Add a quirk to configure the core to support the
> >>> UTMI+ PHY wit
On Tue, Jul 5, 2016 at 5:04 AM, Joseph Lo wrote:
> The Inter-VM communication (IVC) is a communication protocol, which is
> designed for interprocessor communication (IPC) or the communication
> between the hypervisor and the virtual machine with a guest OS on it. So
> it can be translated as inte
On Thu, Jul 7, 2016 at 6:37 PM, Gregory CLEMENT
wrote:
> This clock is the parent of all the Armada 3700 clocks. It is a fixed
> rate clock which depends on the gpio configuration read when resetting
> the SoC.
>
> Signed-off-by: Gregory CLEMENT
> ---
> drivers/clk/mvebu/Kconfig| 3
On 9 Jul 2016 at 14:27, Andy Lutomirski wrote:
> On Jul 6, 2016 6:25 PM, "Kees Cook" wrote:
> >
> > Hi,
> >
> > This is a start of the mainline port of PAX_USERCOPY[1]. After I started
> > writing tests (now in lkdtm in -next) for Casey's earlier port[2], I
> > kept tweaking things further and fu
[Re: [PATCH 14/14] PCI: xgene: make it explicitly non-modular] On 07/07/2016
(Thu 15:42) Duc Dang wrote:
> On Thu, Jul 7, 2016 at 3:35 PM, Tanmay Inamdar wrote:
> >
> >
> > On Sat, Jul 2, 2016 at 4:13 PM, Paul Gortmaker
> > wrote:
> >>
> >> The Kconfig currently controlling compilation of this
Hi Randy,
Am Samstag, 9. Juli 2016, 23:42:28 schrieb ayaka:
> On 07/08/2016 05:35 AM, Heiko Stuebner wrote:
> > Am Donnerstag, 7. Juli 2016, 02:22:57 schrieb Randy Li:
> >> The rk3288 firefly reload is a Rockchip RK3288 based board be found by
> >> core board and main board. The regulators are co
From: Colin Ian King
At the current point where ret is being checked for non-zero it has
not changed since it was initialized to zero, hence the check and the
label unref are redundant and can be removed.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/vc4/vc4_drv.c | 3 ---
1 file changed,
From: Jon Mason
Date: Thu, 7 Jul 2016 19:08:52 -0400
> David Miller, Please consider including patches 1-5 in net-next
Done.
From: Arvind Yadav
Date: Fri, 8 Jul 2016 00:07:54 +0530
> -Return type of 'qe_muram_alloc' is 'unsigned long', That Was trying to
> assigned in ucc_fast_tx_virtual_fifo_base_offset and
> ucc_fast_rx_virtual_fifo_base_offset. These variable are 'unsigned int'.
> So before assginment need a proper
From: Hayes Wang
Date: Thu, 7 Jul 2016 15:09:17 +0800
> Remove the unnacessary code.
Series applied.
is_prefetch in arch/x86/mm/fault.c can be called on a user address
that's not readable due to PKRU. This could break it. You might need
to add a get_user_exec or similar.
--Andy
On Jul 6, 2016 6:25 PM, "Kees Cook" wrote:
>
> Hi,
>
> This is a start of the mainline port of PAX_USERCOPY[1]. After I started
> writing tests (now in lkdtm in -next) for Casey's earlier port[2], I
> kept tweaking things further and further until I ended up with a whole
> new patch series. To tha
On Fri, Jul 08, 2016 at 06:03:38PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160707:
>
> New trees: netfilter and netfilter-next
>
> The drm-msm tree gained a conflict against the arm tree.
>
> The block tree gained conflicts against Linus' and the btrfs-kdave trees.
>
> The
Fixes: a1db74209483 ("module: replace copy_module_from_fd with kernel version")
Signed-off-by: Mickaël Salaün
Cc: Mimi Zohar
Cc: Kees Cook
Cc: Luis R. Rodriguez
Cc: Rusty Russell
Cc: Linus Torvalds
Cc: Greg Kroah-Hartman
---
include/linux/lsm_hooks.h | 1 -
include/linux/security.h | 1 -
On Fri, Jul 08, 2016 at 03:06:07PM -0700, Dmitry Torokhov wrote:
> > Last year we had the invite-only session on the 3rd day and what I heard
> > from some people that was considered better. People had a chance to
> > already solve several things upfront and the invite-only day had less
> > issues
When a word length of 1 byte is selected and writing data of length
more than QSPI_WLEN_MAX_BYTES, first MAX_BYTES will be transfered
and remaining will be transfered byte by byte. In that case wlen
field should be cleared before setting.
Signed-off-by: Prahlad V
---
drivers/spi/spi-ti-qspi.c |
ebied...@xmission.com (Eric W. Biederman) writes:
> Andrew Vagin writes:
>
>> All these thoughts about security make me thinking that kcmp is what we
>> should use here. It's maybe something like this:
>>
>> kcmp(pid1, pid2, KCMP_NS_USERNS, fd1, fd2)
>>
>> - to check if userns of the fd1 namepsac
Andrew Vagin writes:
> All these thoughts about security make me thinking that kcmp is what we
> should use here. It's maybe something like this:
>
> kcmp(pid1, pid2, KCMP_NS_USERNS, fd1, fd2)
>
> - to check if userns of the fd1 namepsace is equal to the fd2 userns
>
> kcmp(pid1, pid2, KCMP_NS_PA
-to-avoid-IS_ERR_VALUE-abuses/20160709-235356
config: x86_64-randconfig-x007-201628 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
I
On Sat, 2016-07-09 at 09:50 +0200, Borislav Petkov wrote:
> On Fri, Jul 08, 2016 at 07:40:48PM -0700, Joe Perches wrote:
> > This change isn't described in the commit message and there
> > doesn't seem to be a need to change this.
> How do *you* know? Did *you* actually sit down and build a kernel
Commit-ID: 8709ed4d4b0eab04561c1ec9e6ea50fd1e3897ff
Gitweb: http://git.kernel.org/tip/8709ed4d4b0eab04561c1ec9e6ea50fd1e3897ff
Author: Dave Hansen
AuthorDate: Fri, 17 Jun 2016 17:15:03 -0700
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 14:06:06 +0200
x86/cpu: Fix duplicated X86_B
Commit-ID: 62d855d3e725f4e4b0d2786f7cad3f0660a03a59
Gitweb: http://git.kernel.org/tip/62d855d3e725f4e4b0d2786f7cad3f0660a03a59
Author: Andy Shevchenko
AuthorDate: Sat, 18 Jun 2016 18:51:34 +0300
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 14:02:09 +0200
x86/platform/intel-mid: R
Commit-ID: 9acacc2ac525ef1397af63b15cef7bb77a823c06
Gitweb: http://git.kernel.org/tip/9acacc2ac525ef1397af63b15cef7bb77a823c06
Author: Zhao Lei
AuthorDate: Mon, 20 Jun 2016 17:37:18 +0800
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 13:56:15 +0200
sched/cpuacct: Merge cpuacct_usa
Commit-ID: 8e546bfafb3121ed25c73a0c02311ec58459344a
Gitweb: http://git.kernel.org/tip/8e546bfafb3121ed25c73a0c02311ec58459344a
Author: Zhao Lei
AuthorDate: Mon, 20 Jun 2016 17:37:19 +0800
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 13:56:15 +0200
sched/cpuacct: Use loop to conso
Commit-ID: 277a13e4f0d661678a7084bf97ed96a99c7dac21
Gitweb: http://git.kernel.org/tip/277a13e4f0d661678a7084bf97ed96a99c7dac21
Author: Zhao Lei
AuthorDate: Mon, 20 Jun 2016 17:37:20 +0800
Committer: Ingo Molnar
CommitDate: Sat, 9 Jul 2016 13:56:15 +0200
sched/cpuacct: Introduce cpuacct
Hello!
I've been attempting to qualify the Linux 4.5.2 user-space headers for
a toolchain release, and ran into what looks like a missing include
file in include/uapi/linux/errqueue.h. In particular,
https://github.com/torvalds/linux/commit/f24b9be5957b38bb420b838115040dc2031b7d0c
adds the follow
From: Chen Gang
For a pure output parameter:
- When callee fails, the caller should not assume the output parameter
is still valid.
- And callee should not assume the pure output parameter must be
provided by caller -- caller has right to pass NULL when caller does
not care about it.
Hi Eric,
thanks for all the infos and help! Both your patches look good and i
have successfully tested them on top of with my vblank timestamping patch.
So for both:
Reviewed-and-tested-by: Mario Kleiner
Will you squash 2/2 into my patch or should i resend my patch with yours
squashed in?
On Fri, Jul 8, 2016 at 11:17 PM, wrote:
> Yeah, 'ping' dies with a similar traceback going to rawv6_setsockopt(),
> and 'trinity' dies a horrid death during initialization because it creates
> some sctp sockets to fool around with. The problem in all these cases is that
> setsockopt uses copy_fr
applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Arvind-Yadav/ErrHandling-Make-IS_ERR_VALUE_U32-as-generic-API-to-avoid-IS_ERR_VALUE-abuses/20160709-235356
config: x86_64-rhel (attached as .config)
compiler: gcc-4.9
On Sat, Jul 9, 2016 at 1:25 AM, Ard Biesheuvel
wrote:
> On 9 July 2016 at 04:22, Laura Abbott wrote:
>> On 07/06/2016 03:25 PM, Kees Cook wrote:
>>>
>>> Hi,
>>>
>>> This is a start of the mainline port of PAX_USERCOPY[1]. After I started
>>> writing tests (now in lkdtm in -next) for Casey's earli
IS_ERR_VALUE() assumes that its parameter is an unsigned long.
It can not be used to check if an 'unsigned int' reflects an error.
As they pass an 'unsigned int' into a function that takes an
'unsigned long' argument. This happens to work because the type
is sign-extended on 64-bit architectures be
On Fri, Jul 8, 2016 at 7:22 PM, Laura Abbott wrote:
> On 07/06/2016 03:25 PM, Kees Cook wrote:
>>
>> Hi,
>>
>> This is a start of the mainline port of PAX_USERCOPY[1]. After I started
>> writing tests (now in lkdtm in -next) for Casey's earlier port[2], I
>> kept tweaking things further and furthe
On Sat, Jul 9, 2016 at 5:03 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> Before, the stack protector flag was sanity checked before .config had
>> been reprocessed. This meant the build couldn't be aborted early, and
>> only a warning could be emitted followed later by the compiler blowing
-to-avoid-IS_ERR_VALUE-abuses/20160709-235356
config: x86_64-rhel (attached as .config)
compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
In file included from i
On 07/08/16 09:13, Petr Mladek wrote:
> On Thu 2016-07-07 20:27:13, Topi Miettinen wrote:
>> On 07/07/16 09:16, Petr Mladek wrote:
>>> On Sun 2016-07-03 15:08:07, Topi Miettinen wrote:
The attached patch would make any uses of capabilities generate audit
messages. It works for simple test
From: Chen Gang
For pure bool function's return value, bool is a little better more or
less than int.
And return boolean result directly. Since 'if' statement is also for
boolean checking, and return boolean result, too.
Signed-off-by: Chen Gang
---
arch/powerpc/include/asm/mman.h | 8 +++
On Sat, Jul 09, 2016 at 10:28:49AM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2016/6/9 1:24, Jaegeuk Kim wrote:
> > In f2fs, we don't need to keep block plugging for NODE and DATA writes,
> > since
> > we already merged bios as much as possible.
>
> IMO, we can not remove block plug, this is bec
On Fri, Jul 08, 2016 at 11:50:02PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2016/7/8 11:19, Jaegeuk Kim wrote:
> > Hi Chao,
> >
> > Could you take a look at this in xfstests/generic/013?
> >
> > [ 502.480850] ==
> > [ 502.480864] [ INFO: po
From: Chen Gang
For pure bool function's return value, bool is a little better more or
less than int.
And return boolean result directly, since 'if' statement is also for
boolean checking, and return boolean result, too.
Signed-off-by: Chen Gang
---
include/linux/migrate.h | 4 ++--
mm/compac
IS_ERR_VALUE() assumes that its parameter is an unsigned long.
It can not be used to check if an 'unsigned int' reflects an error.
As they pass an 'unsigned int' into a function that takes an
'unsigned long' argument. This happens to work because the type
is sign-extended on 64-bit architectures be
Thank you for you review, HeiKo
On 07/08/2016 05:35 AM, Heiko Stuebner wrote:
Hi Randy,
Am Donnerstag, 7. Juli 2016, 02:22:57 schrieb Randy Li:
The rk3288 firefly reload is a Rockchip RK3288 based board be found by
core board and main board. The regulators are connected in a different
way to
On 9 July 2016 at 05:04, Luis de Bethencourt wrote:
> On 08/07/16 23:43, Markus Mayer wrote:
>> Add a collection of generic functions to convert strings to lowercase
>> or uppercase.
>>
>> Changing the case of a string (with or without copying it first) seems
>> to be a recurring requirement in th
Hello, Ming.
On Fri, Jul 08, 2016 at 06:35:06PM +0800, Ming Lei wrote:
> I am wondering why REQ_THROTTLED is cleared for the original bio
> even it has been charged and will be issued to driver, and is it allowed
> to throttle and charge the same bio for many times?
So, IIUC, the flag is just to
Hi Hans,
Thanks for great help.
I believe the issues highlighted by your are rectified by now.
One chunk of your proposed changes seems to be wrong.
Also I have one non-technical change I want to introduce to this driver, see it
in the bottom of this letter ("Also, I decided to document known vi
Hi dmitry:
> >>input_mt_report_slot_state(ts->input, MT_TOOL_FINGER, state);
> >>
> >> - if (!state)
> >> - continue;
> >> -
> >> - input_report_abs(ts->input, ABS_MT_POSITION_X,
> >> + if (state == 0x01) {
>
> >Why we need this change? How
Hi dmitry:
>> >> modify raydium touch firmware update rule.
>>
>> >Why? You need to explain why you are proposing a change (but as I
>> >mentioned I see no reason for using custom file names for firmware. Have
>> >userspace adjust name as needed by the driver.
>>
>> >Thanks.
>>
>> Just want to
Intel MID platforms are using explicitly defined regulators.
Let regulator core know that we do not have any additional
regulators left. This lets it substitute unprovided regulators with
dummy ones.
Without this change when CONFIG_REGULATOR=y the USB driver fails on getting
"vbus" regulator and
Hi,
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.7-rc6 next-20160708]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Insu-Yun/qxl-correctly-handling-failed-allocation/201
tip-bot for Paolo Bonzini wrote:
>Commit-ID: eec4b1227db153ca16f8f5f285d01fefdce05438
>Gitweb:
>http://git.kernel.org/tip/eec4b1227db153ca16f8f5f285d01fefdce05438
>Author: Paolo Bonzini
>AuthorDate: Mon, 20 Jun 2016 16:58:30 +0200
>Committer: Ingo Molnar
>CommitDate: Sat, 9 Jul 2016 1
On Sat, Jul 9, 2016 at 6:43 AM, Michal Kubecek wrote:
> On Sat, Jul 09, 2016 at 11:48:49AM +0200, Daniel Borkmann wrote:
>> On 07/09/2016 02:20 AM, Alexei Starovoitov wrote:
>> >On Sat, Jul 09, 2016 at 01:31:40AM +0200, Eric Dumazet wrote:
>> >>On Fri, 2016-07-08 at 17:52 +0200, Michal Kubecek wro
Am 2016-07-08 um 23:08 schrieb Dmitry Torokhov:
> On Tue, Jun 28, 2016 at 06:17:13PM +0200, Martin Kepplinger wrote:
>> Am 2016-06-23 um 19:18 schrieb Dmitry Torokhov:
>>> Hi Martin,
>>>
>>> On Tue, Jun 14, 2016 at 01:20:15PM +0200, Martin Kepplinger wrote:
static int pegasus_reset_resume(str
On 08/07/16 23:43, Markus Mayer wrote:
> Add a collection of generic functions to convert strings to lowercase
> or uppercase.
>
> Changing the case of a string (with or without copying it first) seems
> to be a recurring requirement in the kernel that is currently being
> solved by several duplic
Hi Aaron,
On Sat, 2016-07-09 at 07:47 -0400, Aaron Z wrote:
> On Sat, Jul 9, 2016 at 4:37 AM, Alexey Brodkin
> wrote:
> >
> > Hello,
> >
> > I was playing with quite simple bridged setup on different boards with
> > very recent kernels (4.6.3 as of this writing) and found one interesting
> > be
1 - 100 of 145 matches
Mail list logo
