[CC: Dave Chinner, Jan Kara, xfs]
On Sat, Jun 20, 2020 at 10:15 PM Matthew Wilcox wrote:
>
> On Sat, Jun 20, 2020 at 09:19:37AM +0300, Amir Goldstein wrote:
> > On Fri, Jun 19, 2020 at 6:52 PM Matthew Wilcox wrote:
> > > This patch lifts the IOCB_CACHED idea expressed by Andreas to the VFS.
> >
On Mon 15 Jun 23:13 PDT 2020, John Stultz wrote:
> Tweaks to allow pinctrl-msm code to be loadable as a module.
> This is needed in order to support having the qcom-scm driver,
> which pinctrl-msm calls into, configured as a module.
>
This means that we need a "depends on QCOM_SCM ||
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 8b6ddd10d678bebec32381f71b6b420bafc43ad0
commit: d3c7b35c20d60650bac8b55c17b194adda03a979 dm: add emulated block size
target
date: 5 weeks ago
config: openrisc-randconfig-r035-20200621 (attached
On Sat 20 Jun 07:46 PDT 2020, Konrad Dybcio wrote:
> s3 was mislabeled as s2. Fix it.
>
> Signed-off-by: Konrad Dybcio
Reviewed-by: Bjorn Andersson
Regards,
Bjorn
> ---
> drivers/regulator/qcom_smd-regulator.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
Hi Adam.
On Mon, Jun 15, 2020 at 09:53:45AM -0500, Adam Ford wrote:
> On Mon, Jun 15, 2020 at 9:46 AM Fabio Estevam wrote:
> >
> > On Mon, Jun 15, 2020 at 10:19 AM Adam Ford wrote:
> > >
> > > The LogicPD Type28 display used by several Logic PD products has not
> > > worked since v5.5.
> >
> >
Hi all,
After merging the tip tree, today's linux-next build (perf) failed
like this:
In file included from trace/beauty/tracepoints/x86_msr.c:10:
perf/trace/beauty/generated/x86_arch_MSRs_array.c:292:45: error: initialized
field overwritten [-Werror=override-init]
292 | [0xc0010280 -
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
branch HEAD: d3779e78b9848a707448dbb4a0cb6c4bb651fe9c kcsan: Disable branch
tracing in core runtime
elapsed time: 725m
configs tested: 116
configs skipped: 8
The following configs have been built
Hi Matthias
On Fri, Jun 12, 2020 at 09:22:15AM +0200, Matthias Schiffer wrote:
> From: Matthias Schiffer
>
> This adds a few panels TQ-Systems uses with various starterkit
> mainboards. Device trees actually using these panels will be added with
> a later submission.
>
>
> Matthias Schiffer
ze
> target
> date: 5 weeks ago
> config: openrisc-randconfig-r035-20200621 (attached as .config)
> compiler: or1k-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget
> https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
> ~/bin
Happy to meet you congratulations respond for the details of the good news
On Sat, Jun 20, 2020 at 09:41:28AM +0300, Denis Efremov wrote:
>
>
> On 6/19/20 7:17 PM, kernel test robot wrote:
> > Hi Denis,
> >
> > First bad commit (maybe != root cause):
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > master
> > head:
On Sat, 20 Jun 2020 at 13:53, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.48 release.
> There are 259 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.
>
>
On Wed 17 Jun 11:02 PDT 2020, Wesley Cheng wrote:
> Some Qualcomm PMICs have the capability to source the VBUS output to
> connected peripherals. This driver will register a regulator to the
> regulator list to enable or disable this source by an external driver.
>
> Signed-off-by: Wesley Cheng
On Wed 17 Jun 11:02 PDT 2020, Wesley Cheng wrote:
> Add the required DTS node for the USB VBUS output regulator, which is
> available on PM8150B. This will provide the VBUS source to connected
> peripherals.
>
> Signed-off-by: Wesley Cheng
> ---
> arch/arm64/boot/dts/qcom/pm8150b.dtsi | 6
On Wed 17 Jun 11:02 PDT 2020, Wesley Cheng wrote:
> The PM8150B has a dedicated USB type C block, which can be used for type C
> orientation and role detection. Create the reference node to this type C
> block for further use.
>
> Signed-off-by: Wesley Cheng
> ---
>
On Sat, 20 Jun 2020 at 13:53, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.129 release.
> There are 265 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.
>
>
On Wed, Jun 17, 2020 at 03:23:00PM -0300, Jason Gunthorpe wrote:
> On Wed, Jun 17, 2020 at 08:17:39AM +0300, Leon Romanovsky wrote:
> >
> > My thoughts that everything here hints me that state machine and
> > locking are implemented wrongly. In ideal world, the expectation
> > is that REQ message
On Mon 08 Jun 23:44 PDT 2020, Amit Kucheria wrote:
> sm8250 has 24 thermal sensors split across two tsens controllers. Add
> the thermal zones to expose them and wireup the cpus to throttle on
> crossing passive temperature thresholds.
>
> Update the comment in the drivers to list the SoCs it
On 19-06-20, 16:31, Dave Jiang wrote:
>
>
> On 6/19/2020 3:47 PM, Federico Vaga wrote:
> > Hello,
> >
> > is there the possibility of using a DMA engine channel from userspace?
> >
> > Something like:
> > - configure DMA using ioctl() (or whatever configuration mechanism)
> > - read() or
On Tue 09 Jun 06:30 PDT 2020, Sai Prakash Ranjan wrote:
> Define iommus property for Coresight ETR component in
> SC7180 SoC with the SID and mask to enable SMMU
> translation for this master.
>
We don't have _smmu in linux-next, as we've yet to figure out how
to disable the boot splash or
On Tue 16 Jun 23:56 PDT 2020, Sai Prakash Ranjan wrote:
> Hi Bjorn,
>
Hi Sai,
> On 2020-02-12 03:54, Sai Prakash Ranjan wrote:
> > This series converts QCOM watchdog timer bindings to YAML. Also
> > it adds the missing SoC-specific compatible for QCS404, SC7180,
> > SDM845 and SM8150 SoCs.
> >
percpu_counter_sum_positive() will provide more accurate info.
As with percpu_counter_read_positive(), in worst case the deviation
could be 'batch * nr_cpus', which is totalram_pages/256 for now,
and will be more when the batch gets enlarged.
Its time cost is about 800 nanoseconds on a 2C/4T
When checking a performance change for will-it-scale scalability
mmap test [1], we found very high lock contention for spinlock of
percpu counter 'vm_committed_as':
94.14% 0.35% [kernel.kallsyms] [k] _raw_spin_lock_irqsave
48.21%
When checking a performance change for will-it-scale scalability mmap test
[1], we found very high lock contention for spinlock of percpu counter
'vm_committed_as':
94.14% 0.35% [kernel.kallsyms] [k] _raw_spin_lock_irqsave
48.21%
Use the existing vm_memory_committed() instead, which is also
convenient for future change.
Signed-off-by: Feng Tang
Acked-by: Michal Hocko
Cc: Matthew Wilcox (Oracle)
Cc: Johannes Weiner
Cc: Mel Gorman
Cc: Kees Cook
Cc: Andi Kleen
Cc: Tim Chen
Cc: Dave Hansen
Cc: Huang Ying
---
>
> On Wed, Apr 8, 2020 at 3:00 PM Asutosh Das
> wrote:
> >
> > The write performance of TLC NAND is considerably
> > lower than SLC NAND. Using SLC NAND as a WriteBooster
> > Buffer enables the write request to be processed with
> > lower latency and improves the overall write performance.
>
On Tue 16 Jun 23:56 PDT 2020, Naresh Kamboju wrote:
> This patch adds linux/slab.h to fix build error in qcom_q6v5_mss.c
>
> Build error:
> ../drivers/remoteproc/qcom_q6v5_mss.c:
> In function ‘q6v5_mpss_init_image’:
> ../drivers/remoteproc/qcom_q6v5_mss.c:772:3:
> error: implicit
On Sun 21 Jun 00:40 PDT 2020, Avri Altman wrote:
>
> >
> > On Wed, Apr 8, 2020 at 3:00 PM Asutosh Das
> > wrote:
> > >
> > > The write performance of TLC NAND is considerably
> > > lower than SLC NAND. Using SLC NAND as a WriteBooster
> > > Buffer enables the write request to be processed
From: Yangtao Li
After commit 333cff6c963fbc ("powercap/drivers/idle_inject: Specify
idle state max latency"), we convert to use play_idle_precise() with
max allowed latency to specify the idle state.
Some function comments still use play_idle(), let's update it to
play_idle_precise().
Hi Bjorn,
On 2020-06-21 12:52, Bjorn Andersson wrote:
On Tue 09 Jun 06:30 PDT 2020, Sai Prakash Ranjan wrote:
Define iommus property for Coresight ETR component in
SC7180 SoC with the SID and mask to enable SMMU
translation for this master.
We don't have _smmu in linux-next, as we've yet
Hi Xin.
On Tue, Jun 09, 2020 at 03:19:50PM +0800, Xin Ji wrote:
> The ANX7625 is an ultra-low power 4K Mobile HD Transmitter designed
> for portable device. It converts MIPI DSI/DPI to DisplayPort 1.3 4K.
>
> Signed-off-by: Xin Ji
The bridge driver now implements the bridge functions for
'topology_sysfs_init()' is only called via 'device_initcall'.
It can be marked as __init to save a few bytes of memory.
Signed-off-by: Christophe JAILLET
---
drivers/base/topology.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/topology.c
On Tue, Jun 09, 2020 at 11:29:43AM +0200, Bartlomiej Zolnierkiewicz wrote:
> Fix the recent regression.
>
> Fixes: dbc7ece12a38 ("video: uvesafb: use true,false for bool variables")
> Cc: Jason Yan
> Reviewed-by: Sam Ravnborg
> Signed-off-by: Bartlomiej Zolnierkiewicz
Hi Bartlomiej
I was
'early_resume_init()' and 'late_resume_init() 'are only called respectively
via 'early_resume_init' and 'late_resume_init'.
They can be marked as __init to save a few bytes of memory.
Signed-off-by: Christophe JAILLET
---
drivers/base/power/trace.c | 4 ++--
1 file changed, 2 insertions(+), 2
Hi Linus:
This push contains a number of fixes:
- NULL dereference in octeontx.
- PM reference imbalance in ks-sa.
- Dead-lock in crypto manager.
- Memory leak in drbg.
- Missing socket limit check on receive SG list size in algif_skcipher.
- Typos in caam.
- Warnings in ccp and hisilicon.
The
> out and this commit was modified to prints an error message. it is an
> inappropriate conversion by used phy_read_poll_timeout() to introduce
> this bug. so fix this issue by use read_poll_timeout() to replace
> phy_read_poll_timeout().
Will another wording variant be nicer (with less typos)
'cpu_pm_init()' is only called via 'core_initcall'.
It can be marked as __init to save a few bytes of memory.
Signed-off-by: Christophe JAILLET
---
kernel/cpu_pm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/cpu_pm.c b/kernel/cpu_pm.c
index
Hi Günter,
On Sat, Jun 20, 2020 at 10:09 PM Guenter Roeck wrote:
> On Mon, Jun 08, 2020 at 03:22:17PM +0200, Geert Uytterhoeven wrote:
> > On systems with at least 32 MiB, but less than 32 GiB of RAM, the DMA
> > memory pools are much larger than intended (e.g. 2 MiB instead of 128
> > KiB on a
Alexander Kapshuk wrote on Sat, Jun 20, 2020:
> Use (un)lock_task_sighand instead of spin_lock_irqsave and
> spin_unlock_irqrestore to ensure current->sighand is a valid pointer as
> suggested in the email referenced below.
Thanks for v2! Patch itself looks good to me.
I always add another
On Sat, Jun 20, 2020 at 06:05:29PM +0300, Denis Efremov wrote:
> >From Documentation/filesystems/sysfs.txt:
> - show() must not use snprintf() when formatting the value to be
> returned to user space. If you can guarantee that an overflow
> will never happen you can use sprintf() otherwise you
On Sat, Jun 20, 2020 at 03:56:39PM +0300, Vadym Kochan wrote:
> But it will look same as prestera_destroy_ports(), do you think
> this is not a problem to have a same logic doubled ?
No, error paths of init() usually share logic with fini(). The benefits
of being consistent, always having init()
weeks ago
config: alpha-randconfig-s032-20200621 (attached as .config)
compiler: alpha-linux-gcc (GCC) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-rc2-13-gc59158c8-dirty
git checkout bbd7ffdbef6888459f301c5889f3b14ada38b913
# save the attached
Small fixes and adapt essiv support to the new template format
Gilad Ben-Yossef (3):
crypto: ccree: fix resource leak on error path
crypto: ccree: adapt ccree essiv supprot to kcapi
crypto: ccree: remove unused field
drivers/crypto/ccree/cc_cipher.c | 149 ++-
Fix a small resource leak on the error path of cipher processing.
Signed-off-by: Gilad Ben-Yossef
---
drivers/crypto/ccree/cc_cipher.c | 30 ++
1 file changed, 18 insertions(+), 12 deletions(-)
diff --git a/drivers/crypto/ccree/cc_cipher.c
Remove yet another unused field left over from times gone by.
Signed-off-by: Gilad Ben-Yossef
---
drivers/crypto/ccree/cc_cipher.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/crypto/ccree/cc_cipher.c b/drivers/crypto/ccree/cc_cipher.c
index 6575e216262b..79cfb47c759c 100644
---
The ESSIV support in ccree was added before the kernel
generic support and using a slightly different API.
This patch brings the ccree essiv interface into
compliance with kernel crypto api one.
Since CryptoCell only support 256 bit AES key for ESSIV,
also use a fallback if requested a smaller
On Fri, Jun 19, 2020 at 11:07:12PM -0500, Daniel Díaz wrote:
> Hello!
>
> On 6/19/20 9:28 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.7.5 release.
> > There are 376 patches in this series, all will be posted as a response
> > to this one. If anyone
On Sat, Jun 20, 2020 at 10:52:19AM +0100, Jon Hunter wrote:
>
> On 19/06/2020 15:28, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.7.5 release.
> > There are 376 patches in this series, all will be posted as a response
> > to this one. If anyone has any
> Fix a small resource leak on the error path of cipher processing.
Would you like to add the tag “Fixes” to the commit message?
…
> +++ b/drivers/crypto/ccree/cc_cipher.c
…
> @@ -190,21 +198,19 @@ static int cc_cipher_init(struct crypto_tfm *tfm)
…
> - return rc;
> +out_key:
> +
I started to see this warning recently:
[ 474.827893] [ cut here ]
[ 474.827894] WARNING: CPU: 28 PID: 3984 at kernel/rcu/tree.c:453
rcu_is_cpu_rrupt_from_idle+0x29/0x40
[ 474.827894] Modules linked in: vfio_pci vfio_virqfd vfio_iommu_type1 vfio
xfs rfcomm
Hi Atish,
Le 6/20/20 à 5:04 AM, Alex Ghiti a écrit :
Hi Atish,
Le 6/19/20 à 2:16 PM, Atish Patra a écrit :
On Thu, Jun 18, 2020 at 9:28 PM Alex Ghiti wrote:
Hi Atish,
Le 6/18/20 à 8:47 PM, Atish Patra a écrit :
On Wed, Jun 3, 2020 at 8:38 AM Alexandre Ghiti wrote:
Improve best_map_size
ago
config: microblaze-randconfig-c022-20200621 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All errors (new ones prefixed by >>):
>> ERROR: "min_low_pfn" [driv
This little series adds the last forgotten feature string for
NETIF_F_GSO_TUNNEL_REMCSUM and attempts to prevent such losses
in future.
Patches 2-3 seem more like net-next candidates rather than net-fixes,
but for me it seems a bit more suitable to pull it during "quiet" RC
windows, so any new
The current indentation is an absolute mess of tabs, spaces and their
mixes in different proportions. Convert it all to plain tabs and move
assignment operation char to the right, which is the most commonly
used style in Linux code.
Signed-off-by: Alexander Lobakin
---
net/ethtool/common.c |
Commit e585f2363637 ("udp: Changes to udp_offload to support remote
checksum offload") added new GSO type and a corresponding netdev
feature, but missed Ethtool's 'netdev_features_strings' table.
Give it a name so it will be exposed to userspace and become available
for manual configuration.
The ordering of netdev_features_strings[] makes no sense when it comes
to user interaction, as list of features in `ethtool -k` input is sorted
according to the corresponding bit's position.
Instead, it *does* make sense when it comes to adding new netdev_features
or modifying existing ones. We
On Fri, Mar 06, 2020 at 08:56:06PM +0800, Po Liu wrote:
> Hardware may own many entries for police flow. So that make one(or
> multi) flow to be policed by one hardware entry. This patch add the
> police action index provide to the driver side make it mapping the
> driver hardware entry index.
>
Hello,
syzbot found the following crash on:
HEAD commit:7ae77150 Merge tag 'powerpc-5.8-1' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1772c3a910
kernel config: https://syzkaller.appspot.com/x/.config?x=be4578b3f1083656
Nothing interesting, just killing some stuff first.
Based on top of io_uring-5.8 + 15 async-buf patches.
Pavel Begunkov (4):
io_uring: remove setting REQ_F_MUST_PUNT in rw
io_uring: remove REQ_F_MUST_PUNT
io_uring: set @poll->file after @poll init
io_uring: kill NULL checks for submit
I propose to avoid a typo in the previous patch subject.
> This patch brings the ccree essiv interface into
> compliance with kernel crypto api one.
Can an imperative wording be nicer for the commit message?
After recent changes, io_submit_sqes() always passes valid submit state,
so kill leftovers checking it for NULL.
Signed-off-by: Pavel Begunkov
---
fs/io_uring.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/fs/io_uring.c b/fs/io_uring.c
index
REQ_F_MUST_PUNT may seem looking good and clear, but it's the same
as not having REQ_F_NOWAIT set. That rather creates more confusion.
Moreover, it doesn't even affect any behaviour (e.g. see the patch
removing it from io_{read,write}).
Kill theg flag and update already outdated comments.
io_{read,write}() {
...
copy_iov: // prep async
if (!(flags & REQ_F_NOWAIT) && !file_can_poll(file))
flags |= REQ_F_MUST_PUNT;
}
REQ_F_MUST_PUNT there is pointless, because if it happens then
REQ_F_NOWAIT is known to be _not_ set, and the request will go
async path
It's a good practice to modify fields of a struct after but not before
it was initialised. Even though io_init_poll_iocb() doesn't touch
poll->file, call it first.
Signed-off-by: Pavel Begunkov
---
fs/io_uring.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/io_uring.c
Michael Ellerman writes:
> On Tue, 16 Jun 2020 23:56:16 +1000, Michael Ellerman wrote:
>> Currently the macro that inserts entries into the SPU syscall table
>> doesn't actually use the "nr" (syscall number) parameter.
>>
>> This does work, but it relies on the exact right number of syscall
>>
This is detected by Coverity scan: #CID: 1464472(CHECKED_RETURN)
FIXES: c94082656dac7(x86: Use enum instead of literals for trap values)
Signed-off-by: Bo YU
---
arch/x86/kernel/traps.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/traps.c
On Sun, Jun 21, 2020 at 11:45 AM Dominique Martinet
wrote:
>
> Alexander Kapshuk wrote on Sat, Jun 20, 2020:
> > Use (un)lock_task_sighand instead of spin_lock_irqsave and
> > spin_unlock_irqrestore to ensure current->sighand is a valid pointer as
> > suggested in the email referenced below.
>
>
-20200621 (attached as .config)
compiler: riscv32-linux-gcc (GCC) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-rc2-13-gc59158c8-dirty
git checkout ccfc639a94f25eb8639e8ffbecad2f6b60d22eb1
# save the attached .config to linux build tree
make
From: Leon Romanovsky
Two small patches to simplify and improve XRC logic.
Maor Gottlieb (2):
RDMA: Clean ib_alloc_xrcd() and reuse it to allocate XRC domain
RDMA/core: Optimize XRC target lookup
drivers/infiniband/core/uverbs_cmd.c | 12 ++---
drivers/infiniband/core/verbs.c | 69
Syzbot reports an use-after-free in workqueue context:
BUG: KASAN: use-after-free in mutex_unlock+0x19/0x40 kernel/locking/mutex.c:737
mutex_unlock+0x19/0x40 kernel/locking/mutex.c:737
__smsc95xx_mdio_read drivers/net/usb/smsc95xx.c:217 [inline]
smsc95xx_mdio_read+0x583/0x870
From: Leon Romanovsky
Hi,
This is combination of fixes and refactoring in MAD layer. Because
everything here is "old", I'm sending it to rdma-next and not "wasting"
our time in attempt to separate fix patches from refactoring ones.
Thanks
Shay Drory (4):
IB/mad: Fix use after free when
I propose to combine two tags in the previous patch subject.
> pm_runtime_get_sync() increments the runtime PM usage counter even
> when it returns an error code. Thus a pairing decrement is needed on
> the error handling path to keep the counter balanced.
* Can an imperative wording be nicer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Linus,
Please pull some more powerpc fixes for 5.8.
These have all been in linux-next since Thursday, but I rebased last night to
drop a commit, so the time stamps on the last few commits reflect that.
The following changes since commit
+ acme for an FYI.
On Sun, Jun 21, 2020 at 04:33:23PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (perf) failed
> like this:
>
> In file included from trace/beauty/tracepoints/x86_msr.c:10:
>
Alexander Kapshuk wrote on Sun, Jun 21, 2020:
> Thanks for your feedback.
> Shall I simply resend the v2 patch with the commit message reworded as
> you suggested, or should I make it a v3 patch instead?
Yes please resend the same commit reworded. v2 or v3 doesn't matter
much, the [PATCH
On 19/06/2020 12:56, chao hao wrote:
> On Wed, 2020-06-17 at 11:22 +0200, Matthias Brugger wrote:
>>
>> On 17/06/2020 05:00, Chao Hao wrote:
>>> Some platforms(ex: mt6779) have a new register called by REG_MMU_WR_LEN
>>> to improve performance.
>>> This patch add this register definition.
>>
>>
On Sun, Jun 21, 2020 at 1:52 AM Barry Song wrote:
>
> right now, all new ZIP drivers are using crypto_acomp APIs rather than
> legacy crypto_comp APIs. But zswap.c is still using the old APIs. That
> means zswap won't be able to use any new zip drivers in kernel.
>
> This patch moves to use
Hi Markus,
On Sun, Jun 21, 2020 at 1:11 PM Markus Elfring wrote:
>
> I propose to avoid a typo in the previous patch subject.
>
>
> > This patch brings the ccree essiv interface into
> > compliance with kernel crypto api one.
>
> Can an imperative wording be nicer for the commit message?
>
Fix a small resource leak on the error path of cipher processing.
Signed-off-by: Gilad Ben-Yossef
Fixes: 63ee04c8b491e ("crypto: ccree - add skcipher support")
Cc: Markus Elfring
---
drivers/crypto/ccree/cc_cipher.c | 30 ++
1 file changed, 18 insertions(+), 12
The ESSIV support in ccree was added before the kernel
generic support and using a slightly different API.
Brings the ccree essiv interface into compliance with
kernel crypto api one.
Since CryptoCell only support 256 bit AES key for ESSIV,
also use a fallback if requested a smaller key size.
On Sun, Jun 21, 2020 at 1:57 PM Dominique Martinet
wrote:
>
> Alexander Kapshuk wrote on Sun, Jun 21, 2020:
> > Thanks for your feedback.
> > Shall I simply resend the v2 patch with the commit message reworded as
> > you suggested, or should I make it a v3 patch instead?
>
> Yes please resend the
Remove yet another unused field left over from times gone by.
Signed-off-by: Gilad Ben-Yossef
---
drivers/crypto/ccree/cc_cipher.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/crypto/ccree/cc_cipher.c b/drivers/crypto/ccree/cc_cipher.c
index 162871464438..442965b4cd9b 100644
---
Small fixes and adapt essiv support to the new template format
---
Changes from v1:
- Incorporate coding style fixes suggested by Markus Elfring.
Gilad Ben-Yossef (3):
crypto: ccree: fix resource leak on error path
crypto: ccree: adapt ccree essiv support to kcapi
crypto: ccree: remove
Syzbot reports a NULL-ptr deref in the kref_put() call:
BUG: KASAN: null-ptr-deref in media_request_put
drivers/media/mc/mc-request.c:81 [inline]
kref_put include/linux/kref.h:64 [inline]
media_request_put drivers/media/mc/mc-request.c:81 [inline]
media_request_close+0x4d/0x170
> -Original Message-
> From: Vitaly Wool [mailto:vitaly.w...@konsulko.com]
> Sent: Sunday, June 21, 2020 11:16 PM
> To: Song Bao Hua (Barry Song)
> Cc: Andrew Morton ;
> herb...@gondor.apana.org.au; da...@davemloft.net;
> linux-cry...@vger.kernel.org; Linux-MM ; LKML
> ; Linuxarm ; Luis
There was a recent discussion about this code:
https://lore.kernel.org/linux-iio/20200322165317.0b1f0674@archlinux/
This looks like a good time to removed this, since any issues about it
should pop-up under testing, because the iio_dev is having a bit of an
overhaul and stuff being moved to
There are plenty of bad designs we want to discourage or not have to review
manually usually about accessing private (marked as [INTERN]) fields of
'struct iio_dev'.
Sometimes users copy drivers that are not always the best examples.
A better idea is to hide those fields into the framework.
For
Same as with other private fields, this moves the event interface reference
to the opaque IIO device object, to be invisible to drivers.
Signed-off-by: Alexandru Ardelean
---
drivers/iio/industrialio-core.c | 5 ++-
drivers/iio/industrialio-event.c | 68 +++-
This change moves all iio_dev debugfs fields to the iio_dev_priv object.
It's not the biggest advantage yet (to the whole thing of abstractization)
but it's a start.
Signed-off-by: Alexandru Ardelean
---
drivers/iio/industrialio-core.c | 40 ++---
This change moves the 'buffer_list' away from the public IIO device object
into the private part.
Signed-off-by: Alexandru Ardelean
---
drivers/iio/industrialio-buffer.c | 38 +++
drivers/iio/industrialio-core.c | 2 +-
include/linux/iio/iio-opaque.h| 2 ++
All users of this helper have been updated to not use it.
Remove it now, so that we don't need to move it when creating the
iio_dev_opaque structure.
Signed-off-by: Alexandru Ardelean
---
include/linux/iio/iio.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/include/linux/iio/iio.h
This change starts to hide some internal fields of the IIO device into
the framework.
This patchset assumes that all drivers have been addressed with respect
to the use of iio_priv_to_dev(), so the first patch in the series (now)
is to remove it, so that we don't need to move it.
V2 series:
This change bit straightforward and simple, since the
'channel_attr_list' & 'chan_attr_group' fields are only used in
'industrialio-core.c'.
This change moves to the private IIO device object
Signed-off-by: Alexandru Ardelean
---
drivers/iio/industrialio-core.c | 46
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
fs/file.c
between commit:
d3868eea5cbc ("fs: Move __scm_install_fd() to __fd_install_received()")
from the kspp tree and commit:
60997c3d45d9 ("close_range: add CLOSE_RANGE_UNSHARE")
from the pidfd tree.
I fixed it
> …, reorder media_request_alloc() such that …
Wording adjustments:
…, reorder statements in the implementation of the function
“media_request_alloc” so that …
> … the last step thus
… the last step.
Thus media_request_close() …
Would you like to add the tag “Fixes” to the commit message?
On 6/20/2020 12:49 AM, Fabio Estevam wrote:
> On Fri, Jun 19, 2020 at 6:46 PM Fabio Estevam wrote:
>
>> If in the future more SoCs will use this IP, then we will need to keep
>> extending this list over and over again.
>>
>> Maybe you could use:
>>
>> depends on MACH_IMX || COMPILE_TEST
>
>
> Fix a small resource leak on the error path of cipher processing.
I find it more appropriate to resend this patch series with a cover letter
together with all update steps.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 6469e8962c20b580b471790fe42367750599
commit: 4647e021193d638d3c87d1f1b9a5f7f7a48f36a3 net: stmmac: selftests: Add
selftest for L3/L4 Filters
date: 10 months ago
config: riscv-randconfig-s031-20200621
On 6/21/20 1:35 AM, Geert Uytterhoeven wrote:
> Hi Günter,
>
> On Sat, Jun 20, 2020 at 10:09 PM Guenter Roeck wrote:
>> On Mon, Jun 08, 2020 at 03:22:17PM +0200, Geert Uytterhoeven wrote:
>>> On systems with at least 32 MiB, but less than 32 GiB of RAM, the DMA
>>> memory pools are much larger
> Brings the ccree essiv interface …
Wording adjustments:
Bring the …
> also use a fallback if requested a smaller key size.
… fallback if a smaller key size was requested.
Regards,
Markus
1 - 100 of 416 matches
Mail list logo
