On Mon, Jan 25, 2021 at 2:12 AM Zhihao Cheng wrote:
>
> 在 2021/1/23 10:45, Zhihao Cheng 写道:
>
> >> @@ -430,6 +433,7 @@ static int do_tmpfile(struct inode *dir, struct
> >> dentry *dentry,
> >> return 0;
> >> out_cancel:
> Still one question:
> > Does this need a judgment? Like this,
The
From: Finn Thain
As usual, the available documentation is inadequate and leaves endianness
unspecified for message data. However, testing shows that this patch does
improve correctness. The mistake should have been detected earlier but it
was obscured by other bugs. In testing, this patch
See below
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijm...@topicproducts.com
W: www.topicproducts.com
Please consider the environment before printing this
On Mon, Jan 25, 2021 at 2:40 PM Muchun Song wrote:
>
> On Mon, Jan 25, 2021 at 8:05 AM David Rientjes wrote:
> >
> >
> > On Sun, 17 Jan 2021, Muchun Song wrote:
> >
> > > diff --git a/mm/sparse-vmemmap.c b/mm/sparse-vmemmap.c
> > > index ce4be1fa93c2..3b146d5949f3 100644
> > > ---
On 1/25/21 2:43 PM, Chanwoo Lee wrote:
> From: ChanWoo Lee
>
> From the 4.19 kernel, thread related code has been removed in queue.c.
> So we can exclude unnecessary header file.
>
> Signed-off-by: ChanWoo Lee
Acked-by: Coly Li
Thanks.
Coly Li
> ---
> drivers/mmc/core/queue.c | 1 -
> 1
The command 'find ./kernel/rcu/ | xargs ./scripts/kernel-doc -none'
reported an issue with the kernel-doc of struct rcu_tasks.
Rectify the kernel-doc, such that no issues remain for ./kernel/rcu/.
Signed-off-by: Lukas Bulwahn
---
applies cleanly on v5.11-rc5 and next-20210122
Paul, please pick
On Mon, 2021-01-25 at 13:18 +0900, Tomasz Figa wrote:
> On Wed, Jan 20, 2021 at 4:08 PM Yong Wu wrote:
> >
> > On Wed, 2021-01-20 at 13:15 +0900, Tomasz Figa wrote:
> > > On Wed, Jan 13, 2021 at 3:45 PM Yong Wu wrote:
> > > >
> > > > On Wed, 2021-01-13 at 14:30 +0900, Tomasz Figa wrote:
> > > >
On Mon, Jan 25, 2021 at 11:52:32AM +0530, Anshuman Khandual wrote:
>
> On 12/22/20 12:42 PM, Anshuman Khandual wrote:
> > pfn_valid() asserts that there is a memblock entry for a given pfn without
> > MEMBLOCK_NOMAP flag being set. The problem with ZONE_DEVICE based memory is
> > that they do not
On 23.01.21 04:09, Martin K. Petersen wrote:
Ewan,
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 60 40 00 00 01
00
Print the cdb into a new line in any case, not only when cmd_len is
greater than 16. The above example error will then read:
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28
28
czw., 21 sty 2021 o 23:45 Vladimir Oltean napisał(a):
>
> Hi Pawel,
>
Hi Vladimir,
Thank You for Your answer.
> On Wed, Jan 20, 2021 at 07:30:18AM +0100, Pawel Dembicki wrote:
> > This patch adds support for vlan filtering in vsc73xx driver.
> >
> > After vlan filtering enable, CPU_PORT is
Fix the following coccicheck warnings:
./sound/pci/hda/hda_intel.c:2309:3-23: WARNING: Assignment of
0/1 to bool variable.
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Zhong
---
sound/pci/hda/hda_intel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Thu, 21 Jan 2021 01:18:47 -0800, Pan Bian wrote:
> Put the child node np when it fails to get or register device.
Applied to spi-nor/next, thanks!
[1/1] mtd: spi-nor: hisi-sfc: Put child node np on error path
https://git.kernel.org/mtd/c/fe6653460ee7
Best regards,
--
Tudor Ambarus
Some networking and keys LSM hooks are conditionally enabled
and when building the new sleepable BPF LSM hooks with those
LSM hooks disabled, the following build error occurs:
BTFIDS vmlinux
FAILED unresolved symbol bpf_lsm_socket_socketpair
To fix the error, conditionally add the relevant
Simplify kdb commands registration via using linked list instead of
static array for commands storage.
Signed-off-by: Sumit Garg
---
Changes in v2:
- Remove redundant NULL check for "cmd_name".
- Incorporate misc. comment.
kernel/debug/kdb/kdb_main.c| 119
Other perf tool builtins have already supported dso filter.
For example,
perf report --dso, which only considers symbols in these dsos.
Now dso filter is supported for perf-script.
root@kbl-ppc:~# ./perf script --dso "[kernel.kallsyms]"
perf 18123 [000] 6142863.075104: 1
Perf-script supports '-S' or '--symbol' options to only list the
trace records in given symbols. Symbol is typically a name
or hex address. If it's hex address, it is the start address of
one symbol.
While it would be useful if we can filter trace records by any hex
address (not only the start
Fix the following coccicheck warnings:
./net/ipv4/esp4_offload.c:288:32-34: WARNING !A || A && B is
equivalent to !A || B.
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Zhong
---
Changes in v2:
-Drop the parenthesis around !skb_is_gso(skb) now.
net/ipv4/esp4_offload.c | 2 +-
1 file
On Mon, Jan 25, 2021 at 8:05 AM David Rientjes wrote:
>
>
> On Sun, 17 Jan 2021, Muchun Song wrote:
>
> > diff --git a/mm/sparse-vmemmap.c b/mm/sparse-vmemmap.c
> > index ce4be1fa93c2..3b146d5949f3 100644
> > --- a/mm/sparse-vmemmap.c
> > +++ b/mm/sparse-vmemmap.c
> > @@ -29,6 +29,7 @@
> >
On Sat, Jan 23, 2021 at 12:50:21AM +0100, KP Singh wrote:
> On Fri, Jan 22, 2021 at 11:33 PM KP Singh wrote:
> >
> > On Fri, Jan 22, 2021 at 1:32 PM Mikko Ylinen
> > wrote:
> > >
> > > Networking LSM hooks are conditionally enabled and when building the new
> > > sleepable BPF LSM hooks with the
On 2021-01-24 05:45, Jakub Kicinski wrote:
On Fri, 22 Jan 2021 10:07:05 +0100 Martin Schiller wrote:
On 2021-01-21 01:21, Xie He wrote:
> In the lapb module, the timers may run concurrently with other code in
> this module, and there is currently no locking to prevent the code from
> racing on
On Fri, 2021-01-22 at 22:34 +0100, Krzysztof Kozlowski wrote:
> On Thu, Jan 21, 2021 at 02:24:28PM +0800, Yong Wu wrote:
> > The config MTK_SMI always depends on MTK_IOMMU which is built-in
> > currently. Thus we don't have module_exit before. This patch adds
> > module_exit and module_license. It
On Fri, 2021-01-22 at 22:35 +0100, Krzysztof Kozlowski wrote:
> On Thu, Jan 21, 2021 at 02:24:29PM +0800, Yong Wu wrote:
> > This patch switches MTK_SMI to tristate. Support it could be 'm'.
> >
> > Meanwhile, Fix a build issue while MTK_SMI is built as module.
>
> s/Fix/fix.
>
> What error is
From: ChanWoo Lee
>From the 4.19 kernel, thread related code has been removed in queue.c.
So we can exclude unnecessary header file.
Signed-off-by: ChanWoo Lee
---
drivers/mmc/core/queue.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mmc/core/queue.c b/drivers/mmc/core/queue.c
From: Lai Jiangshan
The commit 929bacec21478("x86/entry/64: De-Xen-ify our NMI code") simplified
the NMI code by changing paravirt code into native code and left a comment
about "inspecting RIP instead". But until now, "inspecting RIP instead"
has not been made happened and this patch tries to
From: David Stevens
Use the range passed to mmu_notifer's invalidate_range_start to prevent
spurious page fault retries due to changes in unrelated host virtual
addresses. This has the secondary effect of greatly reducing the
likelihood of extreme latency when handing a page fault due to another
lockdep_assert_irqs_disabled() was added to check rpmh_flush()
can only be invoked when irqs are disabled from last CPU,
this is true for APPS RSC as the last CPU going to deepest low
power mode is writing sleep and wake TCSes.
However platform drivers can invoke rpmh_write_sleep_and_wake()
to
On 12/22/20 12:42 PM, Anshuman Khandual wrote:
> pfn_valid() asserts that there is a memblock entry for a given pfn without
> MEMBLOCK_NOMAP flag being set. The problem with ZONE_DEVICE based memory is
> that they do not have memblock entries. Hence memblock_is_map_memory() will
> invariably
On 1/13/2021 9:35 PM, Vlastimil Babka wrote:
> On 1/12/21 10:21 AM, Faiyaz Mohammed wrote:
>> Reading the sys slab alloc_calls, free_calls returns the available object
>> owners, but the size of this file is limited to PAGE_SIZE
>> because of the limitation of sysfs attributes, it is returning
Hi Marc
> -Original Message-
> From: Justin He
> Sent: Wednesday, January 20, 2021 11:56 PM
> To: Marc Zyngier
> Cc: Catalin Marinas ; Will Deacon
> ; linux-arm-ker...@lists.infradead.org; linux-
> ker...@vger.kernel.org; Anshuman Khandual ;
> Suzuki Poulose ; Mark Rutland
> ; Gustavo A.
Thanks Doug for your review.
On Sat, 23 Jan 2021 at 00:12, Doug Anderson wrote:
>
> Hi,
>
> On Tue, Jan 19, 2021 at 2:50 AM Sumit Garg wrote:
> >
> > Simplify kdb commands registration via using linked list instead of
> > static array for commands storage.
> >
> > Signed-off-by: Sumit Garg
> >
Hi:
On 2021/1/25 12:36, Matthew Wilcox wrote:
> On Sun, Jan 24, 2021 at 11:24:41PM -0500, Waiman Long wrote:
>> diff --git a/mm/filemap.c b/mm/filemap.c
>> index 5c9d564317a5..aa0e0fb04670 100644
>> --- a/mm/filemap.c
>> +++ b/mm/filemap.c
>> @@ -835,6 +835,7 @@ noinline int
On 2021/1/25 12:24, Waiman Long wrote:
> The commit 3fea5a499d57 ("mm: memcontrol: convert page
> cache to a new mem_cgroup_charge() API") introduced a bug in
> __add_to_page_cache_locked() causing the following splat:
>
> [ 1570.068330] page dumped because: VM_BUG_ON_PAGE(page_memcg(page))
> [
Hi all,
FIXME: Add owner of second tree to To:
Add author(s)/SOB of conflicting commits.
Today's linux-next merge of the pidfd tree got a conflict in:
security/integrity/ima/ima_main.c
between commits:
2b4a2474a202 ("IMA: generalize keyring specific measurement constructs")
Hi Kevin,
On 2021/1/22 14:38, Tian, Kevin wrote:
From: Lu Baolu
Sent: Thursday, January 21, 2021 9:45 AM
So that the uses could get chances to know what happened.
Suggested-by: Ashok Raj
Signed-off-by: Lu Baolu
---
drivers/iommu/intel/svm.c | 10 --
1 file changed, 8
On 2021/1/25 11:20, Baolin Wang wrote:
> We've already set the variable 'i' 's initial value before using it,
> thus remove redundant previous assignment of variable 'i'.
>
> Signed-off-by: Baolin Wang
> ---
> mm/filemap.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/mm/filemap.c
On Sun, 2021-01-24 at 12:56 +0800, Chun-Kuang Hu wrote:
> Hi, Chunfeng:
>
> Chun-Kuang Hu 於 2021年1月24日 週日 下午12:47寫道：
> >
> > Hi, Chunfeng:
> >
> > Chunfeng Yun 於 2021年1月22日 週五 下午8:04寫道：
> > >
> > > The compatilbe "mediatek,mt7623-mipi-tx" is not supported in driver,
> > > and in fact uses
From: Lina Iyer
Controllers may be in 'solver' state, where they could be in autonomous
mode executing low power modes for their hardware and as such are not
available for sending active votes. Device driver may notify RPMH
that the controller is in solver mode and when in such mode, disallow
On Sat, 2021-01-23 at 08:18 +0800, Chun-Kuang Hu wrote:
> Hi, Chunfeng:
>
> Chunfeng Yun 於 2021年1月22日 週五 下午8:04寫道：
> >
> > Add an optional "clock-names" property, it's not used to get the clock,
> > but some DTS files (e.g. mt8183) provide it.
>
> I think the logic is that we define property in
Thanks Doug for your comments.
On Fri, 22 Jan 2021 at 22:55, Doug Anderson wrote:
>
> Hi,
>
> On Fri, Jan 22, 2021 at 3:06 AM Sumit Garg wrote:
> >
> > Currently kdb uses in_interrupt() to determine whether its library
> > code has been called from the kgdb trap handler or from a saner calling
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
security/integrity/ima/ima_api.c
between commit:
2b4a2474a202 ("IMA: generalize keyring specific measurement constructs")
from the integrity tree and commit:
a2d2329e30e2 ("ima: handle idmapped mounts")
from the
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
fs/xfs/xfs_inode.c
between commit:
01ea173e103e ("xfs: fix up non-directory creation in SGID directories")
from the xfs tree and commit:
f736d93d76d3 ("xfs: support idmapped mounts")
from the pidfd tree.
I fixed it
Hi, Peter,
> -Original Message-
> From: Zhang, Rui
> Sent: Sunday, January 17, 2021 10:34 PM
> To: 'Peter Zijlstra'
> Cc: mi...@redhat.com; a...@kernel.org; mark.rutl...@arm.com;
> alexander.shish...@linux.intel.com; jo...@redhat.com;
> namhy...@kernel.org; linux-kernel@vger.kernel.org;
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
fs/overlayfs/inode.c
between commit:
9c09be9e71c4 ("ovl: perform vfs_getxattr() with mounter creds")
from the overlayfs tree and commit:
c7c7a1a18af4 ("xattr: handle idmapped mounts")
from the pidfd tree.
I fixed
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
fs/overlayfs/copy_up.c
between commit:
06896fa3193d ("ovl: skip getxattr of security labels")
from the overlayfs tree and commit:
c7c7a1a18af4 ("xattr: handle idmapped mounts")
from the pidfd tree.
I fixed it up
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
fs/namei.c
between commit:
e36cffed20a3 ("fs: make unlazy_walk() error handling consistent")
1e8f44f159b3 ("do_tmpfile(): don't mess with finish_open()")
from the vfs tree and commit:
47291baa8ddf ("namei: make
Long Term Reference (LTR) frames are the frames that are encoded
sometime in the past and stored in the DPB buffer list to be used
as reference to encode future frames.
This change adds controls to enable this feature.
Signed-off-by: Dikshita Agarwal
---
Add support for below LTR controls in encoder:
- V4L2_CID_MPEG_VIDEO_LTR_COUNT
- V4L2_CID_MPEG_VIDEO_FRAME_LTR_INDEX
- V4L2_CID_MPEG_VIDEO_USE_LTR_FRAMES
Signed-off-by: Dikshita Agarwal
---
drivers/media/platform/qcom/venus/venc_ctrls.c | 49 +-
1 file changed, 48
This renames all 'memhp' instances to 'mhp' except for memhp_default_state
for being a kernel command line option. This is just a clean up and should
not cause a functional change.
Cc: Greg Kroah-Hartman
Cc: "Rafael J. Wysocki"
Cc: Andrew Morton
Cc: linux...@kvack.org
Cc:
On 2021-01-24 11:13 p.m., Stephen Rothwell wrote:
Hi all,
After merging the scsi-mkp tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/scsi/sg.c: In function 'sg_find_srp_by_id':
drivers/scsi/sg.c:2908:4: error: expected '}' before 'else'
2908 |else
This series add the encoder controls for long term reference (LTR)
and support for the same in venus driver.
Dikshita Agarwal (2):
media: v4l2-ctrl: add controls for long term reference.
venus: venc: Add support for Long Term Reference (LTR) controls
A long-tail load balance cost is observed on the newly idle path,
this is caused by a race window between the first nr_running check
of the busiest runqueue and its nr_running recheck in detach_tasks.
Before the busiest runqueue is locked, the tasks on the busiest
runqueue could be pulled by
Hi Jiri,
On 1/24/2021 6:57 AM, Jiri Olsa wrote:
On Thu, Jan 21, 2021 at 12:21:36PM +0800, Jin, Yao wrote:
sNIP
mask = hashmap__new(pkg_id_hash, pkg_id_equal, NULL);
d = cpu_map__get_die(cpus, cpu, NULL).die;
key = (size_t)d << KEY_SHIFT | s; /* s is socket id */
if (hashmap__find(mask, (void
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
fs/f2fs/file.c
between commits:
19bb7075d1a9 ("f2fs: fix out-of-repair __setattr_copy()")
7cf2e6173b2d ("f2fs: enhance to update i_mode and acl atomically in
f2fs_setattr()")
from the f2fs tree and commit:
This series add the encoder controls for long term reference (LTR)
and support for the same in venus driver.
Dikshita Agarwal (2):
media: v4l2-ctrl: add controls for long term reference.
venus: venc: Add support for Long Term Reference (LTR) controls
On Sat, 23 Jan 2021 18:21:36 -0600
Jeremy Figgins wrote:
> Signed-off-by: Jeremy Figgins
> +++ b/drivers/usb/class/usblp.c
> + if (usblp->intf->num_altsetting > 1) {
Acked-by: Pete Zaitcev
I am having some misgivings about it, but let's see if it works.
At worst, someone will complain
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
fs/f2fs/acl.c
between commit:
7cf2e6173b2d ("f2fs: enhance to update i_mode and acl atomically in
f2fs_setattr()")
from the f2fs tree and commit:
e65ce2a50cf6 ("acl: handle idmapped mounts")
from the pidfd tree.
I
On Thu, 21 Jan 2021 at 18:27, Christian König wrote:
>
> I still have no idea what's going on here.
>
> The KASAN messages from the DC code are completely unrelated.
>
> Please add the full dmesg to your bug report.
>
I did it.
https://gitlab.freedesktop.org/drm/amd/-/issues/1439#note_776267
--
On 1/7/21 1:09 PM, Florian Fainelli wrote:
On 1/7/21 9:57 AM, Konrad Rzeszutek Wilk wrote:
On Fri, Jan 08, 2021 at 01:39:18AM +0800, Claire Chang wrote:
Hi Greg and Konrad,
This change is intended to be non-arch specific. Any arch that lacks DMA access
control and has devices not behind an
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
fs/ecryptfs/inode.c
between commit:
176cfe865da6 ("ecryptfs: fix uid translation for setxattr on
security.capability")
from the overlayfs tree and commit:
c7c7a1a18af4 ("xattr: handle idmapped mounts")
from the
On Sun, Jan 24, 2021 at 10:54:14PM +0300, Dmitry Osipenko wrote:
> From: Michał Mirosław
>
> Add ELAN KTF3624 touchscreen support to the elants_i2c driver.
> The eKTF3624 TS is found on a series of ASUS Transformer tablet devices,
> Nexus 7 tablet and etc. The firmware interface of eKTF3624 is
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
fs/coredump.c
between commit:
8a3cc755b138 ("coredump: don't bother with do_truncate()")
from the vfs tree and commit:
643fe55a0679 ("open: handle idmapped mounts in do_truncate()")
from the pidfd tree.
I fixed it
On Mon, Jan 25, 2021 at 8:06 AM David Rientjes wrote:
>
>
> On Sun, 17 Jan 2021, Muchun Song wrote:
>
> > Because we reuse the first tail vmemmap page frame and remap it
> > with read-only, we cannot set the PageHWPosion on a tail page.
> > So we can use the head[4].private to record the real
On Mon, Jan 25, 2021 at 12:09 PM Randy Dunlap wrote:
>
> On 1/24/21 8:06 PM, Muchun Song wrote:
> > On Mon, Jan 25, 2021 at 7:58 AM David Rientjes wrote:
> >>
> >>
> >> On Sun, 17 Jan 2021, Muchun Song wrote:
> >>
> >>> The HUGETLB_PAGE_FREE_VMEMMAP option is used to enable the freeing
> >>> of
There exists many build warnings when make M=samples/bpf on the Loongson
platform, this issue is MIPS related, x86 compiles just fine.
Here are some warnings:
CC samples/bpf/ibumad_user.o
samples/bpf/ibumad_user.c: In function ‘dump_counts’:
samples/bpf/ibumad_user.c:46:24: warning: format
In the rtl8366rb driver there are some jam tables which contain
undocumented values.
While trying to understand what these tables actually do,
I noticed a discrepancy in how one of those was treated.
Most of them were plain u16 arrays, while the ethernet one was
an u16 matrix.
By looking at the
I was trying to see if there were some Intel 8051 instructions in the
jam tables with Linus Walleij, when I noticed some oddities.
This patch's aim is to make the code more consistent and more similar
to the vendor's original source.
Link to the Realtek code the actual patch is based on:
[AMD Public Use]
The link error has been fixed by:
5da047444e82 drm/amd/display: fix 64-bit division issue on 32-bit OS
Regards,
Guchun
-Original Message-
From: amd-gfx On Behalf Of Randy Dunlap
Sent: Saturday, January 23, 2021 2:02 AM
To: Stephen Rothwell ; Linux Next Mailing List
On 1/25/21 12:29 PM, Dongsheng Yang wrote:
> commit ad0d9e76(bcache: use bio op accessors) makes the bi_opf
> modified by bio_set_op_attrs(). But there is a logical
> problem in this commit:
>
> trace_bcache_cache_insert(k);
> bch_keylist_push(>insert_keys);
>
> -
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 6ee1d745b7c9fd573fba142a2efdad76a9f1cb04
commit: 0c8d22fcae2f9590a07b000e1724f665820b77f7 Merge tag
'amd-drm-next-5.10-2020-09-03' of git://people.freedesktop.org/~agd5f/linux
into drm-next
date: 5
On 1/4/21 10:30 AM, David Lechner wrote:
This is the first step for adding support for the PRUSS on TI AM18XX/OMAP-L138
SoCs. This series adds support in the top-level PRUSS driver. (Patches for the
interrupt controller and individual PRUs are independent of this change and
will be submitted
Add device tree binding to support MT7530 GPIO controller.
Signed-off-by: DENG Qingfang
---
Changes v1 -> v2:
No changes.
Documentation/devicetree/bindings/net/dsa/mt7530.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/dsa/mt7530.txt
MT7530's LED controller can drive up to 15 LED/GPIOs.
Add support for GPIO control and allow users to use its GPIOs by
setting gpio-controller property in device tree.
Signed-off-by: DENG Qingfang
---
Changes v1 -> v2:
Set Output Enable after changing direction to output to avoid signal
MT7530's LED controller can be used as GPIO controller. Add support for
it.
DENG Qingfang (2):
dt-bindings: net: dsa: add MT7530 GPIO controller binding
net: dsa: mt7530: MT7530 optional GPIO support
.../devicetree/bindings/net/dsa/mt7530.txt| 6 +
drivers/net/dsa/mt7530.c
Reviewed-by: Alex Shi
在 2021/1/25 下午12:24, Waiman Long 写道:
> The commit 3fea5a499d57 ("mm: memcontrol: convert page
> cache to a new mem_cgroup_charge() API") introduced a bug in
> __add_to_page_cache_locked() causing the following splat:
>
> [ 1570.068330] page dumped because:
From: Hou Zhiqiang
In the dw_pcie_ep_init(), it depends on the detected iATU region
numbers to allocate the in/outbound window management bit map.
It fails after the commit 281f1f99cf3a ("PCI: dwc: Detect number
of iATU windows").
So this patch move the iATU region detection into a new
commit ad0d9e76(bcache: use bio op accessors) makes the bi_opf
modified by bio_set_op_attrs(). But there is a logical
problem in this commit:
trace_bcache_cache_insert(k);
bch_keylist_push(>insert_keys);
- n->bi_rw |= REQ_WRITE;
+
On Fri, 22 Jan 2021, shuo.a@intel.com wrote:
From: Shuo Liu
An I/O request of a User VM, which is constructed by the hypervisor, is
distributed by the ACRN Hypervisor Service Module to an I/O client
corresponding to the address range of the I/O request.
For each User VM, there is a
On Sun, Jan 24, 2021 at 11:24:41PM -0500, Waiman Long wrote:
> diff --git a/mm/filemap.c b/mm/filemap.c
> index 5c9d564317a5..aa0e0fb04670 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -835,6 +835,7 @@ noinline int __add_to_page_cache_locked(struct page *page,
> XA_STATE(xas,
Hi Suman, Mathieu,
On 1/7/21 2:49 PM, Suman Anna wrote:
On 1/7/21 4:44 PM, Mathieu Poirier wrote:
On Wed, Jan 06, 2021 at 06:03:25PM -0600, Suman Anna wrote:
Hi Mathieu,
[...]
I only see input from Andy and Lars in the thread you point out, nothing from
Greg. I have also taken a look at
On Fri, Jan 22, 2021 at 11:00:22PM +0800, Colin King wrote:
> From: Colin Ian King
>
> Currently the ! operator is incorrectly being used to flip bits on
> mask values. Fix this by using the bit-wise ~ operator instead.
>
> Addresses-Coverity: ("Logical vs. bitwise operator")
> Fixes:
On 1/19/21 5:33 AM, Pan Bian wrote:
> Free the request rq before returning error code.
Applied, thanks.
--
Jens Axboe
On 1/17/21 1:50 AM, Dinghao Liu wrote:
> Once we have called device_initialize(), we should use put_device() to
> give up the reference on error, just like what we have done on failure
> of device_add().
Applied for 5.11, thanks.
--
Jens Axboe
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-...@vger.kernel.org
Cc: linux...@kvack.org
Cc: Andrew
On 2021/1/22 21:22, Vincent Guittot wrote:
> On Fri, 22 Jan 2021 at 11:14, Mel Gorman wrote:
>>
>> On Fri, Jan 22, 2021 at 10:30:52AM +0100, Vincent Guittot wrote:
>>> Hi Mel,
>>>
>>> On Tue, 19 Jan 2021 at 13:02, Mel Gorman
>>> wrote:
On Tue, Jan 19, 2021 at 12:33:04PM +0100, Vincent
On Fri, Jan 22, 2021 at 02:05:47PM +0100, Jann Horn wrote:
> On Thu, Jan 21, 2021 at 7:19 PM Vlastimil Babka wrote:
> > On 1/21/21 11:01 AM, Christoph Lameter wrote:
> > > On Thu, 21 Jan 2021, Bharata B Rao wrote:
> > >
> > >> > The problem is that calculate_order() is called a number of times
>
On 1/23/21 1:10 PM, Sebastian Andrzej Siewior wrote:
> Patch 2+3 were applied and then dropped by Jens due to a NOHZ+softirq
> related warning [0]. Turns out a successful wakeup via
> set_nr_if_polling() will not process any softirqs and the CPU may go
> back to idle. This is addressed by patch
On Wed, Jan 20, 2021 at 4:08 PM Yong Wu wrote:
>
> On Wed, 2021-01-20 at 13:15 +0900, Tomasz Figa wrote:
> > On Wed, Jan 13, 2021 at 3:45 PM Yong Wu wrote:
> > >
> > > On Wed, 2021-01-13 at 14:30 +0900, Tomasz Figa wrote:
> > > > On Thu, Dec 24, 2020 at 8:35 PM Yong Wu wrote:
> > > > >
> > > >
The commit 3fea5a499d57 ("mm: memcontrol: convert page
cache to a new mem_cgroup_charge() API") introduced a bug in
__add_to_page_cache_locked() causing the following splat:
[ 1570.068330] page dumped because: VM_BUG_ON_PAGE(page_memcg(page))
[ 1570.068333] pages's memcg:8889a4116000
[
On Mon, 2021-01-25 at 11:24 +0800, Nicolas Boichat wrote:
> On Mon, Jan 25, 2021 at 11:15 AM Hailong Fan wrote:
> >
> > When flipping the polarity will be generated interrupt under certain
> > circumstances, but GPIO external signal has not changed.
> > Then, mask the interrupt before polarity
When flipping the polarity will be generated interrupt under certain
circumstances, but GPIO external signal has not changed.
Then, mask the interrupt before polarity setting, and clear the
unexpected interrupt after trigger type setting completed.
Remove mtk_eint_flip_edge: because
On Thu, 14 Jan 2021, at 23:46, Chia-Wei, Wang wrote:
> Add check against LPC device v2 compatible string to
> ensure that the fixed device tree layout is adopted.
> The LPC register offsets are also fixed accordingly.
>
> Signed-off-by: Chia-Wei, Wang
> ---
>
On Thu, 14 Jan 2021, at 23:46, Chia-Wei, Wang wrote:
> The LPC controller has no concept of the BMC and the Host partitions.
>
> A concrete instance is that the HICRB[5:4] are for the I/O port address
> configurtaion of KCS channel 1/2. However, the KCS driver cannot access
> HICRB for channel
Hi all,
After merging the scsi-mkp tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/scsi/sg.c: In function 'sg_find_srp_by_id':
drivers/scsi/sg.c:2908:4: error: expected '}' before 'else'
2908 |else
|^~~~
drivers/scsi/sg.c:2902:16: warning: unused
On Thu, 14 Jan 2021, at 23:46, Chia-Wei, Wang wrote:
> Add check against LPC device v2 compatible string to
> ensure that the fixed device tree layout is adopted.
> The LPC register offsets are also fixed accordingly.
>
> Signed-off-by: Chia-Wei, Wang
Using a Witherspoon (AST2500):
On 20:06 Sun 24 Jan 2021, Guenter Roeck wrote:
On 1/24/21 7:56 PM, Bhaskar Chowdhury wrote:
On 19:48 Sun 24 Jan 2021, Guenter Roeck wrote:
On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote:
So this rc looked fairly calm and small, all the way up until today.
In fact, over 40% of
On 1/24/21 8:06 PM, Muchun Song wrote:
> On Mon, Jan 25, 2021 at 7:58 AM David Rientjes wrote:
>>
>>
>> On Sun, 17 Jan 2021, Muchun Song wrote:
>>
>>> The HUGETLB_PAGE_FREE_VMEMMAP option is used to enable the freeing
>>> of unnecessary vmemmap associated with HugeTLB pages. The config
>>> option
On Mon, Jan 25, 2021 at 7:58 AM David Rientjes wrote:
>
>
> On Sun, 17 Jan 2021, Muchun Song wrote:
>
> > The HUGETLB_PAGE_FREE_VMEMMAP option is used to enable the freeing
> > of unnecessary vmemmap associated with HugeTLB pages. The config
> > option is introduced early so that supporting code
On 1/24/21 7:56 PM, Bhaskar Chowdhury wrote:
> On 19:48 Sun 24 Jan 2021, Guenter Roeck wrote:
>> On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote:
>>> So this rc looked fairly calm and small, all the way up until today.
>>>
>>> In fact, over 40% of the non-merge commits came in
Hi all,
Today's linux-next merge of the scsi-mkp tree got a conflict in:
drivers/scsi/gdth.c
between commit:
537896fabed1 ("kbuild: give the SUBLEVEL more room in KERNEL_VERSION")
from the kbuild tree and commit:
0653c358d2dc ("scsi: Drop gdth driver")
from the scsi-mkp tree.
I fixed
From: Zqiang
Due to kworker also is kernel thread, it's already included
PF_KTHREAD mask, so remove PF_WQ_WORKER mask.
Signed-off-by: Zqiang
---
kernel/power/process.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/power/process.c b/kernel/power/process.c
index
1 - 100 of 499 matches
Mail list logo
