Hello Jernej,
Thanks for the patch.
On Wed, 20 May 2020 at 14:12, Jernej Skrabec wrote:
>
> If VPU supports untiled output, it actually supports several different
> YUV 4:2:0 layouts, namely NV12, NV21, YUV420 and YVU420.
>
> Add support for all of them.
>
> Signed-off-by: Jernej Skrabec
> ---
On Fri, Jun 05, 2020 at 11:04:51AM -0700, Guenter Roeck wrote:
> On Fri, Jun 05, 2020 at 10:18:21PM +0530, Manikandan wrote:
> > On Fri, May 29, 2020 at 10:30:16AM -0700, Guenter Roeck wrote:
> > > On 5/29/20 5:46 AM, Manikandan Elumalai wrote:
> > > > The adm1278 temperature sysfs attribute need
Add maintainer entry for new Broadcom VK Driver
Signed-off-by: Scott Branden
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 411cd97bb485..ced084c526df 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3656,6 +3656,13 @@ L:
Add FIRMWARE_PARTIAL_READ support for integrity
measurement on partial reads of firmware files.
Signed-off-by: Scott Branden
---
drivers/base/firmware_loader/main.c | 6 +-
fs/exec.c | 6 --
include/linux/fs.h | 1 +
Add Broadcom VK driver offload engine.
This driver interfaces to the VK PCIe offload engine to perform
should offload functions as video transcoding on multiple streams
in parallel. VK device is booted from files loaded using
request_firmware_into_buf mechanism. After booted card status is
Add firmware tests for partial file reads of request_firmware_into_buf.
Signed-off-by: Scott Branden
---
.../selftests/firmware/fw_filesystem.sh | 80 +++
1 file changed, 80 insertions(+)
diff --git a/tools/testing/selftests/firmware/fw_filesystem.sh
Add additional hooks to test_firmware to pass in support
for partial file read using request_firmware_into_buf.
buf_size: size of buffer to request firmware into
partial: indicates that a partial file request is being made
file_offset: to indicate offset into file to request
Signed-off-by: Scott
Add offset to request_firmware_into_buf to allow for portions
of firmware file to be read into a buffer. Necessary where firmware
needs to be loaded in portions from file in memory constrained systems.
Signed-off-by: Scott Branden
---
drivers/base/firmware_loader/firmware.h | 5 +++
Add user space api for bcm-vk driver.
Signed-off-by: Scott Branden
---
include/uapi/linux/misc/bcm_vk.h | 99
1 file changed, 99 insertions(+)
create mode 100644 include/uapi/linux/misc/bcm_vk.h
diff --git a/include/uapi/linux/misc/bcm_vk.h
Add kernel_pread_file* support to kernel to allow for partial read
of files with an offset into the file. Existing kernel_read_file
functions call new kernel_pread_file functions with offset=0 and
opt=KERNEL_PREAD_WHOLE.
Signed-off-by: Scott Branden
---
fs/exec.c | 95
This patch series adds partial read support in request_firmware_into_buf.
In order to accept the enhanced API it has been requested that kernel
selftests and upstreamed driver utilize the API enhancement and so
are included in this patch series.
Also in this patch series is the addition of a new
Hello
The race window I mentioned in the commit message is pretty small. So it’s
difficult to reproduce it.
But with the following ‘delay’ patch, it can be very easy to reproduce.
```
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index c17e6eb9ad43..b6728bf80a7d 100644
---
Hi Matthew,
On 2020-06-05 8:20 p.m., Matthew Wilcox wrote:
On Fri, Jun 05, 2020 at 03:59:52PM -0700, Scott Branden wrote:
-int kernel_read_file(struct file *file, void **buf, loff_t *size,
-loff_t max_size, enum kernel_read_file_id id)
-{
- loff_t i_size, pos;
+int
On 2020/06/05 Fri 21:00, Chandrakanth Patil wrote:
Hi Kai Liu,
Tomcat (Device ID: 0017) belongs to Gen3.5 controllers (Ventura family of
controllers). So this issue is applicable.
As this is an OEM specific firmware, Please contact Broadcom support team in
order get the correct firmware image.
When we hit the fadump crash via the panic path the pstore update is
missing. This is observed when commit 8341f2f222d7 ("sysrq: Use panic()
to force a crash") changed the sysrq-trigger to take panic path instead
of die path.
The PPC panic event handler addresses the system panic in two different
Commit b1394e745b94 ("KVM: x86: fix APIC page invalidation") tried to
fix inappropriate APIC page invalidation by re-introducing arch specific
kvm_arch_mmu_notifier_invalidate_range() and calling it from
kvm_mmu_notifier_invalidate_range_start. But threre could be the
following race because VMCS
Hi Tony,
I love your patch! Perhaps something to improve:
[auto build test WARNING on kvms390/next]
[also build test WARNING on linus/master v5.7]
[cannot apply to s390/features linux/master next-20200605]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve
This patch adds the interconnects property for the gpu node and the
opp-peak-kBps property to the opps of the gpu opp table. This should
help enable DDR bandwidth scaling dynamically and proportionally to the
GPU frequency.
Signed-off-by: Sharat Masetty
---
arch/arm64/boot/dts/qcom/sdm845.dtsi
Update documentation to list the gpu opp table bindings including the
newly added "opp-peak-kBps" needed for GPU-DDR bandwidth scaling.
Signed-off-by: Sharat Masetty
Acked-by: Rob Herring
---
.../devicetree/bindings/display/msm/gpu.txt| 28 ++
1 file changed, 28
This patch changes the plumbing to send the devfreq recommended opp rather
than the frequency. Also consolidate and rearrange the code in a6xx to set
the GPU frequency and the icc vote in preparation for the upcoming
changes for GPU->DDR scaling votes.
Signed-off-by: Sharat Masetty
---
Add opp-peak-kBps bindings to the GPU opp table, listing the peak
GPU -> DDR bandwidth requirement for each opp level. This will be
used to scale the DDR bandwidth along with the GPU frequency dynamically.
Signed-off-by: Sharat Masetty
Reviewed-by: Matthias Kaehlcke
---
This patches replaces the previously used static DDR vote and uses
dev_pm_opp_set_bw() to scale GPU->DDR bandwidth along with scaling
GPU frequency. Also since the icc path voting is handled completely
in the opp driver, remove the icc_path handle and its usage in the
drm driver.
Signed-off-by:
This patch adds the interconnects property to the GPU node. This enables
the GPU->DDR path bandwidth voting.
Signed-off-by: Sharat Masetty
---
arch/arm64/boot/dts/qcom/sc7180.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi
This is a respin of [1]. Incorported review feedback and fixed issues observed
during testing. Picked up the Georgi's series from opp/linux-next [2], and this
series is also dependent on a helper function needed to set and clear ddr
bandwidth vote [3]. Patch number 4 in the series adds support for
I have an urgent message for you, reply me now
Anders Karlsson, CFO Swedbank
From: Patricia Alfonso
Integrate KASAN into KUnit testing framework.
- Fail tests when KASAN reports an error that is not expected
- Use KUNIT_EXPECT_KASAN_FAIL to expect a KASAN error in KASAN
tests
- Expected KASAN reports pass tests and are still printed when
From: Patricia Alfonso
Transfer all previous tests for KASAN to KUnit so they can be run
more easily. Using kunit_tool, developers can run these tests with their
other KUnit tests and see "pass" or "fail" with the appropriate KASAN
report instead of needing to parse each KASAN report to test
On MIPS system which has rixi hardware bit, page access bit is not
set in pgrot. For memory reading, there will be one page fault to
allocate physical page; however valid bit is not set, there will
be the second fast tlb-miss fault handling to set valid/access bit.
This patch set page
KASAN errors will currently trigger a panic when panic_on_warn is set.
This renders kasan_multishot useless, as further KASAN errors won't be
reported if the kernel has already paniced. By making kasan_multishot
disable this behaviour for KASAN errors, we can still have the benefits
of
From: Patricia Alfonso
Include documentation on how to test KASAN using CONFIG_TEST_KASAN_KUNIT
and CONFIG_TEST_KASAN_MODULE.
Signed-off-by: Patricia Alfonso
Reviewed-by: Dmitry Vyukov
Signed-off-by: David Gow
Reviewed-by: Andrey Konovalov
---
Documentation/dev-tools/kasan.rst | 70
From: Patricia Alfonso
In order to integrate debugging tools like KASAN into the KUnit
framework, add KUnit struct to the current task to keep track of the
current KUnit test.
Signed-off-by: Patricia Alfonso
Reviewed-by: Brendan Higgins
Signed-off-by: David Gow
---
include/linux/sched.h | 4
This patchset contains everything needed to integrate KASAN and KUnit.
KUnit will be able to:
(1) Fail tests when an unexpected KASAN error occurs
(2) Pass tests when an expected KASAN error occurs
Convert KASAN tests to KUnit with the exception of copy_user_test
because KUnit is unable to test
On Linux system, writable applies readable privilege in most
architectures, this patch adds this policy on MIPS platform
where hardware rixi is supported.
Signed-off-by: Bibo Mao
---
arch/mips/mm/cache.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi Amit,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on robh/for-next]
[also build test WARNING on clk/clk-next pza/reset/next linus/master v5.7
next-20200605]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system
On Fri, Jun 05, 2020 at 11:57:51AM +0300, Dan Carpenter wrote:
> On Fri, Jun 05, 2020 at 06:04:31AM +, Song Bao Hua (Barry Song) wrote:
> >
> >
> > > -Original Message-
> > > From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> > > Sent: Thursday, June 4, 2020 11:37 PM
> > > To:
On Fri, Jun 05, 2020 at 03:59:52PM -0700, Scott Branden wrote:
> -int kernel_read_file(struct file *file, void **buf, loff_t *size,
> - loff_t max_size, enum kernel_read_file_id id)
> -{
> - loff_t i_size, pos;
> +int kernel_pread_file(struct file *file, void **buf, loff_t
On Fri, Jun 5, 2020 at 9:54 PM Kyle Evans wrote:
>
> On Fri, Jun 5, 2020 at 9:55 AM Szabolcs Nagy wrote:
> >
> > * Christian Brauner [2020-06-02 22:42:17
> > +0200]:
> > > [... snip ...]
> > >
> > > First, it helps to close all file descriptors of an exec()ing task. This
> > > can be done
Hi Sean,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on tip/auto-latest v5.7 next-20200605]
[cannot apply to bp/for-next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we
On 6/5/2020 10:05 PM, Peter Zijlstra wrote:
On Fri, Jun 05, 2020 at 06:17:51AM -0700, Eric Dumazet wrote:
On Fri, Jun 5, 2020 at 1:10 AM kernel test robot wrote:
There you go.
We decided this was a bogus report, and that UBSAN requires sane compilers.
Please read the fine comment that was
On 6/6/2020 12:42 AM, Prarit Bhargava wrote:
On 6/5/20 11:29 AM, Xiaoyao Li wrote:
On 6/5/2020 7:44 PM, Prarit Bhargava wrote:
There are two problems with kernel messages in fatal mode that
were found during testing of guests and userspace programs.
The first is that no kernel message is
On Fri, Jun 5, 2020 at 9:55 AM Szabolcs Nagy wrote:
>
> * Christian Brauner [2020-06-02 22:42:17
> +0200]:
> > [... snip ...]
> >
> > First, it helps to close all file descriptors of an exec()ing task. This
> > can be done safely via (quoting Al's example from [1] verbatim):
> >
> > /*
Hi Tony,
I love your patch! Perhaps something to improve:
[auto build test WARNING on kvms390/next]
[also build test WARNING on linus/master v5.7]
[cannot apply to s390/features linux/master next-20200605]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve
On 6/6/2020 3:26 AM, Sean Christopherson wrote:
Choo! Choo! All aboard the Split Lock Express, with direct service to
Wreckage!
Skip split_lock_verify_msr() if the CPU isn't whitelisted as a possible
SLD-enabled CPU model to avoid writing MSR_TEST_CTRL. MSR_TEST_CTRL
exists, and is writable,
Hi Scott,
I love your patch! Yet something to improve:
[auto build test ERROR on next-20200605]
[cannot apply to char-misc/char-misc-testing driver-core/driver-core-testing
kselftest/next integrity/next-integrity linus/master v5.7 v5.7-rc7 v5.7-rc6
v5.7]
[if your patch is applied to the wrong
| |-- ld:smp.c:(.text):undefined-reference-to-__umoddi3
| `-- smp.c:(.text):undefined-reference-to-__udivdi3
`-- i386-randconfig-c001-20200605
|-- kernel-smp.c:undefined-reference-to-__udivdi3
|-- ld:kernel-smp.c:undefined-reference-to-__udivdi3
`-- ld:kernel-smp.c:undefined
On Fri, 2020-06-05 at 17:32 -0700, Andrew Morton wrote:
> On Fri, 05 Jun 2020 11:24:43 -0700 Joe Perches wrote:
>
> > IS_ENABLED is almost always used with CONFIG_ defines.
> >
> > Add a test to verify that the #define being tested starts with CONFIG_.
>
> Yay.
>
> I wonder if there's a
On Fri, May 29, 2020 at 11:02:15PM +0100, David Howells wrote:
> +static struct afs_volume *afs_sample_volume(struct afs_cell *cell, struct
> key *key,
> + const char *name, unsigned int
> namelen)
> +{
> + struct afs_volume *volume;
> + struct
On Fri, Jun 05, 2020 at 11:53:05AM +0200, Bartosz Golaszewski wrote:
> czw., 4 cze 2020 o 18:00 Kent Gibson napisał(a):
> >
>
> [snip!]
>
> > > > +
> > > > +enum gpioline_edge {
> > > > + GPIOLINE_EDGE_NONE = 0,
> > > > + GPIOLINE_EDGE_RISING= 1,
> > > > +
On Fri, Jun 05, 2020 at 05:40:53PM -0700, Andrew Morton wrote:
> On Fri, 5 Jun 2020 09:00:10 -0700 Kees Cook wrote:
>
> > While looking at the code paths for the proposed O_MAYEXEC flag, I saw
> > some things that looked like they should be fixed up.
> >
> > exec: Change uselib(2) IS_SREG()
On 2020/6/5 下午11:49, Eric Biggers wrote:
On Fri, Jun 05, 2020 at 11:26:20PM +0800, Zhangfei Gao wrote:
On 2020/6/5 下午8:17, Herbert Xu wrote:
On Fri, Jun 05, 2020 at 05:34:32PM +0800, Zhangfei Gao wrote:
Will add a check after the copy.
strlcpy(interface.name,
Hi Tony,
I love your patch! Perhaps something to improve:
[auto build test WARNING on kvms390/next]
[also build test WARNING on linus/master v5.7]
[cannot apply to s390/features linux/master next-20200605]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve
Hi Tony,
I love your patch! Perhaps something to improve:
[auto build test WARNING on kvms390/next]
[also build test WARNING on linus/master v5.7]
[cannot apply to s390/features linux/master next-20200605]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve
Hi all,
Commit
1c82ca4f876d ("RISC-V: Force select RISCV_INTC for CONFIG_RISCV")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpTO9ql0kqAM.pgp
Description: OpenPGP digital signature
Hello Greg,
Thank you for continuing to work with me through this.
On Fri, Jun 5, 2020 at 1:02 AM Greg Kroah-Hartman
wrote:
>
> On Thu, Jun 04, 2020 at 12:38:18PM -0700, Rajat Jain wrote:
> > Hello,
> >
> > I spent some more thoughts into this...
> >
> > On Wed, Jun 3, 2020 at 5:16 AM Greg
On Fri, 5 Jun 2020 17:11:05 +0800 Bibo Mao wrote:
> On MIPS system which has rixi hardware bit, page access bit is not
> set in pgrot. For memory reading, there will be one page fault to
> allocate physical page; however valid bit is not set, there will
> be the second fast tlb-miss fault
On Fri, 5 Jun 2020 12:46:55 +0100 Catalin Marinas
wrote:
> On Fri, Jun 05, 2020 at 11:08:13AM +0100, Catalin Marinas wrote:
> > This patch causes a kernel panic on arm64 (and possibly powerpc, I
> > haven't tried). arm64 still uses the 5level-fixup.h and pud_alloc()
> > checks for the empty p4d
On Fri, 5 Jun 2020 20:23:07 +0200 Geert Uytterhoeven
wrote:
> Hi Adrian,
>
> On Fri, Jun 5, 2020 at 7:58 PM John Paul Adrian Glaubitz
> wrote:
> > On 6/5/20 5:59 PM, Rich Felker wrote:
> > >> Ah, sorry, I missed that. You're right, it should probably go through
> > >> someone else's tree
Linus Torvalds writes:
> On Fri, Jun 5, 2020 at 12:01 PM Linus Torvalds
> wrote:
>>
>> ..and then when I actually compared whether I otherwise got the same
>> result as you, I realized that this all depends on the module tree.
>>
>> I'll go merge that first, and then re-do this all. Oh well.
>
>
Linus Torvalds writes:
> On Fri, Jun 5, 2020 at 9:38 AM Michael Ellerman wrote:
>>
>> I've pushed the result of my resolution of the conflicts to the powerpc/merge
>> branch, if you want to look at that, though I've also tried to describe it in
>> full below.
>
> I ended up doing the
Hi Tony,
I love your patch! Perhaps something to improve:
[auto build test WARNING on kvms390/next]
[also build test WARNING on linus/master v5.7]
[cannot apply to s390/features linux/master next-20200605]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve
On Fri, 5 Jun 2020 09:00:10 -0700 Kees Cook wrote:
> While looking at the code paths for the proposed O_MAYEXEC flag, I saw
> some things that looked like they should be fixed up.
>
> exec: Change uselib(2) IS_SREG() failure to EACCES
> This just regularizes the return code on
Consider this example where -> means LHS device is a consumer of RHS
device and indentation represents "child of" of the previous device.
Device A -> Device C
Device B -> Device A
Device C
Without this commit:
1. Device A is added.
2. Device A is added to waiting for supplier list
Patch 2/2 explain the series. Just using a cover letter to thread the
series and add CC's.
-Saravana
Saravana Kannan (2):
driver core: Add device_is_dependent() to linux/device.h
of: property: Improve cycle detection when one of the devices is never
added
drivers/base/core.c| 2 +-
DT implementation of fw_devlink needs this function to detect cycles. So
make it available.
Signed-off-by: Saravana Kannan
---
drivers/base/core.c| 2 +-
include/linux/device.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/base/core.c b/drivers/base/core.c
On Tue, Jun 02, 2020 at 04:15:19PM +0200, Vlastimil Babka wrote:
> The attribute reflects the SLAB_RECLAIM_ACCOUNT cache flag. It's not clear why
> this attribute was writable in the first place, as it's tied to how the cache
> is used by its creator, it's not a user tunable. Furthermore:
>
> -
On Tue, Jun 02, 2020 at 04:15:18PM +0200, Vlastimil Babka wrote:
> SLUB_DEBUG creates several files under /sys/kernel/slab// that can be
> read to check if the respective debugging options are enabled for given cache.
> Some options, namely sanity_checks, trace, and failslab can be also enabled
>
On Fri, Jun 5, 2020 at 11:24 PM Jens Axboe wrote:
>
> On 6/5/20 3:13 PM, Jens Axboe wrote:
> > On 6/5/20 2:53 PM, Jens Axboe wrote:
> >> On 6/5/20 2:36 PM, Andres Freund wrote:
> >>> Hi,
> >>>
> >>> On 2020-06-05 13:20:28 -0700, Andres Freund wrote:
> I'll go and try to figure out why I
On Tue, Jun 02, 2020 at 04:15:17PM +0200, Vlastimil Babka wrote:
> SLUB allows runtime changing of page allocation order by writing into the
> /sys/kernel/slab//order file. Jann has reported [1] that this interface
> allows the order to be set too small, leading to crashes.
>
> While it's
On Tue, Jun 02, 2020 at 04:15:16PM +0200, Vlastimil Babka wrote:
> SLUB_DEBUG creates several files under /sys/kernel/slab// that can be
> read to check if the respective debugging options are enabled for given cache.
> The options can be also toggled at runtime by writing into the files. Some of
On Fri, 05 Jun 2020 11:24:43 -0700 Joe Perches wrote:
> IS_ENABLED is almost always used with CONFIG_ defines.
>
> Add a test to verify that the #define being tested starts with CONFIG_.
Yay.
I wonder if there's a simple way of testing whether the CONFIG_ thing
can *ever* be enabled. So
rcuperf: Fix
> kfree_mult to match printk() format
> config: arm-randconfig-r004-20200605 (attached as .config)
> compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project
> 6dd738e2f0609f7d3313b574a1d471263d2d3ba1)
> reproduce (this is a W=1 build):
> wget
> https:
On Fri, 5 Jun 2020 23:06:10 + Wei Yang wrote:
> On Thu, Jun 04, 2020 at 02:51:40PM +0200, Geert Uytterhoeven wrote:
> >Hi Wei,
> >
> >On Thu, Jun 4, 2020 at 2:28 PM Wei Yang wrote:
> [...]
> >>
> >> You mean
> >>
> >>{0x0003, 2},
> >>{0x0004, 2},
>
On Sat, Feb 29, 2020 at 11:04:56AM +, Russell King - ARM Linux admin wrote:
> Adding Ted and Andreas...
>
> Here's the debugfs -n "id" output for dpkg.status.5.gz (which is fine,
> and probably a similar size):
>
> debugfs: id <917527>
> a481 30ff 0300 bd8e 475e bd77 4f5e
--
Attention: Please,
I am John Robinson, the Head of file Department in Tesco Bank Plc here
in London United Kingdom. I wish to notify you again that you were
listed as a beneficiary to the total sum of Twelve Million Five
Hundred thousand British pounds in the codicil and last testament of
our
The pull request you sent on Thu, 4 Jun 2020 19:12:59 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
> tags/ext4_for_linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0b166a57e6222666292a481b742af92b50c3ba50
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Fri, 5 Jun 2020 13:18:03 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git dlm-5.8
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e3cea0cad147a9ab4f0e74a2fbdf15d18df1f820
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Thu, 04 Jun 2020 17:58:19 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> tags/afs-next-20200604
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9daa0a27a0bce6596be287fb1df372ff80bb1087
Thank you!
--
On Fri, 2020-06-05 at 16:31 -0700, Scott Branden wrote:
> Hi Mimi,
>
> On 2020-06-05 4:19 p.m., Mimi Zohar wrote:
> > Hi Scott,
> >
> > On Fri, 2020-06-05 at 15:59 -0700, Scott Branden wrote:
> >> @@ -648,6 +667,9 @@ int ima_post_read_file(struct file *file, void *buf,
> >> loff_t size,
> >>
Hi André,
On 6/5/20 10:55 AM, André Almeida wrote:
> Create a documentation providing a background and explanation around the
> operation of the Multi-Queue Block IO Queueing Mechanism (blk-mq).
>
> The reference for writing this documentation was the source code and
> "Linux Block IO:
5.4.44-rt27-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
This is an incremental update of the zswap patch. Addtional spots were
identified, which were lacking proper locking, during the rework of the
patch for
5.4.44-rt27-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Liwei Song
The ACPI code allocates larger amount of memory during resume. This
triggers a warning because the allocation happens with disabled
interrupts.
At this stage only one CPU
5.4.44-rt27-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Kevin Hao
After commit f0b231101c94 ("mm/SLUB: delay giving back empty slubs to
IRQ enabled regions"), when the free_slab() is invoked with the IRQ
disabled, the empty slubs are
5.4.44-rt27-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: John Ogness
Even though the printk kthread is always preemptible, it is still not
allowed to call cond_resched() from within console drivers. The
task may become non-preemptible in
5.4.44-rt27-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
Include the swait.h header so it compiles even if not all patches are
applied.
Reported-by: kbuild test robot
Signed-off-by: Sebastian Andrzej Siewior
5.4.44-rt27-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Steven Rostedt (VMware)"
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index 2e9afd4a0afd..3b0c6038dae9
Dear RT Folks,
This is the RT stable review cycle of patch 5.4.44-rt27-rc1.
Please scream at me if I messed something up. Please test the patches too.
The -rc release will be uploaded to kernel.org and will be deleted when
the final release is out. This is just a review release (or release
5.4.44-rt27-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
There is no need to loop for longer. The message of too much work was
removed in commit
9d7c249a1ef9b ("serial: 8250: drop the printk from
On Thu, Jun 4, 2020 at 9:58 AM David Howells wrote:
>
> (4) Improve Ext4's time updating. Konstantin Khlebnikov said "For now,
> I've plugged this issue with try-lock in ext4 lazy time update. This
> solution is much better."
It would have been good to get acks on this from the ext4
Hi Mimi,
On 2020-06-05 4:19 p.m., Mimi Zohar wrote:
Hi Scott,
On Fri, 2020-06-05 at 15:59 -0700, Scott Branden wrote:
@@ -648,6 +667,9 @@ int ima_post_read_file(struct file *file, void *buf, loff_t
size,
enum ima_hooks func;
u32 secid;
+ if (!file && read_id ==
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev.2020.06.02a
head: 5216948905dd07a84cef8a7dc72c2ec076802efd
commit: 7d16add62717136b1839f0b3d7ea4cbb98f38c2a [67/90] rcuperf: Fix
kfree_mult to match printk() format
config: arm-randconfig-r004-20200605 (attached
Hi Scott,
On Fri, 2020-06-05 at 15:59 -0700, Scott Branden wrote:
>
> @@ -648,6 +667,9 @@ int ima_post_read_file(struct file *file, void *buf,
> loff_t size,
> enum ima_hooks func;
> u32 secid;
>
> + if (!file && read_id == READING_FIRMWARE_PARTIAL_READ)
> + return
On Thu, Jun 04, 2020 at 09:33:07PM +0800, Zhangfei Gao wrote:
> On 2020/6/2 上午1:41, Bjorn Helgaas wrote:
> > On Thu, May 28, 2020 at 09:33:44AM +0200, Joerg Roedel wrote:
> > > On Wed, May 27, 2020 at 01:18:42PM -0500, Bjorn Helgaas wrote:
> > > > Is this slowdown significant? We already iterate
Hi,
On Wed, Jun 03, 2020 at 06:21:18PM +0200, Luca Ceresoli wrote:
> dev_err() needs a terminating newline.
>
> Signed-off-by: Luca Ceresoli
> ---
Thanks, queued.
-- Sebastian
> drivers/power/reset/gpio-poweroff.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
SBS batteries optionally have support for PEC. This enables
PEC handling based on the implemented SBS version as suggested
by the standard. The support for PEC is re-evaluated when the
battery is hotplugged into the system, since there might be
systems supporting batteries from different SBS
Hi,
Second try to enable PEC for SBS battery. Mainline currently
has 3 different platforms using sbs-battery with an I2C driver
not implementing I2C_M_RECV_LEN:
* i2c-exynos5
* i2c-rk3x
* i2c-tegra
On those platforms PEC will be temporarly disabled for SBS
functions requesting strings. I
On Thu, Jun 04, 2020 at 02:51:40PM +0200, Geert Uytterhoeven wrote:
>Hi Wei,
>
>On Thu, Jun 4, 2020 at 2:28 PM Wei Yang wrote:
[...]
>>
>> You mean
>>
>>{0x0003, 2},
>>{0x0004, 2},
>>{0x1fff, 13},
>>{0x2000, 13},
>>
The SBS battery implements SMBus block reads. Currently the
driver "emulates" this by doing an I2C byte read for the
length followed by an I2C block read. The I2C subsystem
actually provides a proper API for doing SMBus block reads,
which can and should be used instead. The current implementation
Hi,
On 2020-06-05 16:56:44 -0600, Jens Axboe wrote:
> On 6/5/20 4:54 PM, Andres Freund wrote:
> > On 2020-06-05 16:49:24 -0600, Jens Axboe wrote:
> >> Yes that's expected, if we have to fallback to ->readpage(), then it'll
> >> go to a worker. read-ahead is what drives the async nature of it, as
Add user space api for bcm-vk driver.
Signed-off-by: Scott Branden
---
include/uapi/linux/misc/bcm_vk.h | 99
1 file changed, 99 insertions(+)
create mode 100644 include/uapi/linux/misc/bcm_vk.h
diff --git a/include/uapi/linux/misc/bcm_vk.h
Add FIRMWARE_PARTIAL_READ support for integrity
measurement on partial reads of firmware files.
Signed-off-by: Scott Branden
---
drivers/base/firmware_loader/main.c | 6 +-
fs/exec.c | 6 --
include/linux/fs.h | 1 +
1 - 100 of 1157 matches
Mail list logo
