On Wed, Oct 11, 2017 at 07:07:23PM +0200, David Sterba wrote:
> The comment is useful, but the condition will be always true, so I don't
> see the point.
>
> /*
>* The btree_inode will be always in the root cgroup. The cgroup
>* writeback can be enabled on regular inodes sele
On 12.10.2017 16:45, Jon Hunter wrote:
>
> On 12/10/17 14:25, Thierry Reding wrote:
>> * PGP Signed by an unknown key
>>
>> On Thu, Oct 12, 2017 at 03:06:17PM +0300, Dmitry Osipenko wrote:
>>> Hello Vladimir,
>>>
>>> On 12.10.2017 10:43, Vladimir Zapolskiy wrote:
Hello Dmitry,
On 10
On Thursday, October 12, 2017 10:14:00 AM EDT Richard Guy Briggs wrote:
> Containers are a userspace concept. The kernel knows nothing of them.
>
> The Linux audit system needs a way to be able to track the container
> provenance of events and actions. Audit needs the kernel's help to do
> this.
From: Colin Ian King
Currently variable num_segments is being assigned but never actually
used. Fix this actually using it in the for-loop. Also clean up the
code a little by assigning num_segments at declaration time.
Cleans up clang warning: Value stored to 'num_segments' is never read
Signe
On Thu, Oct 12, 2017 at 09:37:11AM -0600, Jens Axboe wrote:
> On 10/12/2017 09:33 AM, Bart Van Assche wrote:
> > On Thu, 2017-10-12 at 18:01 +0800, Ming Lei wrote:
> >> Even EWMA approach isn't good on SCSI-MQ too, because
> >> some SCSI's .cmd_per_lun is very small, such as 3 on
> >> lpfc and qla2
We are sharing the prototype version of 'fake DAX' flushing
interface for the initial feedback. This is still work in progress
and not yet ready for merging.
Prototype right now just implements basic functionality without advanced
features with two major parts:
- Qemu virtio-pmem device
It expo
This patch moves common code to base header files
so that it can be used for both ACPI pmem and VIRTIO pmem
drivers. More common code needs to be moved out in future
based on functionality required for virtio_pmem driver and
coupling of code with existing ACPI pmem driver.
Signed-off-by: Pan
This patch adds virtio-pmem driver for KVM guest.
Guest reads the persistent memory range information
over virtio bus from Qemu and reserves the range
as persistent memory. Guest also allocates a block
device corresponding to the pmem range which later
can be accessed with DAX compatibl
This patch adds virtio-pmem Qemu device.
This device configures memory address range information with file
backend type. It acts like persistent memory device for KVM guest.
It presents the memory address range to virtio-pmem driver over
virtio channel and does the block flush whenever there
On Thu, 2017-10-12 at 08:23 +0900, Namhyung Kim wrote:
> Hi Tom,
>
> On Wed, Oct 11, 2017 at 08:33:17AM -0500, Tom Zanussi wrote:
> > On Mon, 2017-10-09 at 12:27 +0900, Namhyung Kim wrote:
> > > On Fri, Sep 22, 2017 at 02:59:52PM -0500, Tom Zanussi wrote:
> > > > Variables set as above can be used
On Mon, Sep 11, 2017 at 11:05:22PM -0600, Ross Zwisler wrote:
> If an inode has inline data it is currently prevented from using DAX by a
> check in ext4_set_inode_flags(). When the inode grows inline data via
> ext4_create_inline_data() or removes its inline data via
> ext4_destroy_inline_data_no
On Mon, Sep 11, 2017 at 11:05:23PM -0600, Ross Zwisler wrote:
> The current code has the potential for data corruption when changing an
> inode's journaling mode, as that can result in a subsequent unsafe change
> in S_DAX.
>
> I've captured an instance of this data corruption in the following fst
> Right, but its not going to even get to copcsr until this patch, so the
> SIGFPE handling is I think fixed by this patch, i.e. it isn't just about
> the stats.
On more detailed code inspection, you are right.
> This patch fixes something, I think it should
> a) be clear in the commit message wh
We do not want the common dma_configure() pathway to apply
indiscriminately to all devices, since there are plenty of buses which
do not have DMA capability, and if their child devices were used for
DMA API calls it would only be indicative of a driver bug. However,
there are a number of buses for
On Thu, Oct 12, 2017 at 02:22:04PM +1100, NeilBrown wrote:
>
> If faddr2line is given a function name which is the
> last one listed by "nm -n", it will fail because it
> never finds the next symbol.
>
> So teach the awk script to catch that possibility,
> and use 'size' to provide the end point
On Thu, Oct 12, 2017 at 08:38:17AM -0700, Tejun Heo wrote:
>
> As long as we have the same level of protection, simpler code is of
> course preferable. That said, I haven't followed the discussion
> closely and don't want to apply it without Peter's ack. Peter?
I'm really tied up atm; and feel
On Thu, Oct 12, 2017 at 11:31:51PM +0800, Wangnan (F) wrote:
SNIP
> > > > Ok. If it works it's fine for me.
> > well it works, but it means that bpf file cannot contains any directory
> > part.. which im not sure is ok with bpf folks ;-) anyone?
>
> Sorry I didn't see this thread these days.
>
On Tue, Sep 12, 2017 at 08:46:12AM +0200, Jan Kara wrote:
> On Mon 11-09-17 23:05:25, Ross Zwisler wrote:
> > This helper, in the spirit of ext4_should_dioread_nolock() et al., replaces
> > the complex conditional in ext4_set_inode_flags().
> >
> > Signed-off-by: Ross Zwisler
>
> Yeah, makes sen
On Wed, Oct 11, 2017 at 06:24:03PM -0700, Ricardo Neri wrote:
> On the other hand, in long mode, hardware ignore all segment registers except
> FS
> and GS.
Yap.
> Hence, I guess I can remove the check in question.
Thx.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jan
[ added dri-devel & sparclinux MLs to cc: ]
On Thursday, September 14, 2017 06:02:14 PM Bhumika Goyal wrote:
> Make these structures static as they are not referenced in any other
> file. Make them const as they are used only during a copy operation.
> Replace __initdata with __initconst in file
On Thu, Oct 12, 2017 at 02:32:14PM +0530, Kamalesh Babulal wrote:
> free the allocated insn before returning, when an error occurs
> before adding insn to file->insn_list.
>
> Signed-off-by: Kamalesh Babulal
Any chance you're working on porting objtool to ppc64le? :-)
Acked-by: Josh Poimboeuf
On 2017/10/12 23:59, Jiri Olsa wrote:
On Thu, Oct 12, 2017 at 11:31:51PM +0800, Wangnan (F) wrote:
SNIP
Ok. If it works it's fine for me.
well it works, but it means that bpf file cannot contains any directory
part.. which im not sure is ok with bpf folks ;-) anyone?
Sorry I didn't see thi
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1364489
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/ks7010/ks_wlan_net.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/staging/
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/lustre/lnet/klnds/socklnd/socklnd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lnet/
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/rtl8192e/rtllib_wx.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8192e/rtllib_wx.c
b/d
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1077613
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/rtl8188eu/os_dep/usb_ops_linux.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/
While doing my presentation for ELC and OSS in Prague in a couple of
weeks, I notice an issue with the printk_safe logic. Then I wrote code
to see if my fears were justified.
I noticed that the NMI printks now depend on an irq_work to trigger to
flush the data out that was written by printks durin
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/lustre/lnet/selftest/module.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lnet/s
[ added dri-devel ML to cc: ]
On Tuesday, September 19, 2017 10:32:01 PM Colin King wrote:
> From: Colin Ian King
>
> Don't populate the read-only const array post_divs on the stack,
> nstead make it static. Makes the object code smaller by 90 bytes:
>
> Before:
>text data bss
Hi Eric,
Are you okay with my changes/substitution of your key instantiation-state
patches?
David
---
Here's a collection of fixes for Linux keyrings, mostly thanks to Eric
Biggers, including:
(1) Fix a bunch of places where kernel drivers may access revoked user-type
keys and don't do it
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1077598
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/lustre/lustre/osc/osc_cache.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/lus
On 12/10/17 17:17, Bartlomiej Zolnierkiewicz wrote:
>
> [ added dri-devel ML to cc: ]
>
> On Tuesday, September 19, 2017 10:32:01 PM Colin King wrote:
>> From: Colin Ian King
>>
>> Don't populate the read-only const array post_divs on the stack,
>> nstead make it static. Makes the object code sm
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1271166
Addresses-Coverity-ID: 1271167
Addresses-Coverity-ID: 1271168
Addresses-Coverity-ID: 1271169
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/lustre/l
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/lustre/lnet/selftest/conctl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/lustre/lnet/selftest/conctl.c
b/d
On Mon, Sep 11, 2017 at 11:05:26PM -0600, Ross Zwisler wrote:
> The following commit:
>
> commit 9b7365fc1c82 ("ext4: add FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR
> interface support")
>
> added several defines related to extended attributes to ext4.h. They were
> added within an #ifndef FS_IOC_FSGET
[ added dri-devel ML to cc: ]
On Tuesday, September 12, 2017 07:39:30 AM Christophe JAILLET wrote:
> If 'dmam_alloc_attrs()' fails, we must go through the error handling code,
> as done elsewhere in this function. Otherwise, there is a resource leak.
>
> Signed-off-by: Christophe JAILLET
> ---
When a exception is trapped to EL2, hardware uses ELR_ELx to hold
the current fault instruction address. If KVM wants to inject a
abort to 32 bit guest, it needs to set the LR register for the
guest to emulate this abort happened in the guest. Because ARM32
architecture is Multi-pipeline, so the
Sorry, I didn't manage to include the patches because stgit doesn't consider:
Cc: [v2.6.38+]
to be a valid email :-/
submitting-patches.rst and stable-kernel-rules.rst state this:
Cc: sta...@vger.kernel.org
or this:
Cc: # 3.3.x
David
On Thursday, October 12, 2017 05:17:49 PM Colin Ian King wrote:
> On 12/10/17 17:17, Bartlomiej Zolnierkiewicz wrote:
> >
> > [ added dri-devel ML to cc: ]
> >
> > On Tuesday, September 19, 2017 10:32:01 PM Colin King wrote:
> >> From: Colin Ian King
> >>
> >> Don't populate the read-only const
On Tue, Oct 03, 2017 at 08:54:19PM -0700, Ricardo Neri wrote:
> Obtain the default values of the address and operand sizes as specified in
> the D and L bits of the the segment descriptor selected by the register
> CS. The function can be used for both protected and long modes.
> For virtual-8086 m
If the TSC has already been determined to be unstable, then checking
TSC ADJUST values is a waste of time and generates unnecessary error
messages.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Russ Anderson
Reviewed-by: Peter Zijlstra
---
v2: Add check_tsc_unstable to
[Patches merged against 4.14.0-rc4]
The UV BIOS goes to considerable effort to get the TSC synchronization
accurate across the entire system. Included in that are multiple chassis
that can have 32+ sockets. The architecture does support an external
high resolution clock to aid in maintaining th
Prior to the TSC ADJUST MSR being available, the method to set TSC's in
sync with each other naturally caused a small skew between cpu threads.
This was NOT a firmware bug at the time so introducing a whole avalanche
of alarming warning messages might cause unnecessary concern and customer
complain
On systems where multiple chassis are reset asynchronously, and thus
the TSC counters are started asynchronously, the offset needed to
convert to TSC to ART would be different. Disable ART in that case
and rely on the TSC counters to supply the accurate time.
Signed-off-by: Mike Travis
Reviewed-
Add a flag to indicate and process that TSC counters are on chassis
that reset at different times during system startup. Therefore which
TSC ADJUST values should be zero is not predictable.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Russ Anderson
Reviewed-by: Andrew
Insert a check early in UV system startup that checks whether BIOS was
able to obtain satisfactory TSC Sync stability. If not, it usually
is caused by an error in the external TSC clock generation source.
In this case the best fallback is to use the builtin hardware RTC
as the kernel will not be a
On 10/12/2017 7:14 AM, Richard Guy Briggs wrote:
> Containers are a userspace concept. The kernel knows nothing of them.
>
> The Linux audit system needs a way to be able to track the container
> provenance of events and actions. Audit needs the kernel's help to do
> this.
>
> Since the concept o
On 10/12/2017 8:22 AM, Thomas Gleixner wrote:
On Thu, 12 Oct 2017, Mike Travis wrote:
On 10/12/2017 4:17 AM, Thomas Gleixner wrote:
On Thu, 5 Oct 2017, mike.tra...@hpe.com wrote:
@@ -89,6 +93,10 @@ bool tsc_store_and_check_tsc_adjust(bool
if (!boot_cpu_has(X86_FEATURE_TSC_ADJUST))
On Thu, Oct 12, 2017 at 03:54:48PM +, Aleksandar Markovic wrote:
> > This patch fixes something, I think it should
> > a) be clear in the commit message what is fixed
> > b) be tagged for stable (though that can always be done
> > retrospectively)
>
> If you agree, I am going to submit v2 of t
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1373894
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/rtl8188eu/hal/usb_halinit.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/rtl81
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/rtlwifi/halmac/halmac_88xx/halmac_api_88xx.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/rtlwifi/halmac/ha
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/vt6656/card.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/vt6656/card.c b/drivers/staging/vt6656/card.c
in
On 10/11/2017 6:08 PM, Bjorn Helgaas wrote:
> I think this series makes a lot of sense overall; thanks for doing
> this work! I had a few comments on the individual patches.
>
> (This response would ordinarily be to the cover letter, but there
> isn't one, so I'm just responding to the first patc
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/comedi/drivers/s526.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/comedi/drivers/s526.c
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/lustre/lustre/ldlm/ldlm_request.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_reques
On Tue, Oct 03, 2017 at 11:35:36AM +0300, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v1:
> - Fixed typo in commit message
> - Separated from the 'dmaengine: core/edma/omap-dma: maximum SG len reporting'
> series
>
> Both eDMA and sDMA have limit on the maximum burst size. The two patch
> imp
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1077604
Addresses-Coverity-ID: 1077605
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/lustre/lnet/selftest/rpc.c | 13 +
1 file changed, 9 inser
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/lustre/lnet/lnet/net_fault.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/lustre/lnet/lnet/net_fault.c
b/dri
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/rtlwifi/halmac/rtl_halmac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtlwifi/halmac/rtl_h
On 10/11/2017 5:00 PM, Bjorn Helgaas wrote:
> On Sat, Sep 23, 2017 at 08:16:55PM -0400, Sinan Kaya wrote:
>> pci_flr_wait() and pci_af_flr() functions assume graceful return even
>> though the device is inaccessible under error conditions.
>>
>> Return -ENOTTY in error cases so that __pci_reset_fun
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/lustre/lustre/llite/namei.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/lli
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/staging/lustre/lustre/ptlrpc/pack_generic.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/lustre
In case of failure in loading customize topology firmware, dfw_sst.bin
gets loaded. However, current log provides this message as error even
after successfully falling back to default topology "dfw_sst.bin".
Hence to convey proper message, changing log level and message.
Signed-off-by: Chintan Pa
From: Colin Ian King
The variable offset is being assigned and not being used; it should
be passed as the 2nd argument to call to function nitrox_write_csr
but has been omitted. Fix this.
Cleans up clang warning: Value stored to 'offset' is never read
Fixes: 14fa93cdcd9b ("crypto: cavium - Add
[ Resending again, including linux...@vger.kernel.org this time ]
From: Steven Rostedt (VMware)
Commit 74704ac6 ("tracing, perf: Add more power related events") added
new events, among them were trace_clock_enable, trace_clock_disable and
trace_clock_set_rate. In the last 7 years, nothing has u
On 10/11/2017 6:06 PM, Bjorn Helgaas wrote:
>> static int pci_pm_reset(struct pci_dev *dev, int probe)
>> {
>> +unsigned int delay = dev->d3_delay;
>> u16 csr;
>>
>> if (!dev->pm_cap || dev->dev_flags & PCI_DEV_FLAGS_NO_PM_RESET)
>> @@ -3988,7 +3989,10 @@ static int pci_pm_reset(st
On 10/12/2017 07:41 AM, Julien Thierry wrote:
> Hi Jim,
>
> On 11/10/17 23:34, Jim Quinlan wrote:
>> From: Florian Fainelli
>>
>> This commit adds a memory API suitable for ascertaining the sizes of
>> each of the N memory controllers in a Broadcom STB chip. Its first
>> user will be the Broadco
On 10/12/2017 09:35 AM, Shuah Khan wrote:
> On 10/12/2017 09:25 AM, Xin Long wrote:
>> On Thu, Oct 12, 2017 at 11:18 PM, Andreas Radke
>> wrote:
>>> Building the 4.9.x kernel package for Arch Linux 4.9.55 gives this IPv4
>>> error here:
>>>
>>> Job for dhcpd4.service failed because the control pr
From: Colin Ian King
Variable qim is assigned but never read, it is redundant and can
be removed.
Cleans up clang warning: Value stored to 'qim' is never read
Fixes: 4b394a232df7 ("crypto: ccp - Let a v5 CCP provide the same function as
v3")
Signed-off-by: Colin Ian King
---
drivers/crypto/c
On 11 October 2017 at 10:02, Peter Zijlstra wrote:
> On Wed, Aug 16, 2017 at 03:20:36PM -0600, Mathieu Poirier wrote:
>
>> In this set the problem is addressed by relying on existing list of tasks
>> (sleeping or not) already maintained by CPUsets.
>
> Right, that's a much saner approach :-)
Luca
Replaced by pr_err usage in commit ef51042472f5 ("block, dax: move
"select DAX" from BLOCK to FS_DAX")
Signed-off-by: Rakesh Pandit
Acked-by: Ross Zwisler
---
Al, May you consider queuing this for v4.15 ? Thank you.
fs/block_dev.c | 12
include/linux/blkdev.h | 11 ---
On Sun, Sep 24, 2017 at 08:26:41AM +0200, Christophe JAILLET wrote:
> All sanity checks in this function set 'sdmac->status = DMA_ERROR' if
> something looks wrong, except if the byte count or the address don't match
> the bus width.
>
> Fix it and report the error in status in such a case.
>
> S
Hi Joel, Atish,
Moving off-line discussions to LKML, just so everyone's on the same page,
I actually like this version now and it is outperforming my previous
code, so I am on board with this version. It makes the code simpler too.
Since we need a fast way of returning an idle cpu in select_idle
In preparation to enabling -Wimplicit-fallthrough, this patchset aims
to mark switch cases where we are expecting to fall through.
In Kees Cook words:
"This is an unfortunate omission in the C language, and thankfully both
gcc and clang have stepped up to solve this the same way static
analyzers h
Hello, Ingo,
This v2 urgent pull request contains five commits that fix a problem
that arose when designing requested extensions to sys_membarrier()
to allow JITs to efficiently flush old code from instruction caches.
Several potential algorithms are much less painful if the user register
intent t
On Mon, 2 Oct 2017 17:44:17 -0600
Shuah Khan wrote:
> Update to include details on make O=dir support and other changes improve
> test results output.
So the three patches you sent me appear to be a part of a larger series
that I didn't get. I'll assume you want me to apply these three...
>
On Thursday, October 12, 2017, Nicolas Pitre wrote:
> Small embedded systems typically execute the kernel code in place (XIP)
> directly from flash to save on precious RAM usage. This adds the ability
> to consume filesystem data directly from flash to the cramfs filesystem
> as well. Cramfs is par
From: Colin Ian King
The pointer vf_info is being assigned but never read, it is redundant
and therefore can be removed.
Cleans up clang warning: Value stored to 'vf_info' is never read
Fixes: ed8ccaef52fa ("crypto: qat - Add support for SRIOV")
Signed-off-by: Colin Ian King
---
drivers/crypt
On Wed, 11 Oct 2017, Josh Poimboeuf wrote:
> I failed to add the slab maintainers to CC on the last attempt. Trying
> again.
Hmmm... Yea. SLOB is rarely used and tested. Good illustration of a simple
allocator and the K&R mechanism that was used in the early kernels.
> > Adding the slub mainta
Issuing metdata or otherwise shared IOs from !root cgroup can lead to
priority inversion. This patch ensures that those IOs are always
issued from the root cgroup.
v3: Dropped unnecessary btree_inode handling as suggested by David
Sterba.
v2: Fixed missing @bh in submit_bh_blkcg_css() call.
On 11/10/17 23:34, Jim Quinlan wrote:
> The BrcmSTB driver needs to get ahold of a pointer to swiotlb_dma_ops.
> However, that variable is defined as static. Instead, we use
> arch_setup_dma_ops() to get the pointer to swiotlb_dma_ops. Since
> we also want our driver to be a separate module, we n
On 10/12/2017 11:02 AM, Jonathan Corbet wrote:
> On Mon, 2 Oct 2017 17:44:17 -0600
> Shuah Khan wrote:
>
>> Update to include details on make O=dir support and other changes improve
>> test results output.
>
> So the three patches you sent me appear to be a part of a larger series
> that I didn
Christian Brauner writes:
> On Wed, Oct 11, 2017 at 03:43:20PM -0500, Eric W. Biederman wrote:
>> "Serge E. Hallyn" writes:
>>
>> > Quoting Christian Brauner (christian.brau...@ubuntu.com):
>> >> We have quite some use cases where users already run into the current
>> >> limit for
>> >> {g,u}id
On Thu, 2017-10-12 at 10:54 -0600, Shuah Khan wrote:
> On 10/12/2017 09:35 AM, Shuah Khan wrote:
> > On 10/12/2017 09:25 AM, Xin Long wrote:
> > > On Thu, Oct 12, 2017 at 11:18 PM, Andreas Radke
> > > wrote:
> > > > Building the 4.9.x kernel package for Arch Linux 4.9.55 gives
> > > > this IPv4 er
On Thu, 2017-10-12 at 15:31 +0200, Arnd Bergmann wrote:
> On Thu, Jun 8, 2017 at 3:48 PM, Andy Shevchenko
> wrote:
>
> > diff --git a/kernel/debug/kdb/kdb_main.c
> > b/kernel/debug/kdb/kdb_main.c
> > index c8146d53ca67..2a6f12be79d8 100644
> > --- a/kernel/debug/kdb/kdb_main.c
> > +++ b/kernel/de
Hi,
On Thu, Oct 12, 2017 at 2:22 AM, Masahiro Yamada
wrote:
> Some $(call cc-option,...) are invoked very early, even before
> KBUILD_CFLAGS, etc. are initialized.
>
> The returned string from $(call cc-option,...) depends on
> KBUILD_CPPFLAGS, KBUILD_CFLAGS, and GCC_PLUGINS_CFLAGS.
>
> Since the
Hi,
On Thu, Oct 12, 2017 at 2:29 AM, Masahiro Yamada
wrote:
> The cache files are only cleaned away by "make clean". If you continue
> incremental builds, the cache files will grow up little by little.
> It is not a big deal in general use cases because $(call cc-option,...)
> in not added/delet
Hi all,
Today's linux-next merge of the wireless-drivers-next tree got a
conflict in:
drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c
between commit:
44fd09dad5d2b78e ("iwlwifi: nvm: set the correct offsets to 3168 series")
from the wireless-drivers tree and commit:
a2ff48af65ad661a
From: Xin Long
Date: Thu, 12 Oct 2017 23:25:10 +0800
> pls try revert:
> commit 02f7e4101092b88e57c73171174976c8a72a3eba
> Author: Eric Dumazet
> Date: Mon Oct 2 12:20:51 2017 -0700
>
> socket, bpf: fix possible use after free
>
> which caused a obvious issue in __sk_attach_prog():
>
On 10/12/2017 07:37 AM, Michal Hocko wrote:
> On Wed 11-10-17 18:46:11, Mike Kravetz wrote:
>> Add new MAP_CONTIG flag to mmap system call. Check for flag in normal
>> mmap flag processing. If present, pre-allocate a contiguous set of
>> pages to back the mapping. These pages will be used a faul
Hi all,
Today's linux-next merge of the wireless-drivers-next tree got a
conflict in:
drivers/net/wireless/intel/iwlwifi/cfg/a000.c
between commit:
44fd09dad5d2b78ef ("iwlwifi: nvm: set the correct offsets to 3168 series")
from the wireless-drivers tree and commit:
dd05f9aab4426ff1 ("i
On Tue, 10 Oct 2017 12:35:58 -0500
Tom Saeger wrote:
> Recently, while reading up on binfmt I attempted to open a document ref
> only to find it was invalid. I did a quick grep, found all the
> binfmt_misc related broken refs and sent a patch.
>
> Fine. Easy.
>
> Then I wondered, "how many bro
On Thu, Oct 12, 2017 at 8:54 PM, Will Deacon wrote:
> On Thu, Oct 12, 2017 at 07:41:12PM +0530, Ganapatrao Kulkarni wrote:
>> Extending json/jevent framework for parsing arm64 event files.
>> Adding jevents for ThunderX2 implementation defined PMU events.
>>
>> v8:
>>- Rename thunderx2 directo
On Tue, Sep 26, 2017 at 1:25 AM, Sergey Senozhatsky
wrote:
> Do not strdup() console options. It seems that the only reason for
> it to be strdup()-ed was a compilation warning: printk, UART and
> console drivers, for some reason, expect char pointer instead of
> const char pointer. So we can just
Hi all,
Today's linux-next merge of the wireless-drivers-next tree got a
conflict in:
drivers/net/wireless/intel/iwlwifi/iwl-config.h
between commit:
dd05f9aab4426f ("iwlwifi: pcie: dynamic Tx command queue size")
from the wireless-drivers tree and commit:
44fd09dad5d2b7 ("iwlwifi: nv
On Thu, 12 Oct 2017 15:00:06 +1100 (AEDT)
Finn Thain wrote:
> CONFIG_BLK_DEV_HD_IDE was removed in commit 80aa31cb460d ("ide:
> remove CONFIG_BLK_DEV_HD_IDE config option (take 2)") but the ide-cd
> documentation was not updated and still asks users to disable it,
> which is misleading and inv
On Tue, Sep 26, 2017 at 3:40 AM, Stewart Smith
wrote:
> There are two types of memory reservations firmware can ask the kernel
> to make in the device tree: static and dynamic.
> See Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
>
> If you have greater than 16 entries in /r
> "Gustavo A. R. Silva" hat am 12. Oktober 2017 um
> 18:16 geschrieben:
>
>
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Signed-off-by: Gustavo A. R. Silva
> ---
> drivers/staging/vc04_services/interface/vchiq_arm/vchiq
401 - 500 of 970 matches
Mail list logo
