Here's a set of patches that massively overhauls the object lifecycle
management and the I/O API of the local caching for network filesystems code
for a reduction of about 3000 LoC and a 1000 line Documentation reduction.
The ability to use async DIO to pass data to/from the cache gives a huge
Temporarily disable the fscache side of fscache_invalidate() so that the
operation managing code can be removed.
Signed-off-by: David Howells
---
fs/cachefiles/interface.c |9 ++---
fs/fscache/cookie.c |4 +-
fs/fscache/object.c | 78
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
Provide a macro, lru_to_last_page(), to find the last page in a page list
(the opposite of lru_to_page()).
Signed-off-by: David Howells
---
include/linux/mm.h |1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/mm.h b/include/linux/mm.h
index dc7b87310c10..9692b9b58b06 100644
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
Add an iterator, ITER_MAPPING, that walks through a set of pages attached
to an address_space, starting at a given page and offset and walking for
the specified amount of bytes.
The caller must guarantee that the pages are all present and they must be
locked using PG_locked, PG_writeback or
Provide an S_CACHE_FILE inode flag that cachefiles can set to ward off
other kernel services and drivers (including itself) from using its cache
files.
Signed-off-by: David Howells
---
include/linux/fs.h |1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/fs.h
Provide a simple thread pool that can be used to run cookie management
operations in the background and a dispatcher infrastructure to punt
operations to the pool if threads are available or to just run the
operation in the calling thread if not.
A future patch will replace all the object state
Remove the tree of active dentries from the cachefiles_cache struct and
instead set a flag, S_CACHE_FILE, on the backing inode to indicate that
this file is in use by the kernel so as to ward off other kernel users.
This simplifies the code a lot and also prevents two overlain caches from
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
Rewrite the fscache I/O API by introducing a number of new routines based
on a number of principles:
(1) The cache provides *only* write-to-cache and read-from-cache calls for
transferring data to/from the cache.
(2) The bufferage for I/O to/from the cache is supplied with an iov_iter.
On Mon, Jul 13, 2020 at 03:50:18PM +0200, Alexander A. Klimov wrote:
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Deterministic algorithm:
> For each file:
> If not .svg:
> For each line:
> If
Hi Vasily,
>> maybe just the read sync train params command is broken? Can you change the
>> init code and not send it and see if the rest of the init phase proceeds. I
>> would rather have the secure connections actually tested before dismissing
>> it altogether.
>
> I don't think that I
Remove fscache_wait_on_invalidate() as the invalidation wait is now built into
the I/O path.
Signed-off-by: David Howells
---
fs/fscache/cookie.c | 14 --
include/linux/fscache.h | 17 -
2 files changed, 31 deletions(-)
diff --git a/fs/fscache/cookie.c
* Lee Jones [200713 14:50]:
> Add some missing attributes/parameter descriptions, remove other
> superfluous ones, add struct header titles and fix misspellings.
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/pinctrl/pinctrl-single.c:50: warning: Function parameter or member
Replace the object management state machine with something a lot simpler.
The entire process of setting up or tearing down a cookie is done in one
go, and the dispatcher either punts it to a worker thread, or if all the
worker threads are all busy, does it in the current thread.
Keep track of the size of a file that we're caching as last set
independently on the server by another client. As long as this does not
change, we can make the assumption that anything over that boundary, if not
represented in the local cache, will not be represented on the server
either and can
Recast assertion in terms of cookie not being an index rather than being a
datafile.
Signed-off-by: David Howells
---
fs/fscache/cookie.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/fscache/cookie.c b/fs/fscache/cookie.c
index 5c53027d3f53..2d9d147411cd 100644
---
Fix variable unused warnings due to disabled histogram stuff.
Signed-off-by: David Howells
---
fs/cachefiles/internal.h |7 +--
fs/fscache/internal.h|6 --
2 files changed, 9 insertions(+), 4 deletions(-)
diff --git a/fs/cachefiles/internal.h b/fs/cachefiles/internal.h
Implement the new fscache I/O backend API in cachefiles. The
cachefiles_object struct carries a non-accounted file to the cachefiles
object (so that it doesn't cause ENFILE).
Signed-off-by: David Howells
---
fs/cachefiles/Makefile|1 +
fs/cachefiles/interface.c |3 ++
Split cachefiles_drop_object() up a bit to make it easier to modify later.
Signed-off-by: David Howells
---
fs/cachefiles/interface.c | 58 ++---
1 file changed, 39 insertions(+), 19 deletions(-)
diff --git a/fs/cachefiles/interface.c
Remove some redundant checks for unsigned values being >= 0.
Signed-off-by: David Howells
---
fs/cachefiles/bind.c |6 ++
fs/cachefiles/daemon.c |6 +++---
2 files changed, 5 insertions(+), 7 deletions(-)
diff --git a/fs/cachefiles/bind.c b/fs/cachefiles/bind.c
index
On Thu, Jul 09, 2020 at 11:35:23PM +0200, Michael Walle wrote:
> The constants are taken from the USXGMII Singleport Copper Interface
> specification. The naming are based on the SGMII ones, but with an MDIO_
> prefix.
>
> Signed-off-by: Michael Walle
> ---
Somebody would need to review this
On Thu, Jul 09, 2020 at 11:35:24PM +0200, Michael Walle wrote:
> Now that there are USXGMII constants available, drop the old definitions
> and reuse the generic ones.
>
> Signed-off-by: Michael Walle
> ---
I did regression-testing of this on an LS1028A-QDS with SerDes protocol
0x13bb.
Merge the object->backer pointer into the object->dentry pointer and assume
that data objects are always going to be just regular files.
object->dentry can then more easily be overridden later by invalidation
without having two different things to update the xattrs on.
object->old maintains a
Add a cachefiles tracepoint that logs the result of coherency management
when the coherency data on a file in the cache is checked or committed.
Signed-off-by: David Howells
---
fs/cachefiles/xattr.c | 45 ++
include/trace/events/cachefiles.h | 56
Implement a content indicator that indicates the presence or absence of
content and a bitmap that indicates which blocks of granular content are
present in a granular file. This is added to the xattr that stores the
netfs coherency data, along with the file size and the file zero point (the
point
Round the size of a cachefile up to DIO block size so that we can always
read back the last partial page of a file using direct I/O.
Signed-off-by: David Howells
---
fs/cachefiles/interface.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/fs/cachefiles/interface.c
Implement the function that shapes extents to map onto the granules in a
cache file.
When setting to fetch data from the server to be cached, the extent will be
expanded to align with granule size and cut down so that it doesn't cross
the boundary between a non-present extent and a present
---
fs/cachefiles/interface.c | 16 +++--
fs/cachefiles/io.c|2 +
include/trace/events/cachefiles.h | 123 +
3 files changed, 136 insertions(+), 5 deletions(-)
diff --git a/fs/cachefiles/interface.c b/fs/cachefiles/interface.c
Implement writing into the cache and reading back from the cache inside
cachefiles using asynchronous direct I/O from the specified iterator. The
size and position of the request should be aligned to the reported
dio_block_size.
Errors and completion are reported by callback.
Signed-off-by:
Rewrite the cache object invalidation code in fscache and cachefiles. The
following changes are made to fscache:
(1) Invalidation is now ignored or allowed to proceed depending on the
'stage' a non-index cookie is in with respect to the backing object.
(2) If invalidation is proceeds, it
Add a trio of helper functions:
fscache_read_helper_page_list();
fscache_read_helper_locked_page();
fscache_read_helper_for_write();
to do the work of shaping read requests, attempting to read from the cache,
issuing or reissuing requests to the filesystem to pass to the
Create some new stat counters appropriate to the new routines and display
them in /proc/fs/fscache/stats.
Signed-off-by: David Howells
---
fs/fscache/dispatcher.c |6
fs/fscache/internal.h| 25 +
fs/fscache/io.c |2 +
fs/fscache/read_helper.c | 38
Hi Joseph,
> This patch adds the Realtek 8822CE controller to the usb_device_id
> table to support the wideband speech capability.
>
> Reviewed-by: ala...@chromium.org
> Signed-off-by: Joseph Hwang
> ---
>
> Changes in v2:
> - Fixed the commit subject and message body.
>
>
Allow the cache to add information in /proc/fs/fscache/objects instead of
displaying cookie key and aux data - which can be seen in the cookies file.
Signed-off-by: David Howells
---
fs/cachefiles/content-map.c | 41 +
fs/cachefiles/interface.c |
For the Qualcomm TrustZone firmwares which I am familiar with:
Reviewed-by: Elliot Berman
On 7/4/2020 10:23 AM, Jonathan McDowell wrote:
> The move to a combined driver for the QCOM SCM hardware changed the
> io_writel and io_readl helpers to use non-atomic calls, despite the
> commit message
Remove some more stats that have become obsolete.
Signed-off-by: David Howells
---
fs/fscache/internal.h | 18 ++
fs/fscache/obj.c |6 +++---
fs/fscache/stats.c| 50 +
3 files changed, 14 insertions(+), 60
Implement the "will_modify" parameter passed to fscache_use_cookie().
Setting this to true will henceforth cause the affected object to be marked
as dirty on disk, subject to conflict resolution in the event that power
failure or a crash occurs or the filesystem operates in disconnected mode.
On Mon, Jul 13, 2020 at 9:13 AM Greg Kroah-Hartman
wrote:
>
> On Mon, Jul 13, 2020 at 09:09:18AM -0700, Dan Williams wrote:
> > On Mon, Jul 13, 2020 at 8:52 AM Greg Kroah-Hartman
> > wrote:
> > >
> > > On Mon, Jul 13, 2020 at 08:39:43AM -0700, Dan Williams wrote:
> > > > On Sun, Jul 12, 2020 at
Provide a cache operation to resize an object. This is intended to be run
synchronously rather than being deferred as it really needs to run inside
the inode lock on the netfs inode from ->setattr() to correctly order with
respect to other truncates and writes.
Signed-off-by: David Howells
---
The afs filesystem driver allows unstarted operations to be cancelled by
signal, but most of these can easily be restarted (mkdir for example). The
primary culprits for reproducing this are those applications that use
SIGALRM to display a progress counter.
File lock-extension operation is marked
Remove the cache-side of the object update operation as it doesn't
serialise with other setattr, O_TRUNC and write operations.
Signed-off-by: David Howells
---
fs/cachefiles/interface.c | 59 -
fs/fscache/internal.h |1 -
On 7/12/20 9:27 AM, Dan Williams wrote:
The 'struct resource' in 'struct dev_pagemap' is only used for holding
resource span information. The other fields, 'name', 'flags', 'desc',
'parent', 'sibling', and 'child' are all unused wasted space.
This is in preparation for introducing a
In cachefiles_shape_extent(), shape a write request to always write to the
cache. The assumption is made that the caller has read the entire cache
granule beforehand if necessary.
Possibly this should be amended so that writes will only take place to
granules that are marked present and granules
Here's a set of patches that makes AFS use the fscache rewrite.
These patches can be found as part of the branch here:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-iter
David
---
David Howells (1):
afs: Add O_DIRECT read support
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
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
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
Excerpts from Andy Lutomirski's message of July 14, 2020 1:48 am:
> On Mon, Jul 13, 2020 at 7:13 AM Mathieu Desnoyers
> wrote:
>>
>> - On Jul 13, 2020, at 9:47 AM, Nicholas Piggin npig...@gmail.com wrote:
>>
>> > Excerpts from Nicholas Piggin's message of July 13, 2020 2:45 pm:
>> >> Excerpts
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
On Thu, Jul 09, 2020 at 11:35:25PM +0200, Michael Walle wrote:
> ENETC has ethernet MACs capable of SGMII, 2500BaseX and USXGMII. But in
> order to use these protocols some SerDes configurations need to be
> performed. The SerDes is configurable via an internal PCS PHY which is
> connected to an
On 13/07/2020 04:25, Viresh Kumar wrote:
> On 12-07-20, 11:06, Jon Hunter wrote:
>> Commit 6cc3d0e9a097 ("cpufreq: tegra186: add
>> CPUFREQ_NEED_INITIAL_FREQ_CHECK flag") fixed CPUFREQ support for
>> Tegra186 but as a consequence the following warnings are now seen on
>> boot ...
>>
>> cpufreq:
Note the amount of data transferred in the fscache request op structure in
the delivery/decode routines for the various FetchData operations.
Also, we need to exclude the excess from this value and then we need to use
this in directory read rather than actual_len.
Signed-off-by: David Howells
Embed an fscache_io_request struct into struct afs_read and remove some of
the redundant members from the latter.
Change all references to those removed members to use the fscache ones
instead.
Signed-off-by: David Howells
---
fs/afs/dir.c | 38 --
Hi Venkata,
> 1.During SSR for command time out if BT SoC goes to inresponsive
> state, power cycling of BT SoC was not happening.Given the fix by
> sending hw error event to reset the BT SoC.
>
> 2.If SSR is triggered then ignore the transmit data requests to
> BT SoC until SSR is completed.
>
Use a single ITER_MAPPING 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
PG_fscache is going to be used to indicate that a page is being written to
the cache, and that the page should not be modified or released until it's
finished.
Make afs_invalidatepage() and afs_releasepage() wait for it.
Signed-off-by: David Howells
---
fs/afs/file.c |7 +++
Make AFS use the new fscache I/O API to read and write from the cache.
afs_readpage() now calls fscache_read_helper() once to try and create a
block around the page to be read.
afs_readpages() now calls fscache_read_helper() multiple times until its
list is exhausted or an error occurs.
Add synchronous O_DIRECT read support to AFS (no AIO yet). It can
theoretically handle reads up to the maximum size describable by loff_t -
and given an iterator with sufficiently capacity to handle that and given
support on the server.
Signed-off-by: David Howells
---
fs/afs/file.c |
On Thu, Jul 09, 2020 at 11:35:26PM +0200, Michael Walle wrote:
> From: Alex Marginean
>
> Use DT information rather than in-band information from bootloader to
> set up MAC for XGMII. For RGMII use the DT indication in addition to
> RGMII defaults in hardware.
> However, this implies that PHY
When writing to the server from afs_writepage() or afs_writepages(), copy
the data to the cache object too.
Signed-off-by: David Howells
---
fs/afs/write.c | 132 ++--
1 file changed, 128 insertions(+), 4 deletions(-)
diff --git
Invoke fscache_resize_cookie() to adjust the size of the backing cache
object when setattr is called with ATTR_SIZE. This discards any data that
then lies beyond the revised EOF and frees up space.
Signed-off-by: David Howells
---
fs/afs/inode.c | 24 +++-
1 file
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
On Tue, Jul 07, 2020 at 03:16:29PM -0400, Waiman Long wrote:
> Depending on the workloads, the following circular locking dependency
> warning between sb_internal (a percpu rwsem) and fs_reclaim (a pseudo
> lock) may show up:
>
> ==
> WARNING:
On Mon, Jul 13, 2020 at 07:36:46PM +0530, Sumit Gupta wrote:
> To do frequency scaling on all CPUs within T194 CPU Complex, we need
> to query BPMP for data on valid operating points. Document a compatible
> string under 'cpus' node to represent the CPU Complex for binding drivers
> like cpufreq
Hi Vasily and Heiko,
We were very excited to see your patches going by for enabling Clang
support for s390. Since then, we've added s390 builds to our
continuous integration setup.
We've been running into a few issues with doing virtualized boot tests
of our kernels on s390.
I was curious if
Hi Peilin,
> Check `num_rsp` before using it as for-loop counter.
>
> Cc: sta...@vger.kernel.org
> Signed-off-by: Peilin Ye
> ---
> net/bluetooth/hci_event.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
On Mon, Jul 13, 2020 at 05:15:39PM +0100, Chris Down wrote:
> +#define SHMEM_INO_BATCH 1024U
...
> + if (unlikely((ino & ~SHMEM_INO_BATCH) == 0)) {
I don't think that works. I think you meant to write ~(SHMEM_INO_BATCH - 1).
Or just ino % SHMEM_INO_BATCH which works even for
On Mon, Jul 13, 2020 at 04:50:03PM +0200, Pali Rohár wrote:
> On Monday 13 July 2020 12:23:25 Lorenzo Pieralisi wrote:
> > I will go over the thread again but I suspect I can merge the patch even
> > though I still believe there is work to be done to understand the issue
> > we are facing.
>
>
Hi Peilin,
> Check `num_rsp` before using it as for-loop counter. Add `unlock` label.
>
> Cc: sta...@vger.kernel.org
> Signed-off-by: Peilin Ye
> ---
> net/bluetooth/hci_event.c | 7 +++
> 1 file changed, 7 insertions(+)
patch has been applied to bluetooth-next tree.
Regards
Marcel
Hi,
On 7/13/2020 6:22 AM, Saheed O. Bolarinwa wrote:
> In reference to the PCI spec (Chapter 2), PCIBIOS* is an x86 concept.
> Their scope should be limited within arch/x86.
>
> Change all PCIBIOS_SUCCESSFUL to 0
>
> Signed-off-by: "Saheed O. Bolarinwa"
> ---
> drivers/nvme/host/pci.c | 2 +-
>
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
* dillon.min...@gmail.com [200621 15:36]:
> From: dillon min
>
> Since am437x have the same clock structure with am335x [1][2],
> reuse the code from Tony Lindgren's patch [3] to fix dcan probe
> failed on am437x platform.
>
> [1]: https://www.ti.com/lit/pdf/spruh73 Chapter-23, Figure 23-1.
Matthew Wilcox writes:
I don't think that works. I think you meant to write ~(SHMEM_INO_BATCH - 1).
Or just ino % SHMEM_INO_BATCH which works even for non-power-of-two.
Er, right. I now wonder why I didn't just write `ino % SHMEM_INO_BATCH` :-)
I'll send again with that fix.
On Tue, Jun 30, 2020 at 03:55:31PM +0800, Rahul Tanwar wrote:
> Intel's LGM(Lightning Mountain) SoC contains a PWM fan controller
> which is only used to control the fan attached to the system. This
> PWM controller does not have any other consumer other than fan.
> Add DT bindings documentation
* Paul Walmsley [200619 15:20]:
> On Fri, 19 Jun 2020, Chen Tao wrote:
>
> > Fix memory leak in omap_hwmod_allocate_module not freeing in
> > handling error path.
> >
> > Fixes: 8c87970543b17("ARM: OMAP2+: Add functions to allocate module data
> > from device tree")
> > Signed-off-by: Chen Tao
Excerpts from Andy Lutomirski's message of July 14, 2020 1:59 am:
> On Thu, Jul 9, 2020 at 6:57 PM Nicholas Piggin wrote:
>>
>> On big systems, the mm refcount can become highly contented when doing
>> a lot of context switching with threaded applications (particularly
>> switching between the
The IMA_APPRAISE_BOOTPARAM config allows enabling different "ima_appraise="
modes - log, fix, enforce - at run time, but not when IMA architecture
specific policies are enabled. This prevents properly labeling the
filesystem on systems where secure boot is supported, but not enabled on the
Excerpts from Pratik Sampat's message of July 13, 2020 8:02 pm:
> Thank you for your comments,
>
> On 13/07/20 10:53 am, Nicholas Piggin wrote:
>> Excerpts from Pratik Rajesh Sampat's message of July 10, 2020 3:22 pm:
>>> Changelog v1 --> v2:
>>> 1. Save-restore DAWR and DAWRX unconditionally as
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
On Mon, Jul 13, 2020 at 9:36 AM Ralph Campbell wrote:
>
>
> On 7/12/20 9:27 AM, Dan Williams wrote:
> > The 'struct resource' in 'struct dev_pagemap' is only used for holding
> > resource span information. The other fields, 'name', 'flags', 'desc',
> > 'parent', 'sibling', and 'child' are all
From: Bolarinwa Olayemi Saheed
On failure pcie_capability_read_dword() sets it's last parameter, val
to 0. However, with Patch 14/14, it is possible that val is set to ~0 on
failure. This would introduce a bug because (x & x) == (~0 & x).
This bug can be avoided without changing the function's
From: Bolarinwa Olayemi Saheed
On failure pcie_capability_read_dword() sets it's last parameter,
val to 0. In this case dn and up will be 0, so aspm_hw_l1_supported()
will return false.
However, with Patch 14/14, it is possible that val is set to ~0 on
failure. This would introduce a bug because
From: Bolarinwa Olayemi Saheed
On failure pcie_capability_read_dword() sets it's last parameter,
val to 0.
However, with Patch 14/14, it is possible that val is set to ~0 on
failure. This would introduce a bug because (x & x) == (~0 & x).
This bug can be avoided if the return value of
From: Bolarinwa Olayemi Saheed
On failure pcie_capability_read_dword() sets it's last parameter,
val to 0.
However, with Patch 14/14, it is possible that val is set to ~0 on
failure. This would introduce a bug because (x & x) == (~0 & x).
This bug can be avoided if the return value of
On Mon, Jul 13, 2020 at 03:27:55PM +0100, Qais Yousef wrote:
> On 07/13/20 15:35, Peter Zijlstra wrote:
> > > I protect this with rcu_read_lock() which as far as I know
> > > synchronize_rcu()
> > > will ensure if we do the update during this section; we'll wait for it to
> > > finish. New
From: Bolarinwa Olayemi Saheed
On failure pcie_capability_read_dword() sets it's last parameter, val
to 0. However, with Patch 14/14, it is possible that val is set to ~0 on
failure. This would introduce a bug because (x & x) == (~0 & x).
This bug can be avoided without changing the function's
On Mon, Jul 13, 2020 at 05:27:53PM +0100, John Garry wrote:
> On 12/07/2020 14:26, Jiri Olsa wrote:
> > +int expr__add_ref(struct expr_parse_ctx *ctx, struct metric_ref *ref)
> > +{
> > + struct expr_id_data *data_ptr = NULL, *old_data = NULL;
> > + char *old_key = NULL;
> > + char *name;
>
On Mon, Jul 13, 2020 at 08:41:31PM +0800, Zhenyu Ye wrote:
> On 2020/7/13 20:21, Catalin Marinas wrote:
> > On Fri, Jul 10, 2020 at 08:11:19PM +0100, Catalin Marinas wrote:
> >> On Fri, 10 Jul 2020 17:44:18 +0800, Zhenyu Ye wrote:
> >>> NOTICE: this series are based on the arm64 for-next/tlbi
Excerpts from Gautham R Shenoy's message of July 13, 2020 8:48 pm:
> On Mon, Jul 13, 2020 at 03:23:21PM +1000, Nicholas Piggin wrote:
>> Excerpts from Pratik Rajesh Sampat's message of July 10, 2020 3:22 pm:
>> > Changelog v1 --> v2:
>> > 1. Save-restore DAWR and DAWRX unconditionally as they are
On 7/13/20 11:05 AM, Daniel Lezcano wrote:
On 10/07/2020 15:51, Thara Gopinath wrote:
Extend thermal trip point type property to include "cold" trip type
indicating point in the temperature domain below which a warming action
must be intiated.
Signed-off-by: Thara Gopinath
---
On Mon, Jul 13, 2020 at 07:34:16PM +0300, Vladimir Oltean wrote:
> On Thu, Jul 09, 2020 at 11:35:23PM +0200, Michael Walle wrote:
> > The constants are taken from the USXGMII Singleport Copper Interface
> > specification. The naming are based on the SGMII ones, but with an MDIO_
> > prefix.
> >
>
On Wed, Jul 01, 2020 at 03:25:19PM +0200, Benjamin Gaignard wrote:
> Add schemas for firewall consumer and provider.
>
> Signed-off-by: Benjamin Gaignard
> Reviewed-by: Linus Walleij
> ---
> .../bindings/bus/stm32/firewall-consumer.yaml | 36
> ++
>
On Mon, Jul 13, 2020 at 04:11:23PM +0100, Will Deacon wrote:
> On Thu, Jun 11, 2020 at 04:36:56PM -0600, Jordan Crouse wrote:
> > Add a new implementation hook to allow the implementation specific code
> > to tweek the context bank configuration just before it gets written.
> > The first user will
On 13/07/2020 19:01, Thara Gopinath wrote:
>
>
> On 7/13/20 11:05 AM, Daniel Lezcano wrote:
>> On 10/07/2020 15:51, Thara Gopinath wrote:
>>> Extend thermal trip point type property to include "cold" trip type
>>> indicating point in the temperature domain below which a warming action
>>> must
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
On Wed, Jul 01, 2020 at 03:25:21PM +0200, Benjamin Gaignard wrote:
> Document STM32 ETZPC firewall controller bindings
>
> Signed-off-by: Benjamin Gaignard
> ---
> .../bindings/bus/stm32/st,stm32-etzpc.yaml | 46
> ++
> 1 file changed, 46 insertions(+)
> create
Am 2020-07-13 19:01, schrieb Andrew Lunn:
On Mon, Jul 13, 2020 at 07:34:16PM +0300, Vladimir Oltean wrote:
On Thu, Jul 09, 2020 at 11:35:23PM +0200, Michael Walle wrote:
> The constants are taken from the USXGMII Singleport Copper Interface
> specification. The naming are based on the SGMII
This is just an atomic version of mode_valid, which is intended to be
used for situations where a driver might need to check the atomic state
of objects other than the connector itself. One such example is with
MST, where the maximum possible bandwidth on a connector can change
dynamically
701 - 800 of 1509 matches
Mail list logo
