CONFIG_NET is a bool option, and this file is compiled only when
CONFIG_NET=y.
Remove #ifdef CONFIG_NET, which we know it is always met.
Signed-off-by: Masahiro Yamada
---
net/core/sysctl_net_core.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/net/core/sysctl_net_core.c b/net/core/sysc
On Mon, Jan 25, 2021 at 10:21:14PM +, Song Bao Hua (Barry Song) wrote:
> mlock, while certainly be able to prevent swapping out, it won't
> be able to stop page moving due to:
> * memory compaction in alloc_pages()
> * making huge pages
> * numa balance
> * memory compaction in CMA
Enabling th
On 1/25/21 6:11 PM, Andrew Morton wrote:
On Mon, 25 Jan 2021 09:12:56 -0500 Waiman Long wrote:
Yes, this patch should go to stable. I think the stable tree maintainers
will automatically pick up patches with the "Fixes" tag. That is why I
don't explicitly put a "cc:stable" line in the patch.
Add functions to unlock and wait for unlock of PG_fscache analogously with
those for PG_lock.
Signed-off-by: David Howells
---
include/linux/pagemap.h | 14 ++
mm/filemap.c| 18 ++
2 files changed, 32 insertions(+)
diff --git a/include/linux/pagemap.
On Mon, 25 Jan 2021 09:12:56 -0500 Waiman Long wrote:
> Yes, this patch should go to stable. I think the stable tree maintainers
> will automatically pick up patches with the "Fixes" tag. That is why I
> don't explicitly put a "cc:stable" line in the patch.
No. Both the Fixes: and the cc:stab
Hi Linus:
This push fixes a regression in the cesa driver.
The following changes since commit 382811940303f7cd01d0f3dcdf432dfd89c5a98e:
crypto: omap-sham - Fix link error without crypto-engine (2021-01-08 15:37:55
+1100)
are available in the Git repository at:
git://git.kernel.org/pub/scm
Provide a function, readahead_expand(), that expands the set of pages
specified by a readahead_control object to encompass a revised area with a
proposed size and length.
The proposed area must include all of the old area and may be expanded yet
more by this function so that the edges align on (tr
Export rw_verify_area() for so that cachefiles can use it before issuing
call_read_iter() and call_write_iter() to effect async DIO operations
against the cache.
Signed-off-by: David Howells
---
fs/internal.h |5 -
fs/read_write.c|1 +
include/linux/fs.h |1 +
3 files c
On 25.01.21 09:54, Donald Buczek wrote:
Dear Guoqing,
a colleague of mine was able to produce the issue inside a vm and were able to
find a procedure to run the vm into the issue within minutes (not unreliably
after hours on a physical system as before). This of course helped to pinpoint
t
Here's a set of patches to do two things:
(1) Add a helper library to handle the new VM readahead interface. This
is intended to be used unconditionally by the filesystem (whether or
not caching is enabled) and provides a common framework for doing
caching, transparent huge page
Make a netfs helper module to manage read request segmentation, caching
support and transparent huge page support on behalf of a network
filesystem.
Signed-off-by: David Howells
---
fs/netfs/Kconfig |8
1 file changed, 8 insertions(+)
create mode 100644 fs/netfs/Kconfig
diff --gi
In fsdax mode, the memory failure happens on block device. So, it is
needed to introduce an interface for block devices. Each kind of block
device can handle the memory failure in ther own ways.
Signed-off-by: Shiyang Ruan
---
include/linux/blkdev.h | 2 ++
1 file changed, 2 insertions(+)
dif
Pmem device could be a target of mapped device. In order to obtain
superblock on the mapped device, we introduce this to translate offset
from target device to md device.
Currently, we implement it on linear target, which is easy to do the
translation. Other targets will be supported in the futu
Obtain the superblock of a pmem disk, and call filesystem's
->corrupted_range() to handle the corrupted data.
Signed-off-by: Shiyang Ruan
---
block/genhd.c | 6 ++
drivers/nvdimm/pmem.c | 24
include/linux/genhd.h | 1 +
3 files changed, 31 insertions(+)
d
Memory failure occurs in fsdax mode will finally be handled in
filesystem. We introduce this interface to find out files or metadata
affected by the corrupted range, and try to recover the corrupted data
if possiable.
Signed-off-by: Shiyang Ruan
---
include/linux/fs.h | 2 ++
1 file changed, 2
This function is used to handle errors which may cause data lost in
filesystem. Such as memory failure in fsdax mode.
In XFS, it requires "rmapbt" feature in order to query for files or
metadata which associated to the corrupted data. Then we could call fs
recover functions to try to repair the
Since owner tarcking is triggerred by pmem device, these functions are
useless. So remove it.
Signed-off-by: Shiyang Ruan
---
fs/dax.c | 46 --
1 file changed, 46 deletions(-)
diff --git a/fs/dax.c b/fs/dax.c
index c64c3a0e76a6..e20a5df03eec 100644
-
On 1/25/21 12:56 PM, richard.g...@linux.intel.com wrote:
> From: Richard Gong
>
> Add COMMAND_AUTHENTICATE_BITSTREAM command flag for new added bitstream
> authentication feature. Authenticating a bitstream is to make sure a signed
> bitstream has the valid signatures.
>
> Except for the actual
With the support of ->rmap(), it is possible to obtain the superblock on
a mapped device.
If a pmem device is used as one target of mapped device, we cannot
obtain its superblock directly. With the help of SYSFS, the mapped
device can be found on the target devices. So, we iterate the
bdev->bd_h
The current memory_failure_dev_pagemap() can only handle single-mapped
dax page for fsdax mode. The dax page could be mapped by multiple files
and offsets if we let reflink feature & fsdax mode work together. So,
we refactor current implementation to support handle memory failure on
each file and
Call the ->memory_failure() which is implemented by pmem driver, in
order to finally notify filesystem to handle the corrupted data. The
handler which collects and kills processes are moved into
mf_dax_mapping_kill_procs(), which will be called by filesystem.
Keep the old handler in order to roll
When memory-failure occurs, we call this function which is implemented
by each kind of devices. For the fsdax case, pmem device driver
implements it. Pmem device driver will find out the block device where
the error page locates in, and try to get the filesystem on this block
device. And finally
This patchset is aimed to support shared pages tracking for fsdax.
Change from V1:
- Add the old memory-failure handler back for rolling back
- Add callback in MD's ->rmap() to support multiple mapping of dm device
- Add judgement for CONFIG_SYSFS
- Add pfn_valid() judgement in hwpoison_fi
On Thu, Jan 21, 2021 at 01:09:59PM -0800, Luck, Tony wrote:
> On Wed, Jan 20, 2021 at 01:18:12PM +0100, Borislav Petkov wrote:
> But, on a whim, I changed the type of mce_count from "int" to "atomic_t" and
> fixeed up the increment & clear to use atomic_inc_return() and atomic_set().
> See updated
On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson
> wrote:
> >
> > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > Mike Rapoport (3):
> > ...
> > > mm: fix initialization of struct page for holes in memory layout
> >
> > We ha
Hello Andre,
On 25/01/2021 15:18:02+, Andre Przywara wrote:
> Add the obvious compatible name to the existing RTC binding, and pair
> it with the existing H6 fallback compatible string, as the devices are
> compatible.
>
> Signed-off-by: Andre Przywara
> Acked-by: Rob Herring
> ---
> .../d
Disable use of the fscache I/O routined by the AFS filesystem. It's about
to transition to passing iov_iters down and fscache is about to have its
I/O path to use iov_iter, so all that needs to change.
Signed-off-by: David Howells
cc: linux-...@lists.infradead.org
---
fs/afs/file.c | 199 +++
Pass a pointer to the page being accessed into the dirty region helpers so
that the size of the page can be determined in case it's a transparent huge
page.
This also required the page to be passed into the afs_page_dirty trace
point - so there's no need to specifically pass in the index or privat
Add an iterator, ITER_XARRAY, that walks through a set of pages attached to
an xarray, starting at a given page and offset and walking for the
specified amount of bytes. The iterator supports transparent huge pages.
The caller must guarantee that the pages are all present and they must be
locked
On Fri, 4 Dec 2020 13:38:25 +0100 Marco Elver wrote:
> On Fri, Dec 04, 2020 at 01:18PM +0100, Anders Roxell wrote:
> > When building kfence the following error shows up:
> >
> > In file included from mm/kfence/report.c:13:
> > arch/arm64/include/asm/kfence.h: In function ‘kfence_protect_page’:
>
On Fri, Jan 22, 2021 at 6:26 PM Josh Poimboeuf wrote:
>
> On Fri, Jan 22, 2021 at 05:32:43PM -0800, Nick Desaulniers wrote:
> > > In this specific case, find_func_by_offset returns NULL for
> > > .text..L.cfi.jumptable.43 at addend 0x8, because Clang doesn't emit
> > > jump table symbols for stati
Stash the key used to authenticate read operations in the afs_read struct.
This will be necessary to reissue the operation against the server if a
read from the cache fails in upcoming cache changes.
Signed-off-by: David Howells
---
fs/afs/dir.c |3 ++-
fs/afs/file.c | 16 +++
On Fri, 15 Jan 2021 18:11:14 +0100, Konrad Dybcio wrote:
> PM8019 provides 6 MPPs. Add a compatible to support them.
>
> Signed-off-by: Konrad Dybcio
> ---
> Documentation/devicetree/bindings/pinctrl/qcom,pmic-mpp.txt | 1 +
> drivers/pinctrl/qcom/pinctrl-spmi-mpp.c | 1 +
>
On Mon, Jan 25, 2021 at 11:49 AM Michael Walle wrote:
>
> Am 2021-01-21 12:01, schrieb Geert Uytterhoeven:
> > Hi Saravana,
> >
> > On Thu, Jan 21, 2021 at 1:05 AM Saravana Kannan
> > wrote:
> >> On Wed, Jan 20, 2021 at 3:53 PM Michael Walle
> >> wrote:
> >> > Am 2021-01-20 20:47, schrieb Sarava
On 1/25/21 11:14 AM, Borislav Petkov wrote:
On Mon, Jan 25, 2021 at 05:41:04PM +0100, Rafael J. Wysocki wrote:
On Fri, Jan 22, 2021 at 7:05 PM Terry Bowman wrote:
From: Yazen Ghannam
Refactor duplicated GHES identity logic into is_ghes_type().
Signed-off-by: Yazen Ghannam
Reviewed-by: Robert
On Fri, 15 Jan 2021 18:11:13 +0100, Konrad Dybcio wrote:
> PM8019 provides 6 GPIOs. Add a compatible to support that.
>
> Signed-off-by: Konrad Dybcio
> ---
> Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 1 +
> drivers/pinctrl/qcom/pinctrl-spmi-gpio.c | 1 +
On 2021/01/26 3:08, Casey Schaufler wrote:
> On 1/24/2021 6:36 AM, Sabyrzhan Tasbolatov wrote:
>> syzbot found WARNINGs in several smackfs write operations where
>> bytes count is passed to memdup_user_nul which exceeds
>> GFP MAX_ORDER. Check count size if bigger SMK_LONGLABEL,
>> for smk_write_sy
On Fri, Jan 15, 2021 at 04:39:00PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> BCM4908 uses fixed partitions layout but function of some partitions may
> vary. Some devices use multiple firmware partitions and those should be
> marked to let system discover their purpose.
>
> Signed-of
Don't truncate the iterator to correspond to the actual data size when
fetching the data from the server - rather, pass the length we want to read
to rxrpc.
This will allow the clear-after-read code in future to simply clear the
remaining iterator capacity rather than having to reinitialise the
it
Log unmarshalling errors reported by the peer (ie. it can't parse what we
sent it). Limit the maximum number of messages to 3.
Signed-off-by: David Howells
---
fs/afs/rxrpc.c | 34 ++
1 file changed, 34 insertions(+)
diff --git a/fs/afs/rxrpc.c b/fs/afs/rxrpc
Gather statistics from the netfs interface that can be exported through a
seqfile. This is intended to be called by a later patch when viewing
/proc/fs/fscache/stats.
Signed-off-by: David Howells
---
fs/netfs/Kconfig | 15 +
fs/netfs/Makefile |3 +--
fs/netfs/inter
afs_extract_data() sets up a temporary iov_iter and passes it to AF_RXRPC
each time it is called to describe the remaining buffer to be filled.
Instead:
(1) Put an iterator in the afs_call struct.
(2) Set the iterator for each marshalling stage to load data into the
appropriate places. A
vmxnet3: Remove buf_info from device accessible structures
buf_info structures in RX & TX queues are private driver data that
do not need to be visible to the device. Although there is physical
address and length in the queue descriptor that points to these
structures, their layout is not standar
Use a single ITER_XARRAY iterator to describe the portion of a file to be
transmitted to the server rather than generating a series of small
ITER_BVEC iterators on the fly. This will make it easier to implement AIO
in afs.
In theory we could maybe use one giant ITER_BVEC, but that means
potential
Extract writeback extension into its own function to break up the writeback
function a bit.
Signed-off-by: David Howells
---
fs/afs/write.c | 109 ++--
1 file changed, 67 insertions(+), 42 deletions(-)
diff --git a/fs/afs/write.c b/fs/afs/wr
21.01.2021 01:26, Dmitry Osipenko пишет:
> Extend OPP API with dev_pm_opp_sync_regulators() function, which syncs
> voltage state of regulators.
>
> Tested-by: Peter Geis
> Tested-by: Nicolas Chauvet
> Tested-by: Matt Merhar
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/opp/core.c | 41
> -Original Message-
> From: Valentin Schneider [mailto:valentin.schnei...@arm.com]
> Sent: Tuesday, January 26, 2021 5:46 AM
> To: Song Bao Hua (Barry Song) ;
> linux-kernel@vger.kernel.org
> Cc: mi...@kernel.org; pet...@infradead.org; vincent.guit...@linaro.org;
> dietmar.eggem...@arm.
As a prelude to supporting transparent huge pages, use thp_size() and
similar rather than PAGE_SIZE/SHIFT.
Further, try and frame everything in terms of file positions and lengths
rather than page indices and numbers of pages.
Signed-off-by: David Howells
---
fs/afs/dir.c |2
fs/afs/
On Mon, Jan 25, 2021 at 10:52 AM Stephen Boyd wrote:
>
> Quoting Gwendal Grignou (2021-01-24 13:41:44)
> > On Sun, Jan 24, 2021 at 9:38 AM Jonathan Cameron wrote:
> > >
> > > On Fri, 22 Jan 2021 14:54:43 -0800
> > > Stephen Boyd wrote:
> > >
> > > > ---
> > > > drivers/iio/proximity/Kconfig
On Wed, 6 Jan 2021 10:34:48 +, Andre Przywara wrote:
> a fix to v5, now *really* fixing the wrong priority of SMCCC vs. RNDR
> in arch_get_random_seed_long_early(). Apologies for messing this up
> in v5 and thanks to broonie for being on the watch!
>
> Will, Catalin: it would be much appreciat
On Fri, 15 Jan 2021 16:38:59 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Single partition binding is quite common and may be:
> 1. Used by multiple parsers
> 2. Extended for more specific cases
>
> Move it to separated file to avoid code duplication.
>
> Signed-off-by: Rafał Miłecki
On Thu, 14 Jan 2021 20:32:06 +, Caleb Connolly wrote:
> Document compatible bindings for the new OnePlus 6/6T devices.
>
> Signed-off-by: Caleb Connolly
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml| 5 +
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>
Hi Rob
On 1/25/21 7:22 PM, Rob Herring wrote:
On Wed, Jan 13, 2021 at 09:48:13AM +0530, Anshuman Khandual wrote:
From: Suzuki K Poulose
Document the device tree bindings for Embedded Trace Extensions.
ETE can be connected to legacy coresight components and thus
could optionally contain a conn
> -Original Message-
> From: Jason Gunthorpe [mailto:j...@ziepe.ca]
> Sent: Tuesday, January 26, 2021 4:47 AM
> To: Wangzhou (B)
> Cc: Greg Kroah-Hartman ; Arnd Bergmann
> ; Zhangfei Gao ;
> linux-accelerat...@lists.ozlabs.org; linux-kernel@vger.kernel.org;
> io...@lists.linux-foundation
On Mon, Jan 25, 2021 at 02:03:07PM -0800, Kees Cook wrote:
> On Mon, Jan 25, 2021 at 02:42:10PM -0600, Josh Poimboeuf wrote:
> > When a GCC version mismatch is detected, print a warning and disable the
> > plugin. The only exception is the RANDSTRUCT plugin which needs all
> > code to see the same
On Fri, 15 Jan 2021 14:39:41 +0530, Vinod Koul wrote:
> Add the compatible string for SM8350 SoC from Qualcomm.
>
> Signed-off-by: Vinod Koul
> ---
> .../devicetree/bindings/interrupt-controller/qcom,pdc.txt| 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring
On 1/25/2021 1:55 PM, Borislav Petkov wrote:
On Mon, Jan 25, 2021 at 01:27:51PM -0800, Yu, Yu-cheng wrote:
Maybe I'm missing something but those two can happen outside of the
loop, no? Or is *ptep somehow changing concurrently while the loop is
doing the CMPXCHG and you need to recreate it each
Hi Marcel,
On Mon, Jan 25, 2021 at 7:13 AM Marcel Holtmann wrote:
>
> Hi Miao-chen,
>
> > This moves msft_do_close() from hci_dev_do_close() to
> > hci_unregister_dev() to avoid clearing MSFT extension info. This also
> > avoids retrieving MSFT info upon every msft_do_open() if MSFT extension
> >
On Thu, 14 Jan 2021 19:04:15 +0100, AngeloGioacchino Del Regno wrote:
> Document the new noise rejection properties "qcom,noise-reject-sda"
> and "qcom,noise-reject-scl".
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
> .../devicetree/bindings/i2c/qcom,i2c-qup.yaml | 14
On 25/01/21, Fabio Estevam wrote:
> Hi Oliver,
>
> On Mon, Jan 25, 2021 at 6:29 PM Oliver Graute wrote:
>
> > Ok I fixed the pin conflict with regulator-gpio and added a 5V
> > regulator node in my dts file. Now the display is working fine!
>
> That's good news :-)
>
> > I'll post the dts file
On Thu, Jan 14, 2021 at 07:04:13PM +0100, AngeloGioacchino Del Regno wrote:
> Convert the qcom,i2c-qup binding to YAML schema.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
> .../devicetree/bindings/i2c/qcom,i2c-qup.txt | 40 -
> .../devicetree/bindings/i2c/qcom,i2c-qup.yaml |
On Mon, Jan 25, 2021 at 01:27:51PM -0800, Yu, Yu-cheng wrote:
> > Maybe I'm missing something but those two can happen outside of the
> > loop, no? Or is *ptep somehow changing concurrently while the loop is
> > doing the CMPXCHG and you need to recreate it each time?
> >
> > IOW, you can generate
On 25/01/21 20:53, Sean Christopherson wrote:
Eh, I would argue that it is more common to do KVM_REQ_GET_NESTED_STATE_PAGES
with is_guest_mode() than it is with !is_guest_mode(), as the latter is valid if
and only if eVMCS is in use. But, I think we're only vying for internet
points.:-)
howev
On Sat, Jan 23, 2021 at 6:16 PM Masahiro Yamada wrote:
>
> With commit 1e860048c53e ("gcc-plugins: simplify GCC plugin-dev
> capability test") applied, this check can be way simpler because
> now scripts/gcc-plugins/Kconfig only checks plugin-version.h
>
> Signed-off-by: Masahiro Yamada
> ---
>
>
Avoid accessing directly rtc->ops_lock and use the RTC core helpers.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-ac100.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-ac100.c b/drivers/rtc/rtc-ac100.c
index 1ddbef99e38f..66783cb5e711 100644
---
LOTTO.NL,
2391 Beds 152 Koningin Julianaplein 21,
Den Haag-Netherlands.
(Lotto affiliate with Subscriber Agents).
From: Susan Console
(Lottery Coordinator)
Website: www.lotto.nl
Sir/Madam,
CONGRATULATIONS!!!
We are pleased to inform you of the result of the Lotto NL Winners
International progr
The CFG sub-module is not present on some earlier SoCs like the
DA850/OMAPL-138 in the TI Davinci family. Refactor out the CFG
sub-module parse and initialization logic into a separate function
to make it easier to add logic for the PRUSS IP on the above legacy
SoC families.
Signed-off-by: Suman A
On Tue, Jan 26, 2021 at 06:44:35AM +0900, Masahiro Yamada wrote:
> > > If people use a different compiler, they must be
> > > prepared for any possible problem.
> > >
> > > Using different compiler flags for in-tree and out-of-tree
> > > is even more dangerous.
> > >
> > > For example, CONFIG_GCC_P
On 1/25/21 6:49 PM, Mathieu Poirier wrote:
On Sun, Jan 10, 2021 at 10:48:22PM +, Suzuki K Poulose wrote:
CoreSight ETMv4.4 obsoletes memory mapped access to ETM and
mandates the system instructions for registers.
This also implies that they may not be on the amba bus.
Right now all the CoreS
On Mon, Jan 25, 2021 at 02:42:10PM -0600, Josh Poimboeuf wrote:
> When a GCC version mismatch is detected, print a warning and disable the
> plugin. The only exception is the RANDSTRUCT plugin which needs all
> code to see the same struct layouts. In that case print an error.
I prefer this patch
On 1/24/21 8:32 PM, Randy Dunlap wrote:
> Add qualifying build option legend [CMA] to kernel boot options
> that requirce CMA support to be enabled for them to be usable.
>
> Also capitalize 'CMA' when it is used as an acronym.
>
> Signed-off-by: Randy Dunlap
> Cc: Jonathan Corbet
> Cc: linux-.
On Mon, Jan 25, 2021 at 10:12 PM Jakub Kicinski wrote:
>
> CC Willem just in case
This is an old bug really, tun_napi_alloc_frags() does not make sure
its @len argument is not too big.
Since __skb_grow() does not use __GFP_NOWARN we end up with this well
known warning in mm layer.
I would use
Make AFS use the new fscache read helpers to implement the VM read
operations:
- afs_readpage() now hands off responsibility to fscache_readpage().
- afs_readpages() is gone and replaced with afs_readahead().
- afs_readahead() just hands off responsibility to fscache_readahead().
These make
Use the 'success' and 'aborted' afs_operations_ops methods and add a
'failed' method to handle the completion of an AFS.FetchData,
AFS.FetchData64 or YFS.FetchData64 RPC operation rather than directly
calling the done func pointed to by the afs_read struct from the call
delivery handler.
This mean
From: Dave Wysochanski
In prep for the new fscache netfs API, refactor nfs_readpage()
and nfs_readpages() for future patches. No functional change.
Signed-off-by: Dave Wysochanski
---
fs/nfs/read.c | 45 +++--
1 file changed, 23 insertions(+), 22 del
On 19/01/2021 16.52, Andrew Lunn wrote:
> On Tue, Jan 19, 2021 at 09:32:40AM +0100, Horatiu Vultur wrote:
>> The 01/18/2021 21:27, Vladimir Oltean wrote:
>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
>>> content is safe
>>>
>>> On Mon, Jan 18, 2021 at 09:20:36PM +0
From: Dave Wysochanski
There is a small inconsistency with nfs_readpage() vs nfs_readpages() with
regards to NFSIOS_READPAGES. In readpage we unconditionally increment
NFSIOS_READPAGES at the top, which means even if the read fails. In
readpages, we increment NFSIOS_READPAGES at the bottom base
> -Original Message-
> From: Valentin Schneider [mailto:valentin.schnei...@arm.com]
> Sent: Tuesday, January 26, 2021 1:11 AM
> To: Song Bao Hua (Barry Song) ; Vincent Guittot
> ; Mel Gorman
> Cc: Ingo Molnar ; Peter Zijlstra ;
> Dietmar Eggemann ; Morten Rasmussen
> ; linux-kernel ;
>
On Sat, Jan 23, 2021 at 10:34 PM Masahiro Yamada wrote:
>
> [1] Drop the version information
>
> The range of the supported GCC versions are always changing. The
> current minimal GCC version is 4.9, and commit 1e860048c53e
> ("gcc-plugins: simplify GCC plugin-dev capability test") removed the
> o
From: Dave Wysochanski
Refactor slightly so nfs_readpage_async() calls into
readpage_async_filler().
Signed-off-by: Dave Wysochanski
---
fs/nfs/read.c | 28 +++-
1 file changed, 11 insertions(+), 17 deletions(-)
diff --git a/fs/nfs/read.c b/fs/nfs/read.c
index 5fda3
On Mon, Jan 25, 2021 at 02:52:09PM -0700, Shuah Khan wrote:
> On 1/25/21 1:47 PM, Fenghua Yu wrote:
> > On Mon, Nov 30, 2020 at 08:19:53PM +, Fenghua Yu wrote:
> > > This patch set has several miscellaneous fixes to resctrl selftest tool
> > > that are easily visible to user. V1 had fixes to CA
On Mon, Jan 25, 2021 at 8:07 PM Uwe Kleine-König wrote:
>
> Adding the -@ switch to dtc results in the binary devicetrees containing
> a list of symbolic references and their paths. This is necessary to
> apply device tree overlays e.g. on Raspberry Pi as described on
> https://www.raspberrypi.org
When extracting the mask for a SMR that was programmed by the
bootloader, the SMR's valid bit is also extracted and is treated
as part of the mask, which is not correct. Consider the scenario
where an SMMU master whose context is determined by a bootloader
programmed SMR is removed (omitting parts
On Fri, Jan 22, 2021 at 12:53:17PM +, Robin Murphy wrote:
> On 2021-01-22 12:41, Will Deacon wrote:
> >On Tue, Nov 24, 2020 at 12:15:58PM -0700, Jordan Crouse wrote:
> >>Call report_iommu_fault() to allow upper-level drivers to register their
> >>own fault handlers.
> >>
> >>Signed-off-by: Jord
On 1/25/21 1:47 PM, Fenghua Yu wrote:
Hi, Shuah,
On Mon, Nov 30, 2020 at 08:19:53PM +, Fenghua Yu wrote:
This patch set has several miscellaneous fixes to resctrl selftest tool
that are easily visible to user. V1 had fixes to CAT test and CMT test
but they were dropped in V2 because having
On Sat, Jan 23, 2021 at 08:00:42PM +0800, Chunguang Xu wrote:
> On a multi-disk machine, because jbd2 debugging switch is global, this
> confuses the logs of multiple disks. It is not easy to distinguish the
> logs of each disk and the amount of generated logs is very large. Maybe
> a separate debu
On Mon, Jan 25, 2021 at 09:18:04AM -0800, Shakeel Butt wrote:
> On Mon, Jan 25, 2021 at 8:20 AM Matthew Wilcox wrote:
> >
> > On Thu, Jan 21, 2021 at 02:27:20PM +0200, Mike Rapoport wrote:
> > > From: Mike Rapoport
> > >
> > > Account memory consumed by secretmem to memcg. The accounting is updat
On Thu, 14 Jan 2021 18:50:24 +0100, AngeloGioacchino Del Regno wrote:
> Document the boe,bf060y8m-aj0 panel.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
> .../display/panel/boe,bf060y8m-aj0.yaml | 67 +++
> 1 file changed, 67 insertions(+)
> create mode 100644
On Thu, 14 Jan 2021 18:53:38 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> PMB can be also found on bcm63xx chipsets. It uses difference device
> addresses so a new binding is required.
>
> Signed-off-by: Rafał Miłecki
> ---
> Documentation/devicetree/bindings/power/brcm,bcm-pmb.yaml |
From: Dave Wysochanski
Add nfs_pageio_complete_read() and call this from both nfs_readpage()
and nfs_readpages(), since the submission and accounting is the same
for both functions.
Signed-off-by: Dave Wysochanski
---
fs/nfs/read.c | 137 +
On Thu, Jan 14, 2021 at 11:27:00PM +0800, Muhammad Husaini Zulkifli wrote:
> Keem Bay SOC can support dual voltage operations for GPIO SD pins to
> either 1.8V or 3.3V for bus IO line power. In order to operate the GPIOs
> line for Clk, Cmd and Data on Keem Bay hardware, it is important to
> config
Hi Oliver,
On Mon, Jan 25, 2021 at 6:29 PM Oliver Graute wrote:
> Ok I fixed the pin conflict with regulator-gpio and added a 5V
> regulator node in my dts file. Now the display is working fine!
That's good news :-)
> I'll post the dts files soon and check if there is something to
> improve fo
On Tue, Jan 26, 2021 at 6:28 AM Josh Poimboeuf wrote:
>
> On Tue, Jan 26, 2021 at 06:16:01AM +0900, Masahiro Yamada wrote:
> > On Tue, Jan 26, 2021 at 5:42 AM Josh Poimboeuf wrote:
> > >
> > > When building out-of-tree kernel modules, the build system doesn't
> > > require the GCC version to matc
Quoting Mike Rapoport (2021-01-25 21:33:48)
> On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson
> > wrote:
> > >
> > > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > > Mike Rapoport (3):
> > > ...
> > > > mm: fix initializa
For IPv4, default route is learned via DHCPv4 and user is allowed to change
metric using config etc/network/interfaces. But for IPv6, default route can
be learned via RA, for which, currently a fixed metric value 1024 is used.
Ideally, user should be able to configure metric on default route for I
From: Dave Wysochanski
The conversion of the NFS read paths to the new fscache API
will require use of a few read structs and functions,
so move these declarations as required.
Signed-off-by: Dave Wysochanski
---
fs/nfs/internal.h |8
fs/nfs/read.c | 13 -
2 fil
From: Dave Wysochanski
This patch converts the main NFS read paths to the new netfs API,
when fscache is enabled, and converts readpage while minimizing
changes to the existing NFS read code paths.
The netfs API requires a few functions to be provided by the
netfs:
- init_rreq: allows netfs to a
From: Dave Wysochanski
The new FS-Cache API does not have a readpages equivalent function,
and instead of fscache_read_or_alloc_pages() it implements a readahead
function, netfs_readahead(). Call netfs_readahead() if fscache is
enabled, and if not, utilize readahead_page() to run through the
pag
On Thu, Jan 14, 2021 at 06:13:13PM +0100, Amelie Delaunay wrote:
> usbphyc provides a unique clock called ck_usbo_48m.
> STM32 USB OTG needs a 48Mhz clock (utmifs_clk48) for Full-Speed operation.
> ck_usbo_48m is a possible parent clock for USB OTG 48Mhz clock.
>
> ck_usbo_48m is available as soon
On Mon, Jan 25, 2021 at 05:54:51PM +0100, Michal Hocko wrote:
> On Thu 21-01-21 14:27:20, Mike Rapoport wrote:
> > From: Mike Rapoport
> >
> > Account memory consumed by secretmem to memcg. The accounting is updated
> > when the memory is actually allocated and freed.
>
> What does this mean?
T
401 - 500 of 1134 matches
Mail list logo