When gcc considers the size of a function for inlining decisions, it
apparently considers *all* sections. Since the kernel extensively uses
sections for things other than code (e.g., exception-table, bug-table), the
optimality of these decisions seem questionable to me.
The objtool’s sections may
On 5/1/2018 4:22 AM, Andrew Morton wrote:
On Mon, 16 Apr 2018 16:29:02 +0530 Chintan Pandya
wrote:
vunmap does page table clear operations twice in the
case when DEBUG_PAGEALLOC_ENABLE_DEFAULT is enabled.
So, clean up the code as that is unintended.
As a perf gain, we save few us. Below f
> On 1 May 2018, at 06:38, jackm wrote:
>
> On Mon, 30 Apr 2018 13:10:49 -0400
> Doug Ledford wrote:
>
> Looks good!
Yes, absolutely!
Håkon
>
> -Jack
>
>> On Mon, 2018-04-30 at 08:49 -0600, Jason Gunthorpe wrote:
>>> On Mon, Apr 23, 2018 at 10:16:18PM +0300, jackm wrote:
>>>
>> TIDs
On Wed, 25 Apr 2018, Yang Shi wrote:
> Since tmpfs THP was supported in 4.8, hugetlbfs is not the only
> filesystem with huge page support anymore. tmpfs can use huge page via
> THP when mounting by "huge=" mount option.
>
> When applications use huge page on hugetlbfs, it just need check the
> f
On 1 May 2018 12:53:07 AM IST, Greg Kroah-Hartman
wrote:
>This is the start of the stable review cycle for the 3.18.108 release.
>There are 25 patches in this series, all will be posted as a response
>to this one. If anyone has any issues with these being applied, please
>let me know.
>
>Respons
Hi Nipun,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc3 next-20180430]
[cannot apply to iommu/next glikely/devicetree/next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the
Hi all,
Changes since 20180430:
The rdma tree gained a conflict against the rdma-fixes tree.
Non-merge commits (relative to Linus' tree): 3348
3188 files changed, 126791 insertions(+), 59113 deletions(-)
I
Hi Miquèl,
Thank you for your response and feedback. I've modified the fix based on your
comments.
Please see the updated patch file at the end of this message (also in
attachment).
My answers to your comments/questions are inline in the previous message.
The new patch is rebased on top of v
Add driver providing access to EEPROMs connected to RAVE SP devices
Cc: Srinivas Kandagatla
Cc: linux-kernel@vger.kernel.org
Cc: Chris Healy
Cc: Lucas Stach
Cc: Aleksander Morgado
Signed-off-by: Andrey Smirnov
---
drivers/nvmem/Kconfig | 6 +
drivers/nvmem/Makefile | 3 +
Srinivas:
This series is a third iteration of the patchset adding NVMEM support
for EEPROMs connected to RAVE SP MFD device (support for which landed
in 4.15).
Chagnes since [v2]:
- Added verbiage about data cells, fixed captial case hex
number as well as lack of address in nod
Add Device Tree bindings for RAVE SP EEPROM driver - an MFD cell of
parent RAVE SP driver (documented in
Documentation/devicetree/bindings/mfd/zii,rave-sp.txt).
Cc: Srinivas Kandagatla
Cc: linux-kernel@vger.kernel.org
Cc: Chris Healy
Cc: Lucas Stach
Cc: Aleksander Morgado
Cc: Rob Herring
Cc:
On 5/1/2018 4:34 AM, Andrew Morton wrote:
should check for it and do a WARN_ONCE so it gets fixed.
Yes, that was an idea in discussion but I've been suggested that it
could be intentional. But since you are raising this, I will try to dig
once again and share a patch with WARN_ONCE if passing
From: Amit Nischal
The default behavior of the GDSC enable/disable sequence is to
poll the status bits of either the actual GDSCR or the
corresponding HW_CTRL registers.
On targets which have support for a CFG_GDSCR register, the
status bits might not show the correct state of the GDSC,
especial
Hello Doug,
Thanks for the comments, I have based my latest patch on top of the
earlier patches (clk-qcom-sdm845 branch of clk-next).
On 5/1/2018 12:12 AM, Doug Anderson wrote:
Hi,
On Fri, Apr 27, 2018 at 1:19 AM, Taniya Das wrote:
-static int gdsc_is_enabled(struct gdsc *sc, unsigned int
Hi Miquèl and Boris,
Thank you for your response and feedback. I've modified the fix based on your
comments.
Please see the updated patch file at the end of this message (also in
attachment).
My answers to your comments/questions are inline in the previous message.
Here is the answer to Bori
Hello,
syzbot found the following crash on:
HEAD commit:8188fc8bef8c Merge
git://git.kernel.org/pub/scm/linux/kerne...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?id=5093449355231232
kernel config:
https://syzkaller.appspot.com/x/.config?id=64935577
On Mon, 30 Apr 2018 13:10:49 -0400
Doug Ledford wrote:
Looks good!
-Jack
> On Mon, 2018-04-30 at 08:49 -0600, Jason Gunthorpe wrote:
> > On Mon, Apr 23, 2018 at 10:16:18PM +0300, jackm wrote:
> >
> > > > > TIDs need to be globally unique on the entire machine.
> > > Jason, that is not ex
In tipc_link_xmit(), the member field "len" of l->backlog[imp] must
be less than the member field "limit" of l->backlog[imp] when imp is
equal to TIPC_SYSTEM_IMPORTANCE. Otherwise, an error code, i.e., -ENOBUFS,
is returned. This is enforced by the security check. However, at the end
of tipc_link_x
On 04/30/2018 08:00 PM, Manivannan Sadhasivam wrote:
> 1. Fix Kconfig dependency for Actions Semi S900 pinctrl driver which
> generates below warning in x86:
>
> WARNING: unmet direct dependencies detected for PINCTRL_OWL
> Depends on [n]: PINCTRL [=y] && (ARCH_ACTIONS || COMPILE_TEST [=n]) && O
On Apr 30, 2018, at 21:52, NeilBrown wrote:
>
> lu_object maintains 2 lru counts.
> One is a per-bucket lsb_lru_len.
> The other is the per-cpu ls_lru_len_counter.
>
> The only times the per-bucket counters are use are:
> - a debug message when an object is added
> - in lu_site_stats_get when al
On Apr 30, 2018, at 21:52, NeilBrown wrote:
>
> This data structure only needs to be public so that
> various modules can access a wait queue to wait for object
> destruction.
> If we provide a function to get the wait queue, rather than the
> whole bucket, the structure can be made private.
>
>
On Apr 30, 2018, at 16:56, Wenwen Wang wrote:
>
> In ll_dir_ioctl(), the object lumv3 is firstly copied from the user space
> using Its address, i.e., lumv1 = &lumv3. If the lmm_magic field of lumv3 is
> LOV_USER_MAGIC_V3, lumv3 will be modified by the second copy from the user
> space. The secon
On Apr 30, 2018, at 21:52, NeilBrown wrote:
>
> Rather than storing the name of a namespace in the
> hash table, store it directly in the namespace.
> This will allow the hashtable to be changed to use
> rhashtable.
>
> Signed-off-by: NeilBrown
Reviewed-by: Andreas Dilger
> ---
> drivers/sta
d_splice_alias() can return an ERR_PTR().
If it does while debugging is enabled, the following
CDEBUG() will dereference that error and crash.
So add appropriate checking, and provide a separate
debug message for the error case.
Reported-by: James Simmons
Fixes: e9d4f0b9f559 ("staging: lustre: l
There is no longer any need to keep this code separate,
and now we can remove linux-module.c
Signed-off-by: NeilBrown
---
.../staging/lustre/include/linux/libcfs/libcfs.h |4
drivers/staging/lustre/lnet/libcfs/Makefile|1
.../lustre/lnet/libcfs/linux/linux-module.c|
Both the 'next' and the 'show' functions for the dump_page_cache
seqfile perform a lookup based on the current file index. This is
needless duplication.
The reason appears to be that the state that needs to be communicated
from "next" to "show" is two pointers, but seq_file only provides for
a si
The ioctl handler for the misc device is in lnet/libcfs/module.c
but is it registered in lnet/libcfs/linux/linux-module.c.
Keeping related code together make maintenance easier, so move the
code.
Signed-off-by: NeilBrown
---
.../staging/lustre/include/linux/libcfs/libcfs.h |2 -
.../lust
lu_object_new() duplicates a lot of code that is in
lu_object_find_at().
There is no real need for a separate function, it is simpler just
to skip the bits of lu_object_find_at() that we don't
want in the LOC_F_NEW case.
Signed-off-by: NeilBrown
---
drivers/staging/lustre/lustre/obdclass/lu_obje
This data structure only needs to be public so that
various modules can access a wait queue to wait for object
destruction.
If we provide a function to get the wait queue, rather than the
whole bucket, the structure can be made private.
Signed-off-by: NeilBrown
---
drivers/staging/lustre/lustre/
The dump_page_cache debugfs file allocates and frees an 'env' in each
call to vvp_pgcache_start,next,show. This is likely to be fast, but
does introduce the need to check for errors.
It is reasonable to allocate a single 'env' when the file is opened,
and use that throughout.
So create 'seq_priv
The current retry logic, to wait when a 'dying' object is found,
spans multiple functions. The process is attached to a waitqueue
and set TASK_UNINTERRUPTIBLE in htable_lookup, and this status
is passed back through lu_object_find_try() to lu_object_find_at()
where schedule() is called and the pro
lu_object maintains 2 lru counts.
One is a per-bucket lsb_lru_len.
The other is the per-cpu ls_lru_len_counter.
The only times the per-bucket counters are use are:
- a debug message when an object is added
- in lu_site_stats_get when all the counters are combined.
The debug message is not essenti
First 6 patches are clean-up patches that I pulled out
of my rhashtable series. I think these stand alone as
good cleanups, and having them upstream makes the rhashtable
series shorter to ease further review.
Second 2 are revised versions of patches I sent previously that
had conflicts with other
Rather than storing the name of a namespace in the
hash table, store it directly in the namespace.
This will allow the hashtable to be changed to use
rhashtable.
Signed-off-by: NeilBrown
---
drivers/staging/lustre/lustre/include/lustre_dlm.h |5 -
drivers/staging/lustre/lustre/ldlm/ldlm_
On Mon, Apr 30, 2018 at 8:46 PM Randy Dunlap wrote:
> On 04/30/2018 06:42 PM, Joel Fernandes wrote:
> > Split reset functions into seperate functions in preparation
> > of future patches that need to do tracer specific reset.
> >
> Hi,
> Since you are updating patches anyway, please
> s/seperate
On 04/30/2018 06:42 PM, Joel Fernandes wrote:
> Split reset functions into seperate functions in preparation
> of future patches that need to do tracer specific reset.
>
Hi,
Since you are updating patches anyway, please
s/seperate/separate/.
thanks,
--
~Randy
With kernel 4.17.0-rc3, I noted the following warning from driver i915.
kernel: [ cut here ]
kernel: Could not determine valid watermarks for inherited state
kernel: WARNING: CPU: 3 PID: 224 at drivers/gpu/drm/i915/intel_display.c:14584
intel_modeset_init+0x3be/0x1060 [i9
Sudip,
> v1: Only M500IT MU01 was blacklisted.
>
> v2: Whitelist M500IT BG02 and M500DC and then blacklist all other Micron.
I think my preference would be to blacklist M500IT with the MU01
firmware (which Micron said was affected) and rely on the "Micron*"
fallthrough further down for the rest
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Monday, April 30, 2018 1:30 PM
> To: Lee Jones ; Daniel Thompson
> ; Jingoo Han ;
> Bartlomiej Zolnierkiewicz ; linux-
> ker...@vger.kernel.org; dri-de...@lists.freedesktop.org; linux-
> fb...@vger.kernel.org
> Cc: Krzysztof Kozlow
On Monday, April 30, 2018 1:30 PM, Krzysztof Kozlowski wrote:
>
> The driver for S6E63M0 AMOLED LCD panel is not used. It does not
> support DeviceTree and respective possible users (S5Pv210 Aquila and
> Goni boards) are DeviceTree-only.
>
> Suggested-by: Marek Szyprowski
> Cc: Marek Szyprowski
list_for_each_entry_from_rcu() is an RCU version of
list_for_each_entry_from(). It walks a linked list under rcu
protection, from a given start point.
It is similar to list_for_each_entry_continue_rcu() but starts *at*
the given position rather than *after* it.
Naturally, the start point must b
On Mon, Apr 30, 2018 at 4:35 PM Jason Gunthorpe wrote:
> On Wed, Apr 25, 2018 at 03:33:39PM -0700, Greg Thelen wrote:
> > INFINIBAND_SRPT code depends on INFINIBAND_ADDR_TRANS provided symbols.
> > So declare the kconfig dependency. This is necessary to allow for
> > enabling INFINIBAND without
1. Fix Kconfig dependency for Actions Semi S900 pinctrl driver which
generates below warning in x86:
WARNING: unmet direct dependencies detected for PINCTRL_OWL
Depends on [n]: PINCTRL [=y] && (ARCH_ACTIONS || COMPILE_TEST [=n]) && OF [=n]
Selected by [y]:
- PINCTRL_S900 [=y] && PINCTRL [=y]
I've made version 12 of the XArray and page cache conversion available at
git://git.infradead.org/users/willy/linux-dax.git xarray-20180430
Changes since v11:
- At Goldwyn's request, renamed xas_for_each_tag -> xas_for_each_tagged,
xas_find_tag -> xas_find_tagged
On Mon, Apr 30, 2018 at 6:42 PM Joel Fernandes wrote:
> In recent tests with IRQ on/off tracepoints, a large performance
> overhead ~10% is noticed when running hackbench. This is root caused to
> calls to rcu_irq_enter_irqson and rcu_irq_exit_irqson from the
> tracepoint code. Following a long d
Make sure the DVBxB bit 5, PGOOD mask, is set before changing voltage
on the buck converters. If the PGOOD mask bit is not set, the PMIC may
deassert the PGOOD signal during the voltage transition.
On systems that use the PGOOD signal as a power OK indication for the
board or SoC, which should be
Hi Vitaly,
On 04/30/2018 03:58 AM, Vitaly Wool wrote:
Do not try to optimize in-page object layout while the page is
under reclaim. This fixes lock-ups on reclaim and improves reclaim
performance at the same time.
A heads-up: z3fold is still crashing (due to a NULL pointer access) under
heavy
I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
CONFIG_PREEMPTIRQ_EVENTS=y.
$ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
Cc: Steven Rostedt
Cc: Peter Zilstra
Cc: Ingo Molnar
Cc: Mathieu Desnoyers
Cc: Tom Zanussi
Cc: Namhyung Kim
Cc: Thomas Glexiner
Cc
From: "Paul E. McKenney"
This is needed for a future tracepoint patch that uses srcu, and to make
sure it doesn't call into lockdep.
tracepoint code already calls notrace variants for rcu_read_lock_sched
so this patch does the same for srcu which will be used in a later
patch. Keeps it consisten
This is the next revision of preempt/irq tracepoint centralization and
unified usage across the kernel [1].
The preempt/irq tracepoints exist but not everything in the kernel is
using it. This makes things not work simultaneously (for ex, only either
lockdep or irqsoff events can be used at a time)
In this series, we are making lockdep use an rcuidle tracepoint. For
this reason we need a notrace variant of srcu_dereference since
otherwise we get lockdep splats since lockdep hooks may not have run
yet. This patch adds the needed variant.
Cc: Steven Rostedt
Cc: Peter Zilstra
Cc: Ingo Molnar
In recent tests with IRQ on/off tracepoints, a large performance
overhead ~10% is noticed when running hackbench. This is root caused to
calls to rcu_irq_enter_irqson and rcu_irq_exit_irqson from the
tracepoint code. Following a long discussion on the list [1] about this,
we concluded that srcu is
Split reset functions into seperate functions in preparation
of future patches that need to do tracer specific reset.
Cc: Steven Rostedt
Cc: Peter Zilstra
Cc: Ingo Molnar
Cc: Mathieu Desnoyers
Cc: Tom Zanussi
Cc: Namhyung Kim
Cc: Thomas Glexiner
Cc: Boqun Feng
Cc: Paul McKenney
Cc: Freder
This patch detaches the preemptirq tracepoints from the tracers and
keeps it separate.
Advantages:
* Lockdep and irqsoff event can now run in parallel since they no longer
have their own calls.
* This unifies the usecase of adding hooks to an irqsoff and irqson
event, and a preemptoff and preempt
On Wed, Apr 18, 2018 at 2:02 AM Masami Hiramatsu
wrote:
> On Mon, 16 Apr 2018 21:07:47 -0700
> Joel Fernandes wrote:
> > With TRACE_IRQFLAGS, we call trace_ API too many times. We don't need
> > to if local_irq_restore or local_irq_save didn't actually do anything.
> >
> > This gives around a 4
This series adds support for generic binding for pinctrl bcm2835 driver,
and add the code for set output buffer of a pin using the output-low and
output-high generic properties.
Tested on Raspberry Pi Zero W, based on bcm2835 SoC.
Changes since v6:
- I was dumb and calculate the PIN_CONFIG_END (x
Hi Cong,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on v4.17-rc3 next-20180430]
[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
Hello,
Kconfiglib (https://github.com/ulfalizer/Kconfiglib) now has a
terminal menuconfig implementation, implemented in plain curses
(which is in the Python standard library).
The interface should feel familiar to people used to mconf. It has
some features that mconf lacks:
- Seamless resizin
On Tue, 2018-05-01 at 10:10 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the rdma tree got a conflict in:
>
> drivers/infiniband/sw/rxe/rxe_resp.c
>
> between commit:
>
> 9fd4350ba895 ("B/rxe: avoid double kfree_skb")
>
> from the rdma-fixes tree and commit:
>
On Mon, Apr 30, 2018 at 12:23:42PM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.39 release.
> There are 91 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
To keep driver up to date we add generic pinctrl binding support, which
covers the features used in this driver and has additional node properties
that this SoC has compatibility, so enabling future implementations of
these properties without the need to create new node properties in the
device tre
Properties to set initial value of pin output buffer.
This can be useful for configure hardware in overlay files, and in early
boot for checking it states in QA sanity tests.
Signed-off-by: Matheus Castello
Reviewed-by: Eric Anholt
---
drivers/pinctrl/bcm/pinctrl-bcm2835.c | 5 +
1 file cha
Hello Thomas,
I have sent a new version trying to address your feedback. Made this
more cleaner also. Would be great if you could let me know any feedback.
Regards,
Vikas
On Fri, 20 Apr 2018, Vikas Shivappa wrote:
> Sending the second version of MBA software controller which addresses
> the f
I found the description of the table_size argument to the function
acpi_parse_entries_array() unclear and ambiguous. This is a minor
documentation change to improve that description so I don't misuse
the argument again in the future, and it is hopefully clearer to
other future users.
Signed-off-b
There have been multiple reports of the following error message:
[0.068293] Error parsing PCC subspaces from PCCT
This error message is not correct. In multiple cases examined, the PCCT
(Platform Communications Channel Table) concerned is actually properly
constructed; the problem is that ac
This set of patches provide some cleanup in ACPI for minor issues
found while correcting a bogus error message (the first two patches),
and the correction for the error message itself (patch 3/3). Note
that patches 1/3 and 2/3 are not required for 3/3 to work: 1/3 only
changes a comment and 2/3 ma
For ACPI tables that have subtables, acpi_parse_entries_array() gets used
to step through each of the subtables in memory. The primary loop for this
was checking that the beginning location of the subtable being examined
plus the length of struct acpi_subtable_header was not beyond the end of
the
On 2018-04-30 07:33, Rob Herring wrote:
On Fri, Apr 27, 2018 at 5:57 PM, wrote:
On 2018-04-27 07:21, Rob Herring wrote:
On Mon, Apr 23, 2018 at 04:09:31PM -0700, Rishabh Bhatnagar wrote:
Documentation for last level cache controller device tree bindings,
client bindings usage examples.
Si
Hi Cong,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on v4.17-rc3 next-20180430]
[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
Fixes: 601aedfafd22 ("sched/fair: make CFS bandwidth slice per cpu group")
Signed-off-by: Fengguang Wu
---
core.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index abc48d9..daa1843 100644
--- a/kernel/sched/core.c
+++ b/ker
Hi Cong,
I love your patch! Perhaps something to improve:
[auto build test WARNING on tip/sched/core]
[also build test WARNING on v4.17-rc3 next-20180430]
[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
On Mon 30 Apr 07:44 PDT 2018, Sibi Sankar wrote:
> Add all the necessary dt nodes to support SMEM driver
> on SDM845. It also adds the required memory carveouts
> so that the kernel does not access memory that is in
> use.
>
> Signed-off-by: Sibi Sankar
Reviewed-by: Bjorn Andersson
Regards,
B
On Tue, May 1, 2018 at 1:59 AM, Eric Anholt wrote:
> I had originally asked Stefan Schake to drop the pad field from the
> syncobj changes that just landed, because I couldn't come up with a
> reason to align to 64 bits.
>
> Talking with Dave Airlie about the new v3d driver's submit ioctl, we
> ca
Hi all,
Today's linux-next merge of the rdma tree got a conflict in:
drivers/infiniband/sw/rxe/rxe_resp.c
between commit:
9fd4350ba895 ("B/rxe: avoid double kfree_skb")
from the rdma-fixes tree and commit:
2e47350789eb ("IB/rxe: optimize the function duplicate_request")
from the rdma t
On Fri, Apr 27, 2018 at 01:51:47PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Apr 27, 2018 at 10:44:58AM +0200, Arnd Bergmann wrote:
> > On Fri, Apr 27, 2018 at 10:30 AM, Greg Kroah-Hartman
> > wrote:
> > > On Fri, Apr 27, 2018 at 10:17:42AM +0200, Arnd Bergmann wrote:
> > >> On Fri, Apr 27, 2018
On Mon, 30 Apr 2018 19:58:58 -0400 Steven Rostedt wrote:
> On Mon, 30 Apr 2018 16:26:58 -0700
> Andrew Morton wrote:
>
> > On Thu, 26 Apr 2018 16:26:19 -0400 Pavel Tatashin
> > wrote:
> >
> > > The following two bugs were reported by Fengguang Wu:
> > >
> > > kernel reboot-without-warning i
I had originally asked Stefan Schake to drop the pad field from the
syncobj changes that just landed, because I couldn't come up with a
reason to align to 64 bits.
Talking with Dave Airlie about the new v3d driver's submit ioctl, we
came up with a reason: sizeof() on 64-bit platforms may align to
On Mon, 30 Apr 2018 16:26:58 -0700
Andrew Morton wrote:
> On Thu, 26 Apr 2018 16:26:19 -0400 Pavel Tatashin
> wrote:
>
> > The following two bugs were reported by Fengguang Wu:
> >
> > kernel reboot-without-warning in early-boot stage, last printk:
> > early console in setup code
> >
> > htt
On 2018-05-01 00:54, Greg Kroah-Hartman wrote:
4.4-stable review patch. If anyone has any objections, please let me
know.
Hi Greg,
This is a dependency patch to the actual fix ,
[PATCH 2/2 - linux-stable-4.4] ath10k: rebuild crypto header in rx data
frames.
We would like both these patche
On Mon, Apr 30, 2018 at 12:24:11PM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.131 release.
> There are 44 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
Hi Bartosz,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc3 next-20180430]
[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
On Wed, 25 Apr 2018 22:13:53 +0800 Yang Shi wrote:
> Since tmpfs THP was supported in 4.8, hugetlbfs is not the only
> filesystem with huge page support anymore. tmpfs can use huge page via
> THP when mounting by "huge=" mount option.
>
> When applications use huge page on hugetlbfs, it just nee
On 04/27/2018 05:16 AM, Rafael J. Wysocki wrote:
> On Tue, Apr 24, 2018 at 9:35 PM, Al Stone wrote:
>> There have been multiple reports of the following error message:
>>
>> [0.068293] Error parsing PCC subspaces from PCCT
>>
>
> [cut]
>
>>
>> Tested on my personal laptop which showed the er
From: Wanpeng Li
Anthoine reported:
The period used by Windows change over time but it can be 1 milliseconds
or less. I saw the limit_periodic_timer_frequency print so 500
microseconds is sometimes reached.
As suggested by Paolo, lower the timer frequency limit to a
smaller interval of 200 ms
On 04/25/2018 10:49 AM, Peter Zijlstra wrote:
On Tue, Apr 24, 2018 at 02:45:50PM -0700, Subhra Mazumdar wrote:
So what you said makes sense in theory but is not borne out by real
world results. This indicates that threads of these benchmarks care more
about running immediately on any idle cpu
On Wed, Apr 25, 2018 at 03:33:39PM -0700, Greg Thelen wrote:
> INFINIBAND_SRPT code depends on INFINIBAND_ADDR_TRANS provided symbols.
> So declare the kconfig dependency. This is necessary to allow for
> enabling INFINIBAND without INFINIBAND_ADDR_TRANS.
>
> Signed-off-by: Greg Thelen
> Cc: Tar
The following changes since commit 0644f186fc9d77bb5bd198369e59fb28927a3692:
Merge tag 'for_linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost (2018-04-26 16:36:11
-0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git
On 04/27/2018 05:05 AM, Rafael J. Wysocki wrote:
> On Tue, Apr 24, 2018 at 9:35 PM, Al Stone wrote:
>> For ACPI tables that have subtables, acpi_parse_entries_array() gets used
>> to step through each of the subtables in memory. The primary loop for this
>> was checking that the beginning locatio
On Thu, 26 Apr 2018 16:26:19 -0400 Pavel Tatashin
wrote:
> The following two bugs were reported by Fengguang Wu:
>
> kernel reboot-without-warning in early-boot stage, last printk:
> early console in setup code
>
> http://lkml.kernel.org/r/20180418135300.inazvpxjxowog...@wfg-t540p.sh.intel.com
On 04/27/2018 05:04 AM, Rafael J. Wysocki wrote:
> On Tue, Apr 24, 2018 at 9:35 PM, Al Stone wrote:
>> I found the description of the table_size argument to the function
>> acpi_parse_entries_array() unclear and ambiguous. This is a minor
>> documentation change to improve that description so I d
> Turning these tests on will typically result in the link partner
> dropping the link with us, and the interface will be non-functional as
> far as the data path is concerned (similar to an isolation mode). This
> might warrant properly reporting that to user-space through e.g: a
> private IFF_* v
> +/* genphy_set_test - Make a PHY enter one of the standard IEEE defined
> + * test modes
> + * @phydev: the PHY device instance
> + * @test: the desired test mode
> + * @data: test specific data (none)
> + *
> + * This function makes the designated @phydev enter the desired standard
> + * 100Base
Hi Christoph,
Can you drop your "afs: simplify procfs code" patch please and replace with
these three? The patches are:
(1) Rearrange fs/afs/proc.c to get rid of the forward declarations and
simplify the commenting.
(2) Supply functions that allow writable net proc files to be created (
Implement namespacing within AFS, but don't yet let mounts occur outside
the init namespace. An additional patch will be required propagate the
network namespace across automounts.
Signed-off-by: David Howells
---
fs/afs/cell.c |4
fs/afs/cmservice.c |2
fs/afs/internal.h |
Provide two extra functions, proc_create_net_data_write() and
proc_create_net_single_write() that act like their non-write versions but
also set a write method in the proc_dir_entry struct.
An internal simple write function is provided that will copy its buffer and
hand it to the pde->write() meth
Rearrange fs/afs/proc.c to get rid of all the predeclarations.
Signed-off-by: David Howells
---
fs/afs/proc.c | 765 +
1 file changed, 330 insertions(+), 435 deletions(-)
diff --git a/fs/afs/proc.c b/fs/afs/proc.c
index 839a22280606..363
>
>
> Yes, I fixed the original false positive messages myself with the swiotlb
> maintainer and I was CCed in fixing the recent fallout from Chris changes as
> well.
So do we have a good summary of where this at now?
I'm getting reports on 4.16.4 still displaying these, what hammer do I
need to
Hi Bartosz,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc3 next-20180430]
[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
On Fri, 27 Apr 2018 03:42:41 +0400 Igor Stoppa wrote:
> These two patches were written in preparation for the creation of
> protectable memory, however their use is not limited to pmalloc and can
> improve the use of virtally contigous memory.
>
> The first provides a faster path from struct pag
On 04/30/2018 04:48 PM, Greg KH wrote:
> On Mon, Apr 30, 2018 at 04:17:19PM -0600, Shuah Khan (Samsung OSG) wrote:
>> Device is left in the busid_table after unbind and rebind. Rebind
>> initiates usb bus scan and the original driver claims the device.
>> After rescan the device should be deleted f
1 - 100 of 1117 matches
Mail list logo
