Hi Florian, Dave,
On Wed, Oct 10, 2018 at 10:26:05AM -0700, David Miller wrote:
> From: Florian Fainelli
> Date: Wed, 10 Oct 2018 09:25:01 -0700
> >
> > On October 10, 2018 7:46:31 AM PDT, Antoine Tenart
> > wrote:
> >>
> >>@Dave, Florian: it seems to me no modification was requested after
> >
On Tue, Oct 9, 2018 at 4:52 PM Malathi Gottam wrote:
>
> Add USERPTR to queue access methods by adding this
> support to io_modes on both the planes.
>
> Signed-off-by: Malathi Gottam
Tested-by: Alexandre Courbot
On Wed, Oct 10, 2018 at 10:14 PM Alan Cox wrote:
> On Wed, 10 Oct 2018 13:10:30 -0700
> > +appropriate to the circumstances. The TAB is obligated to maintain
> > +confidentiality with regard to the reporter of an incident.
>
> I would add (except where required by law.)
With the above change:
Ack
Please ignore this patch - I did not notice that a similar one has
been sent before. >_<
On Thu, Oct 11, 2018 at 3:46 PM Alexandre Courbot wrote:
>
> The venus codec can work just fine with USERPTR buffers. Enable this
> possibility.
>
> Signed-off-by: Alexandre Courbot
> ---
> drivers/media/pla
Hi Helge,
On Thu, 11 Oct 2018 at 11:40, Firoz Khan wrote:
>
> Hi Helge,
>
> On Wed, 10 Oct 2018 at 01:48, Helge Deller wrote:
> >
> > * Firoz Khan :
> > > System call table generation script must be run to generate
> > > unistd_32/64.h and syscall_table_32/64/c32.h files. This patch
> > > will h
The venus codec can work just fine with USERPTR buffers. Enable this
possibility.
Signed-off-by: Alexandre Courbot
---
drivers/media/platform/qcom/venus/vdec.c | 4 ++--
drivers/media/platform/qcom/venus/venc.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/medi
Quoting Kuninori Morimoto (2018-10-09 19:16:48)
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> index 292056b..9cfeb0e 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -299,5 +299,6 @@ source "drivers/clk/sunxi-ng/Kconfig"
> source "drivers/clk/tegra/Kconfig"
> sourc
On 10/10/18 23:07, James Bottomley wrote:
> Resend to show accumulated tags and also to add a third patch listing
> the TAB as the reporting point as a few people seem to want. If it
> gets the same level of support, I'll send it in with the other two.
>
> ---
>
> Previous cover letter:
>
>
>
Hi Suzuki,
On Wed, Oct 10, 2018 at 3:22 PM Suzuki K Poulose wrote:
>
> Hi Ganapatrao,
>
> On 21/06/18 07:33, Ganapatrao Kulkarni wrote:
> > This patch adds a perf driver for the PMU UNCORE devices DDR4 Memory
> > Controller(DMC) and Level 3 Cache(L3C).
> >
> > ThunderX2 has 8 independent DMC PMUs
There are two eSDHC controllers in lx2160a. This patch is to
enable eSDHC for RDB and QDS board.
Signed-off-by: Yinbo Zhu
---
Change in v2:
squash all lx2160a esdhc dts patch into the original patch
arch/arm64/boot/dts/freescale/fsl-lx2160a-qds.dts |8 ++
arch/arm64/boot
Michal Hocko wrote:
> Once we are here, make sure that the reason to trigger the OOM is
> printed without ratelimiting because this is really valuable to
> debug what happened.
Here is my version.
>From 0c9ab34fd01837d4c85794042ecb9e922c9eed5a Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Th
On Wed, Oct 10, 2018 at 09:58:25PM -0400, Martin K. Petersen wrote:
> > This is because the IPTT index must be a unique value per HBA. However,
> > if we switched to SCSI MQ, the block layer tag becomes unique per queue,
> > and not per HBA.
>
> That doesn't sound right.
blk-mq tags are always pe
On 07/10/18 11:51, Geert Uytterhoeven wrote:
> Providing an explicit list of discrimination factors may give the false
> impression that discrimination based on other unlisted factors would be
> allowed.
>
> Avoid any ambiguity by removing the list, to ensure "a harassment-free
> experience for ev
On Wed, 10 Oct 2018, Nick Desaulniers wrote:
> On Wed, Oct 10, 2018 at 1:30 PM Michal Wajdeczko
> wrote:
>>
>> On Wed, 10 Oct 2018 14:01:40 +0200, Jani Nikula
>> wrote:
>>
>> > On Tue, 09 Oct 2018, Nick Desaulniers wrote:
>> >> On Tue, Oct 9, 2018 at 10:14 AM Nathan Chancellor
>> >> wrote:
>>
Typo fixed!
On Thu, 11 Oct 2018 at 11:40, Firoz Khan wrote:
>
> Hi Helge,
>
> On Wed, 10 Oct 2018 at 01:48, Helge Deller wrote:
> >
> > * Firoz Khan :
> > > System call table generation script must be run to generate
> > > unistd_32/64.h and syscall_table_32/64/c32.h files. This patch
> > > will
Hi Helge,
On Wed, 10 Oct 2018 at 01:48, Helge Deller wrote:
>
> * Firoz Khan :
> > System call table generation script must be run to generate
> > unistd_32/64.h and syscall_table_32/64/c32.h files. This patch
> > will have changes which will invokes the script.
> >
> > This patch will generate u
On Fri, Oct 05, 2018 at 03:19:34PM -0700, Andrew Morton wrote:
> On Fri, 5 Oct 2018 00:07:04 +0300 Mike Rapoport
> wrote:
>
> > When a memblock allocation APIs are called with align = 0, the alignment is
> > implicitly set to SMP_CACHE_BYTES.
> >
> > Replace all such uses of memblock APIs with
From: Salil Mehta
Date: Wed, 10 Oct 2018 20:05:33 +0100
> This patch-set mainly adds new additions related to RSS for the new
> hardware Revision 0x21. It also adds support to use RSS hash value
> provided by the hardware along with descriptor.
Series applied.
Hello MNC & Co,
On Wed, 2018-10-10 at 11:58 -0500, Mike Christie wrote:
> On 10/09/2018 10:23 PM, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger
> >
> > With the addition of commit 00d909a107 in v4.19-rc, it incorrectly assumes
> > no
> > signals will be pending for task_struct execu
From: Wei Yongjun
Date: Wed, 10 Oct 2018 02:00:24 +
> In case of error, the function syscon_node_to_regmap() returns ERR_PTR()
> and never returns NULL. The NULL test in the return value check should
> be replaced with IS_ERR().
>
> Fixes: 51f6b410fc22 ("phy: add driver for Microsemi Ocelot
The keycode KEY_FAVORITES(0x16c) used in thinkpad_acpi driver is too
big (out of range > 255) for xorg to handle.
xkeyboard-config has already mapped KEY_BOOKMARKS(156) to
XF86Favorites:
keycodes/evdev:
= 164; // #define KEY_BOOKMARKS 156
symbols/inet:
key{ [ XF86Fav
On Thu, Oct 11, 2018 at 08:29:55AM +0800, Baoquan He wrote:
>On 10/10/18 at 03:44pm, Masayoshi Mizuma wrote:
>> On Wed, Oct 10, 2018 at 05:30:57PM +0800, Baoquan He wrote:
>> > On 10/10/18 at 11:19am, Borislav Petkov wrote:
>> > > On Wed, Oct 10, 2018 at 11:14:26AM +0200, Thomas Gleixner wrote:
>>
Hello,
syzbot found the following crash on:
HEAD commit:3d647e62686f Merge tag 's390-4.19-4' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1707d80940
kernel config: https://syzkaller.appspot.com/x/.config?x=88e9a8a39dc0be2d
da
On Wed, 10 Oct 2018, Bartlomiej Zolnierkiewicz wrote:
> 'default n' is the default value for any bool or tristate Kconfig
> setting so there is no need to write it explicitly.
>
> Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_FOO
> is not set' for visible symbols") the Kconfig be
Wed, Oct 10, 2018 at 10:27:46PM CEST, ja...@zx2c4.com wrote:
>Hey Jiri,
>
>Actually, in the end I went with the suggestion from Andrew and Lukas,
>which is to follow Dan's guideline:
>https://lkml.org/lkml/2016/8/22/374 . It looks like this:
>
>https://git.kernel.org/pub/scm/linux/kernel/git/zx2c4/
Hey Peter & Co,
On Wed, 2018-10-10 at 10:43 +0200, Peter Zijlstra wrote:
> On Wed, Oct 10, 2018 at 03:23:10AM +, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger
> >
> > With the addition of commit 00d909a107 in v4.19-rc, it incorrectly assumes
> > no
> > signals will be pending fo
On Thu, Oct 11, 2018 at 10:55:34AM +1100, Dave Chinner wrote:
> Hi Greg,
>
> Can you please pull the XFS update from the tag listed below? This
> contains the fix for the clone_file_range data corruption issue I
> mentioned in my -rc6 pull request (zero post-eof blocks), as well as
> fixes for sev
On 10/10/18 14:03, Frank Rowand wrote:
> On 10/10/18 13:40, Alan Tull wrote:
>> On Wed, Oct 10, 2018 at 1:49 AM Frank Rowand wrote:
>>>
>>> On 10/09/18 23:04, frowand.l...@gmail.com wrote:
From: Frank Rowand
"of: overlay: use prop add changeset entry for property in new nodes"
From: Christoph Hellwig
Date: Tue, 9 Oct 2018 16:57:13 +0200
> The fore200e driver came up during some dma-related audits, so
> here is the fallout. Compile tested (x86 & sparc) only.
Series applied to net-next.
From: Jason Wang
Date: Tue, 9 Oct 2018 10:06:26 +0800
> Implement ethtool .set_coalesce (-C) and .get_coalesce (-c) handlers.
> Interrupt moderation is currently not supported, so these accept and
> display the default settings of 0 usec and 1 frame.
>
> Toggle tx napi through setting tx-frames
(Cc'ing Dave)
On Wed, Oct 10, 2018 at 5:14 AM Meelis Roos wrote:
>
> Thies 4.19-rc7 on a bunch of test machines and got this warning from one.
> It is reproducible and I have not noticed it before.
>
[...]
> [9.914805] WARNING: CPU: 0 PID: 0 at kernel/softirq.c:168
> __local_bh_enable_ip+0x2
From: "Gautham R. Shenoy"
Hi,
This is the tenth iteration of the patchset to add support for
big-core on POWER9. This patch also optimizes the task placement on
such big-core systems.
The previous versions can be found here:
v9: https://lkml.org/lkml/2018/10/1/608
v8: https://lkml.org/lkml/2018
From: "Gautham R. Shenoy"
POWER9 SMT8 cores consist of two groups of threads, where threads in
each group shares L1-cache. The scheduler is not aware of this
distinction as the current sched-domain hierarchy has all the threads
of the core defined at the SMT domain.
SMT [Thread siblings
From: "Gautham R. Shenoy"
Currently on POWER9 SMT8 cores systems, in sysfs, we report the
shared_cache_map for L1 caches (both data and instruction) to be the
cpu-ids of the threads in SMT8 cores. This is incorrect since on
POWER9 SMT8 cores there are two groups of threads, each of which
shares i
From: "Gautham R. Shenoy"
On IBM POWER9, the device tree exposes a property array identifed by
"ibm,thread-groups" which will indicate which groups of threads share
a particular set of resources.
As of today we only have one form of grouping identifying the group of
threads in the core that shar
From: Nathan Chancellor
Date: Mon, 8 Oct 2018 15:59:05 -0700
> Clang warns when multiple sets of parentheses are used for a single
> conditional statement.
>
> drivers/isdn/hisax/amd7930_fn.c:628:32: warning: equality comparison
> with extraneous parentheses [-Wparentheses-equality]
>
From: David Howells
Date: Mon, 08 Oct 2018 23:47:18 +0100
> Here are a set of patches that prepares for and fix problems in rxrpc's
> package reception code. There serious problems are:
...
> The second patch fixes (A) - (C); the third patch renders (B) and (C)
> non-issues by using the recap_r
Hi all,
Changes since 20181010:
The crypto tree gained conflicts against the mac80211-next tree.
Non-merge commits (relative to Linus' tree): 9625
9096 files changed, 465434 insertions(+), 197078 deletions(-)
I
From: Colin King
Date: Mon, 8 Oct 2018 14:35:58 +0100
> From: Colin Ian King
>
> There are several variables being initialized that are being set later
> and hence the initialization is redundant and can be removed. Remove
> then.
>
> Signed-off-by: Colin Ian King
Applied to net-next.
On Wed, Oct 10, 2018 at 05:46:18PM -0700, Joel Fernandes wrote:
> diff --git a/arch/powerpc/include/asm/book3s/64/pgalloc.h
> b/arch/powerpc/include/asm/book3s/64/pgalloc.h
> index 391ed2c3b697..8a33f2044923 100644
> --- a/arch/powerpc/include/asm/book3s/64/pgalloc.h
> +++ b/arch/powerpc/include/a
On 10/10/2018 18:57, Boris Ostrovsky wrote:
> On 10/10/18 11:53 AM, Juergen Gross wrote:
>> On 10/10/2018 17:09, Joao Martins wrote:
>>> On 10/09/2018 05:09 PM, Juergen Gross wrote:
xenbus_va_dev_error() will try to write error messages to Xenstore
under the error//error node (with somet
Hi,
As discussed at [1], the latest updates to memory hotplug documentation are
causing a conflict between docs and mmotm trees.
These patches resolve the conflict.
[1] https://lkml.org/lkml/2018/10/8/227
David Hildenbrand (1):
docs/core-api: memory-hotplug: add some details about locking inte
From: Mike Rapoport
to allow additions of new documentation about memory hotplug under the same
roof.
Signed-off-by: Mike Rapoport
---
Documentation/core-api/index.rst | 2 +-
Documentation/core-api/memory-hotplug-notifier.rst | 84 -
Documentation/core-a
From: David Hildenbrand
Let's document the magic a bit, especially why device_hotplug_lock is
required when adding/removing memory and how it all play together with
requests to online/offline memory from user space.
[ rppt: moved the text to Documentation/core-api/memory-hotplug.rst ]
Link: htt
On 2018年10月07日 23:44, Jonathan Cameron wrote:
On Tue, 2 Oct 2018 22:38:12 +0800
Song Qiang wrote:
PNI RM3100 is a high resolution, large signal immunity magnetometer,
composed of 3 single sensors and a processing chip with a MagI2C
interface.
Following functions are available:
- Single-
On Wed, 2018-10-10 at 22:36 +, justin.l...@dell.com wrote:
> Hi Samuel,
>
> I am still testing your change and have some comments below.
>
> Thanks,
> Justin
>
>
> > This patch extends the ncsi-netlink interface with two new commands and
> > three new attributes to configure multiple packag
Hi Borislav,
On Thu, Oct 11, 2018 at 7:23 AM Borislav Petkov wrote:
>
> From: Borislav Petkov
>
> When building randconfigs, the build fails at kernel compression stage
> due to missing lz4 on the system but CONFIG_KERNEL_LZ4 has been selected
> by randconfig. The result looks somethins like thi
wire up perf_event_open, seccomp, pkey_mprotect, pkey_alloc,
pkey_free, statx, io_pgetevents and rseq system calls
This require an architecture specific implementation as it not
present now.
Signed-off-by: Firoz Khan
---
arch/ia64/kernel/syscalls/syscall.tbl | 16
1 file change
System call table generation script must be run to generate
unistd_64.h and syscall_table.h files. This patch will have
changes which will invokes the script.
This patch will generate unistd_64.h and syscall_table.h
files by the syscall table generation script invoked by
arch/ia64/Makefile and the
In IA64, system call table entries are the part of entry.S file.
We need to keep it in a separate file so that one of the patch in
this patch series contains a system call table generation script
which can separately handle system call table entries.
Replaced the system call table from entry.S to
The system call tables are in different format in all
architecture and it will be difficult to manually add or
modify the system calls in the respective files. To make
it easy by keeping a script and which'll generate the
header file and syscall table file so this change will
unify them across all
NR_syscalls macro holds the number of system call exist in IA64
architecture. This macro is currently the part of asm/unistd.h
file. We have to change the value of NR_syscalls, if we add or
delete a system call.
One of the patch in this patch series has a script which will
generate a uapi header b
sys_getpagesize entry is present in entry.S file to support
for old user interface. So we need to add an uapi entry too.
Add __NR_old_getpagesize in order to not break old user space
as it is reserved for backwards compatibility with old __NR_
getpagesize.
Signed-off-by: Firoz Khan
---
arch/ia6
The system call number in IA64 architecture starts with 1024. But
most of the other architecute starts with 0. In order to come up
with a common implementation to generate uapi header we need to add
an offset - __NR_Linux with a value 1024.
One of the patch in this patch series does have a script
The purpose of this patch series is:
1. We can easily add/modify/delete system call by changing entry
in syscall.tbl file. No need to manually edit many files.
2. It is easy to unify the system call implementation across all
the architectures.
The system call tables are in different format in
This patch adds a new led trigger that LED device can employ
software or hardware pattern engine.
Consumers can write 'pattern' file to enable the software pattern
which alters the brightness for the specified duration with one
software timer.
Moreover consumers can write 'hw_pattern' file to ena
This patch implements the 'pattern_set'and 'pattern_clear'
interfaces to support SC27XX LED breathing mode.
Signed-off-by: Baolin Wang
Acked-by: Pavel Machek
---
Chnages from v14:
- None.
Changes from v13:
- None.
Changes from v12:
- None.
Changes from v11:
- None.
Changes from v10:
- A
NestMMU requires us to mark the pte invalid and flush the tlb when we do a
RW upgrade of pte. We fixed a variant of this in the fault path in commit
Fixes: bd5050e38aec ("powerpc/mm/radix: Change pte relax sequence to handle
nest MMU hang")
Do the same for mprotect and autonuma upgrades.
Hugetlb
Architectures like ppc64 requires to do a conditional tlb flush based on the old
and new value of pte. Enable that by passing old pte value as the arg.
Signed-off-by: Aneesh Kumar K.V
---
arch/s390/include/asm/pgtable.h | 3 ++-
arch/s390/mm/pgtable.c | 2 +-
arch/x86/include/asm/paravi
NestMMU requires us to mark the pte invalid and flush the tlb when we do a
RW upgrade of pte. We fixed a variant of this in the fault path in commit
Fixes: bd5050e38aec ("powerpc/mm/radix: Change pte relax sequence to handle
nest MMU hang")
Signed-off-by: Aneesh Kumar K.V
---
arch/powerpc/inclu
Signed-off-by: Aneesh Kumar K.V
---
include/linux/hugetlb.h | 18 ++
mm/hugetlb.c| 8 +---
2 files changed, 23 insertions(+), 3 deletions(-)
diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h
index 087fd5f48c91..e2a3b0c854eb 100644
--- a/include/linux
We can upgrade pte access (R -> RW transition) via mprotect or autonuma. We need
to make sure we follow the recommended pte update sequence as outlined in
commit: bd5050e38aec ("powerpc/mm/radix: Change pte relax sequence to handle
nest MMU hang")
for such updates. This patch series do that.
Anee
Some architecture may want to call flush_tlb_range from these helpers.
Signed-off-by: Aneesh Kumar K.V
---
arch/s390/include/asm/pgtable.h | 4 ++--
arch/s390/mm/pgtable.c | 6 --
arch/x86/include/asm/paravirt.h | 7 +--
fs/proc/task_mmu.c | 4 ++--
include/asm-gene
Add support to expose the SPI boot flash on AMD Family 16h CPUs as a
standard mtd device to give userspace BIOS updaters greater feature
support. The BIOS and Kernel Developer's Guide refers to this as the
'SPI ROM' controller and so the driver follows that naming convention
for consistency.
Sign
On Wed, 10 Oct 2018, Kees Cook wrote:
> v5:
> - redesigned to use CONFIG_LSM= and lsm= for both ordering and enabling
> - dropped various Reviewed-bys due to rather large refactoring
Patches 1-10 applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
next-general
and
On Wed, Oct 10, 2018 at 08:05:44PM -0700, Jaegeuk Kim wrote:
> On 10/10, Jaegeuk Kim wrote:
> > On 10/11, Sahitya Tummala wrote:
> > > On Wed, Oct 10, 2018 at 02:34:02PM -0700, Jaegeuk Kim wrote:
> > > > On 10/10, Sahitya Tummala wrote:
> > > > > Direct IO can be used in case of hardware encryption
Colin,
> There are extraneous parantheses that are causing clang to produce a
> warning so remove these.
>
> Clean up 3 clang warnings:
> equality comparison with extraneous parentheses [-Wparentheses-equality]
Applied to 4.20/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engine
On Wed, Oct 10, 2018 at 05:03:33PM -0600, Logan Gunthorpe wrote:
>
>
> On 2018-10-10 2:19 p.m., Bjorn Helgaas wrote:
> > I added the reviewed-by tags from Christoph, Jens' ack on the blkdev.h
> > change, and applied these to pci/peer-to-peer with the intent of
> > merging these for v4.20.
> >
>
Hi Linus,
After merging the pinctrl tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/pinctrl/bcm/pinctrl-ns.c: In function 'ns_pinctrl_probe':
drivers/pinctrl/bcm/pinctrl-ns.c:288:29: warning: cast from pointer to integer
of different size [-Wpointer-to-int-cas
On 10/10/2018 03:09 PM, Michal Hocko wrote:
> On Wed 10-10-18 08:39:22, Anshuman Khandual wrote:
> [...]
>> diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h
>> index 9df1d59..4bcbf1e 100644
>> --- a/include/linux/hugetlb.h
>> +++ b/include/linux/hugetlb.h
>> @@ -504,6 +504,16 @@ st
Em Wed, 10 Oct 2018 17:00:01 -0700
James Bottomley escreveu:
> On Wed, 2018-10-10 at 18:23 -0500, Eric W. Biederman wrote:
> > James Bottomley writes:
> >
> > > Resend to show accumulated tags and also to add a third patch
> > > listing the TAB as the reporting point as a few people seem to
>
On Wed, Oct 10, 2018 at 02:13:22PM -0700, Andy Lutomirski wrote:
> On Wed, Oct 10, 2018 at 11:17 AM Josh Poimboeuf wrote:
> >
> > On Wed, Oct 10, 2018 at 01:16:05PM -0500, Josh Poimboeuf wrote:
> > > On Wed, Oct 10, 2018 at 11:03:43AM -0700, Andy Lutomirski wrote:
> > > > > +#define DECLARE_STATIC
Hi Jacek,
On 11 October 2018 at 04:43, Jacek Anaszewski
wrote:
> Hi Baolin,
>
> I've finally managed to test this patch and it turned out
> that this implementation doesn't prevent what I had concerns
> about, i.e. setting intervals less then 50ms.
>
> What user needs to do to achieve that is jus
I think the issue is that using vmx instructions after vmx off. The
scenario is:
1. kernel is rebooting and vmx is turned off by notification handler
kvm_reboot(),
and 'kvm_rebooting' is set.
2. But there is a pending KVM_CREATE_VCPU ioctl which will invoke
vmcs_clear()->
kvm_handle_
Andes FPU hardware does not support denormalized number handling.
>From Andes FPU spec, FPU generates a denorm input to require kernel
to deal with this instrution operation when encountering a denormalized
operand. Hence an emulator for nds32 FPU ISA in kernel is needed to
satisfy the requirement.
This modification is quoted from glibc 'commit <
sysdeps/unix/sysv/linux/sparc/sparc64/dl-procinfo.c: Moved to>
(fe0b1e854ad32a69b260)'
Signed-off-by: Vincent Chen
---
include/math-emu/op-2.h | 97 ++
1 files changed, 46 insertions(+), 51 deletions(-
_FP_ROUND_ZERO is defined as 0 and used as a statemente in macro
_FP_ROUND. This generates "error: statement with no effect
[-Werror=unused-value]" from gcc. Defining _FP_ROUND_ZERO as (void)0 to
fix it.
This modification is quoted from glibc 'commit
(8ed1e7d5894000c155acbd06f)'
Signed-off-by: V
For current nds32 FPU, arithmetic for denormalized number is unsupported.
When nds32 FPU finds the result of floating pointer instruction is a
denormlized number, nds32 FPU thinks an underflow condition is happened
and round the result to an appropriate number. It may cause precision
loss. This com
This patchset contains basic components for nds32 FPU support such as
exception handler and context switch for FPU register. Lazy FPU is
supported in nds32 by default. User can through CONFIG_UNLZAY_FPU to
disable this feature. In addition, a floating point emulator is needed to
deal with all ari
This commit contains basic components for nds32 FPU support such as
FPU exception handler and context switch for FPU register.
Signed-off-by: Vincent Chen
---
arch/nds32/Kconfig |1 +
arch/nds32/Kconfig.cpu | 22 +++
arch/nds32/Makefile
On Wed, Oct 10, 2018 at 11:51 PM Kees Cook wrote:
>
> On Wed, Oct 10, 2018 at 12:03 AM, Miguel Ojeda
> wrote:
> > On Wed, Oct 10, 2018 at 8:12 AM Joel Stanley wrote:
> >>
> >> On Thu, 27 Sep 2018 at 05:07, Kees Cook wrote:
> >> >
> >> > Yeah, that's what I'd linked to in the patchwork URL. Andr
Em Wed, 10 Oct 2018 13:09:40 -0700
James Bottomley escreveu:
> Significant concern has been expressed about the responsibilities outlined in
> the enforcement clause of the new code of conduct. Since there is concern
> that this becomes binding on the release of the 4.19 kernel, strip the
> enfo
Em Wed, 10 Oct 2018 13:08:35 -0700
James Bottomley escreveu:
> The current code of conduct has an ambiguity in the it considers publishing
> private information such as email addresses unacceptable behaviour. Since
> the Linux kernel collects and publishes email addresses as part of the patch
>
Em Wed, 10 Oct 2018 21:13:13 +0100
Alan Cox escreveu:
> On Wed, 10 Oct 2018 13:10:30 -0700
> > +appropriate to the circumstances. The TAB is obligated to maintain
> > +confidentiality with regard to the reporter of an incident.
>
> I would add (except where required by law.)
With the proposed
Tisztelt felhasználó,
Postaládája túllépte a szokásos 100 MB tárolási korlátot, nem lesz képes
fogadni vagy küldeni e-mailt, amíg meg nem növeli a postaláda kvótáját. A levél
kvótájának növeléséhez kattintson az alábbi hivatkozásra, és töltse ki a
szükséges adatokat a postaláda-kvóta növelés
Hi Pavel,
On 11 October 2018 at 00:00, Pavel Machek wrote:
> Hi!
>
> [Oops. I wrote this but forgot to send it? Anyway.. I guess it is
> redundant now.]
>
>> > +++ b/Documentation/ABI/testing/sysfs-class-led-trigger-pattern
>> > @@ -0,0 +1,76 @@
>> > +What: /sys/class/leds//pattern
>
Hi all,
On Wed, 10 Oct 2018 13:22:24 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the kvm-ppc tree got a conflict in:
>
> include/uapi/linux/kvm.h
>
> between commit:
>
> 233a7cb23531 ("kvm: arm64: Allow tuning the physical address size for VM")
>
> from the kvm-arm tree
In preparation for runtime randomization of the zone lists, take all
(well, most of) the list_*() functions in the buddy allocator and put
them in helper functions. Provide a common control point for injecting
additional behavior when freeing pages.
Cc: Michal Hocko
Cc: Dave Hansen
Signed-off-by
On Thu, 4 Oct 2018 16:55:47 +
Song Liu wrote:
> > Works for me,
> >
> > Acked-by: Peter Zijlstra (Intel)
>
> Thanks Peter!
>
> Steven, could you please test/apply this?
Sorry for the late reply. Yeah, I just pulled this into my queue and
I've started running tests on it.
Thanks Song
John,
> However it does block us in future from enabling SCSI MQ in the driver.
We're going to remove the legacy I/O path so I'm not particularly keen
on merging something that's going in the opposite direction.
> This is because the IPTT index must be a unique value per HBA. However,
> if we
Some data exfiltration and return-oriented-programming attacks rely on
the ability to infer the location of sensitive data objects. The kernel
page allocator, especially early in system boot, has predictable
first-in-first out behavior for physical pages. Pages are freed in
physical address order w
When freeing a page with an order >= shuffle_page_order randomly select
the front or back of the list for insertion.
While the mm tries to defragment physical pages into huge pages this can
tend to make the page allocator more predictable over time. Inject the
front-back randomness to preserve the
Changes since v3 [1]:
* Replace runtime 'shuffle_page_order' parameter with a compile-time
CONFIG_SHUFFLE_PAGE_ALLOCATOR on/off switch and a
CONFIG_SHUFFLE_PAGE_ORDER if a distro decides that the default 4MB
shuffling boundary is not sufficient. Administrators will not be
burdened with maki
On 10/11/2018 04:25 AM, Shuah Khan wrote:
On 10/07/2018 08:32 AM, Li Zhijian wrote:
ping
On 09/21/2018 06:00 PM, Li Zhijian wrote:
lizhijian@haswell-OptiPlex-9020:/home/lizj/linux/tools/testing/selftests$ make
[...snip...]
make ARCH=x86 CROSS_COMPILE= -C ../../../gpio
make[2]: Entering dire
On (10/10/18 22:10), Tetsuo Handa wrote:
> >> I've found at least 1 place that uses DEFAULT_RATELIMIT_INTERVAL*10:
> >> https://elixir.bootlin.com/linux/latest/source/fs/btrfs/extent-tree.c#L8365
> >> Probably we need something similar here.
>
> Since printk() is a significantly CPU consuming oper
ebied...@xmission.com (Eric W. Biederman) writes:
> Sean Christopherson writes:
>
>> On Wed, Oct 10, 2018 at 05:06:52PM -0500, Eric W. Biederman wrote:
>>> ebied...@xmission.com (Eric W. Biederman) writes:
>>>
>>> > So I am flummoxed. I am reading through the code and I don't see
>>> > anything
Sean Christopherson writes:
> On Wed, Oct 10, 2018 at 05:06:52PM -0500, Eric W. Biederman wrote:
>> ebied...@xmission.com (Eric W. Biederman) writes:
>>
>> > So I am flummoxed. I am reading through the code and I don't see
>> > anything that could trigger this, and when I ran the supplied repro
On Wed, Oct 10, 2018 at 5:46 PM, Joel Fernandes wrote:
> On Wed, Oct 10, 2018 at 01:00:11PM +0300, Kirill A. Shutemov wrote:
[...]
>>
>> My worry is that some architecture has to allocate page table differently
>> depending on virtual address (due to aliasing or something). Original page
>> table
Hi all,
On Thu, 6 Sep 2018 12:49:39 +0200 Peter Oberparleiter
wrote:
>
> On 28.08.2018 02:43, Masami Hiramatsu wrote:
> > I recently added a gcov profiling for ftrace, following
> > Documentation/dev-tools/gcov.rst.
> > 6b7dca401cb1 ("tracing: Allow gcov profiling on only ftrace subsystem")
> >
Three avenues to rescind GPLv2 property. RAP strategy added.
Here's a case in NY where a Software distributor agreement violated New
York's Rule Against Perpetuities
McAllister Software Systems, Inc. v. Henry Schein, Inc., No. 06-0093,
2008 WL 922328 (E.D. Mo. April 2, 2008)
So we see that a
1 - 100 of 750 matches
Mail list logo
