Do we really need a new source file just to call swiotlb_init? And
if we do that file should have a SPDX header these days.
Otherwise looks fine:
Reviewed-by: Christoph Hellwig
Hi Baolin,
On Wed, Nov 7, 2018 at 6:43 AM Baolin Wang wrote:
> We will meet below issue due to mutex_lock() is called in interrupt context.
> The mutex lock is used to protect the pattern trigger data, but before
> changing
> new pattern trigger data (pattern values or repeat value) by users, we
On Wed, Nov 07, 2018 at 12:08:23AM +, Maciej W. Rozycki wrote:
> The Broadcom SiByte BCM1250, BCM1125H and BCM1125 SOCs have an onchip
> 32-bit PCI host bridge, and the two former SOCs also have an onchip HT
> host bridge. The HT host bridge, where present, appears in the PCI
> configuratio
On Wed, 2018-11-07 at 08:35 +0100, Michal Hocko wrote:
> On Wed 07-11-18 07:35:18, Balbir Singh wrote:
> > The check seems to be quite aggressive and in a loop that iterates
> > pages, but has nothing to do with the page, did you mean to make
> > the check
> >
> > zone_idx(page_zone(page)) == ZONE
syzbot has found a reproducer for the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=169e982540
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c
On Wed 07-11-18 08:35:48, Michal Hocko wrote:
> On Wed 07-11-18 07:35:18, Balbir Singh wrote:
> > On Tue, Nov 06, 2018 at 10:55:24AM +0100, Michal Hocko wrote:
> > > From: Michal Hocko
> > >
> > > Page state checks are racy. Under a heavy memory workload (e.g. stress
> > > -m 200 -t 2h) it is qui
On Wed 07-11-18 07:35:18, Balbir Singh wrote:
> On Tue, Nov 06, 2018 at 10:55:24AM +0100, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > Page state checks are racy. Under a heavy memory workload (e.g. stress
> > -m 200 -t 2h) it is quite easy to hit a race window when the page is
> > allocate
Hi Boris and Geert
On Tue, Nov 6, 2018 at 11:34 PM Boris Brezillon
wrote:
>
> On Tue, 6 Nov 2018 23:19:14 +0100
> Geert Uytterhoeven wrote:
>
> > Hi Boris,
> >
> > On Tue, Nov 6, 2018 at 10:58 PM Boris Brezillon
> > wrote:
> > > On Tue, 6 Nov 2018 22:44:16 +0100
> > > Geert Uytterhoeven wrote
Add the HXT vendor ID to pci_ids.h and use it in quirks. As the
design of HXT SD4800 ACS feature is the same as QCOM QDF2xxx,
pci_quirk_qcom_rp_acs() is reused for SD4800 quirk.
cc: Joey Zheng
Reviewed-by: Sinan Kaya
Signed-off-by: Shunyong Yang
---
v2:
Add Reviewed-by: Sinan Kaya.
v1:
In
The HXT SD4800 PCI controller does not set the Command Completed
bit unless writes to the Slot Command register change "Control"
bits.
This patch adds SD4800 to the quirk.
Cc: Joey Zheng
Signed-off-by: Shunyong Yang
diff --git a/drivers/pci/hotplug/pciehp_hpc.c b/drivers/pci/hotplug/pciehp_hpc
Hi Jacek,
On 7 November 2018 at 06:07, Jacek Anaszewski
wrote:
> Switch to using generic LED support for composing LED class
> device name.
>
> Signed-off-by: Jacek Anaszewski
> Cc: Xiaotong Lu
> Cc: Baolin Wang
Thanks for simplifying the code, it can work well for SC27XX LED.
Tested-by: Baol
Hi Jacek,
On 7 November 2018 at 06:07, Jacek Anaszewski
wrote:
> Add public led_compose_name() API for composing LED class device
> name basing on fwnode_handle data. The function composes device name
> according to either a new pattern or the legacy
> pattern. The decision on using the
> parti
This fixes the following warning:
kernel/cgroup/cpuset.c: In function ‘cpuset_cancel_attach’:
kernel/cgroup/cpuset.c:1501:17: warning: variable ‘cs’ set but not used
[-Wunused-but-set-variable]
struct cpuset *cs;
^
Signed-off-by: Yi Wang
---
kernel/cgroup/cpuset.c | 2 --
1 f
Use git commit description style 'commit <12+ chars of sha1>
("")' in the comments.
Signed-off-by: Peng Hao
---
arch/arm64/kernel/sys32.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/kernel/sys32.c b/arch/arm64/kernel/sys32.c
index 0f8bcb7..8317a5a 100644
--
This updates dt-binding documentation for MT7629 SoC
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/watchdog/mtk-wdt.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/watchdog/mtk-wdt.txt
b/Documentation/devicetree/bindings/watchdog/mtk-wd
This updates bindings for MT7629 RNG driver.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/rng/mtk-rng.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/rng/mtk-rng.txt
b/Documentation/devicetree/bindings/rng/mtk-rng.txt
Hi Nylon,
Nylon Chen 於 2018年11月7日 週三 下午1:32寫道：
>
> The "fpu_dp" should be added to hwcap_str table to make sure the cpu features
> displayed correctly.
>
> Signed-off-by: Nylon Chen
> ---
> arch/nds32/kernel/setup.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/nds32/kernel/setu
On 06.11.2018 11:43, Arun KS wrote:
On 2018-11-06 14:07, Konstantin Khlebnikov wrote:
On 06.11.2018 11:30, Arun KS wrote:
On 2018-11-06 13:47, Konstantin Khlebnikov wrote:
On 06.11.2018 8:38, Arun KS wrote:
Any comments?
Looks good.
Except unclear motivation behind this change.
This should
Hi Jacek,
On 7 November 2018 at 06:07, Jacek Anaszewski
wrote:
> Replace of_led_classdev_register() with led_classdev_register_ext(), which
> accepts easily extendable struct led_init_data, instead of the fixed
> struct device_node argument. The latter can be now passed in a fwnode
> property of
Thanks Srinivas for the fix.
On 11/6/2018 5:08 PM, Srinivas Kandagatla wrote:
For some reason the dapm widgets are incorrectly defined from the start,
Not sure how we ended up with such thing. Fix them now!
Without this fix the backend dais are always powered up even if there
is no active stre
On 2018-11-07 02:17, Andy Lutomirski wrote:
On Tue, Nov 6, 2018 at 4:02 PM Sean Christopherson
wrote:
/*
* EEXIT or EENTER faulted. In the latter case, %RAX already holds some
* fault indicator, e.g. -EFAULT.
*/
eexit_or_eenter_fault:
ret
But userspace wants to know whether it wa
On 11/6/18 12:41 PM, Dave Chinner wrote:
> On Tue, Nov 06, 2018 at 12:00:06PM +0100, Jan Kara wrote:
>> On Tue 06-11-18 13:47:15, Dave Chinner wrote:
>>> On Mon, Nov 05, 2018 at 04:26:04PM -0800, John Hubbard wrote:
On 11/5/18 1:54 AM, Jan Kara wrote:
> Hmm, have you tried larger buffer si
On 11/7/18 12:15 AM, Andrew Morton wrote:
> On Tue, 6 Nov 2018 14:20:53 +0200 Alexey Skidanov
> wrote:
>
>> On success, gen_pool_first_fit_align() returns the bit number such that
>> chunk_start_addr + (bit << order) is properly aligned. On failure,
>> the bitmap size parameter is returned.
On 2018-11-07 01:38, Michal Hocko wrote:
On Tue 06-11-18 21:01:29, Arun KS wrote:
On 2018-11-06 19:36, Michal Hocko wrote:
> On Tue 06-11-18 11:33:13, Arun KS wrote:
> > When free pages are done with higher order, time spend on
> > coalescing pages by buddy allocator can be reduced. With
> > sec
On 2018-11-07 05:52, Andrew Morton wrote:
On Fri, 26 Oct 2018 16:30:58 +0530 Arun KS
wrote:
This series convert totalram_pages, totalhigh_pages and
zone->managed_pages to atomic variables.
The whole point appears to be removal of managed_page_count_lock, yes?
Why? What is the value of thi
On 11/7/18 12:11 AM, Andrew Morton wrote:
> On Tue, 6 Nov 2018 14:20:53 +0200 Alexey Skidanov
> wrote:
>
>> On success, gen_pool_first_fit_align() returns the bit number such that
>> chunk_start_addr + (bit << order) is properly aligned. On failure,
>> the bitmap size parameter is returned.
On 11/06/2018 08:31 PM, Roberto Sassu wrote:
This patch removes the hard-coded limit of the active_banks array size.
The hard-coded limit in static array active_banks[] represents the
maximum possible banks.
A TPM might have three banks, but only one bank may be active.
To confirm my und
Hi Vitaly:
Thanks for your review.
On 11/6/2018 11:50 PM, Vitaly Kuznetsov wrote:
ltyker...@gmail.com writes:
From: Lan Tianyu
This patch is to initialize ept_pointer to INVALID_PAGE and check it
before flushing ept tlb. If ept_pointer is invalidated, bypass the flush
request.
Signe
On Sun, Oct 28, 2018 at 11:24 PM Amit Kucheria wrote:
>
> On Thu, Oct 25, 2018 at 9:38 PM Andy Gross wrote:
> >
> > On Thu, Oct 25, 2018 at 10:55:32AM +0530, Amit Kucheria wrote:
> >
> >
> >
> > > Andy,
> > >
> > > While you acked the tsens thermal DT patches[1] so they could go
> > > through th
From: Jiri Olsa
Date: Tue, 6 Nov 2018 21:42:55 +0100
> I pushed that fix in perf/fixes branch, but I'm still occasionaly
> hitting the namespace crash.. working on it ;-)
Jiri, how can this new scheme work without setting copy_on_queue
for the queued_events we use here?
I don't see copy_on_queu
Hi,
Since 37c8a5fafa3bb7dcdd51774be353be6cb2912b86 [kbuild: consolidate
Devicetree dtb build rules], the target bindeb-pkg no longer installs
DTBs in the .deb package.
Thanks,
Nuno
There was a special path in handle_userfault() in the past that we'll
return a VM_FAULT_NOPAGE when we detected non-fatal signals when waiting
for userfault handling. We did that by reacquiring the mmap_sem before
returning. However that brings a risk in that the vmas might have
changed when we r
This is the gup counterpart of the change that allows the VM_FAULT_RETRY
to happen for more than once.
Signed-off-by: Peter Xu
---
mm/gup.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/mm/gup.c b/mm/gup.c
index 6faff46cd409..8a0e7f9bd29a 100644
--- a/mm/
(sorry I got the cc list messed up; am sending another one with no
change but only to fix the cc list)
This is an RFC series as cleanup and enhancements to current page
fault logic. The whole idea comes from the discussion between Andrea
and Linus on the bug reported by syzbot here:
https://l
The idea comes from a discussion between Linus and Andrea [1].
Before this patch we only allow a page fault to retry once. We achieved
this by clearing the FAULT_FLAG_ALLOW_RETRY flag when doing
handle_mm_fault() the second time. This was majorly used to avoid
unexpected starvation of the system
There's plenty of places around __get_user_pages() that has a parameter
"nonblocking" which does not really mean that "it won't block" (because
it can really block) but instead it shows whether the mmap_sem is
released by up_read() during the page fault handling mostly when
VM_FAULT_RETRY is return
We will meet below issue due to mutex_lock() is called in interrupt context.
The mutex lock is used to protect the pattern trigger data, but before changing
new pattern trigger data (pattern values or repeat value) by users, we always
cancel the timer firstly to clear previous patterns' performance
From: Hou Zhiqiang
Removed the wrong compatible string "snps,dw-pcie", in case
match incorrect driver.
Signed-off-by: Hou Zhiqiang
---
V3:
- Reworded the subject.
arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 2 +-
arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 6 +++---
arch/arm64/bo
From: Hou Zhiqiang
Removed the compatible string "snps,dw-pcie", it is for the reference
platform driver for PCI RC IP Protoyping Kits based on the ARC SDP,
so it is not suitable for all platform with designware PCIe controller,
and platform vendors have themselves' drivers.
The compatible strin
From: Hou Zhiqiang
Removed the wrong compatible string "snps,dw-pcie", in case
match incorrect driver.
Signed-off-by: Hou Zhiqiang
---
V3:
- Reworded the subject.
arch/arm/boot/dts/ls1021a.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/ls1021a.
From: Hou Zhiqiang
Removed the compatible string "snps,dw-pcie" from FSL layerscape-pci compatible
string list.
Hou Zhiqiang (4):
dt-bindings: pci: layerscape-pci: add compatible strings
"fsl,ls1043a-pcie"
dt-bindings: pci: layerscape-pci: removed compatible string
"snps,dw-pcie"
A
From: Hou Zhiqiang
The PCIe compatible string for LS1043A was lost, so add it.
Signed-off-by: Hou Zhiqiang
Reviewed-by: Rob Herring
---
V3:
- no change
Documentation/devicetree/bindings/pci/layerscape-pci.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindi
The "fpu_dp" should be added to hwcap_str table to make sure the cpu features
displayed correctly.
Signed-off-by: Nylon Chen
---
arch/nds32/kernel/setup.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/nds32/kernel/setup.c b/arch/nds32/kernel/setup.c
index eacc79024879..e39274a21481 1
We add a config for user to enable or disable this feature.
It can be used to control the hardware prefetch function.
Signed-off-by: Nylon Chen
---
arch/nds32/Kconfig.cpu| 7 +++
arch/nds32/include/asm/bitfield.h | 6 ++
arch/nds32/kernel/head.S | 2 +-
arch/nds32/ke
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1103882b40
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
dashb
Current imx7d-sdb.dts has some incorrect settings about
Rev-A and Rev-B boards, some of the settings are based on
Rev-A board but some are based on Rev-B board, clean up it
by adding i.MX7D SDB Rev-A board support, make default
imx7d-sdb.dts for Rev-B board as usual, and introduce
imx7d-sdb-reva.dt
From: Hou Zhiqiang
The order of parameters is not correct when invoking the outbound
window disable routine.
Fixes: commit 4a2745d760fac ("PCI: layerscape: Disable outbound
windows configured by bootloader").
Cc: sta...@vger.kernel.org
Signed-off-by: Hou Zhiqiang
---
V2:
- Tagged this patch f
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14aa485d40
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
dashb
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16e42f5b40
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
dashb
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10ae982540
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
dashb
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1594d98340
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
dashb
Fix this by using a 'stdout-path' property that points to the device.
Fixes: 0b6286dd96c0 ("arm64: dts: mt7622: add bananapi BPI-R64 board")
Cc: sta...@vger.kernel.org
Signed-off-by: Ryder Lee
---
arch/arm64/boot/dts/mediatek/mt7622-bananapi-bpi-r64.dts | 7 ++-
1 file changed, 6 insertions(
The issue was introduced by Kernel CI:
https://kernelci.org/boot/id/5bbdcbad59b5146fc5b43592/
Fix this by using a 'stdout-path' property that points to the device.
Fixes: c0d9f9ad4f76 ("arm64: dts: mt7622: add earlycon to mt7622-rfb1 board")
Cc: sta...@vger.kernel.org
Signed-off-by: Ryder Lee
--
On Mon, Nov 5, 2018 at 1:19 AM Pavel Machek wrote:
> Plus, I don't think "100% charge" is right test for "battery full". At
> least on thinkpads, there's configuration option, and it is common
> _not_ to charge batterry above 95% or so (to increase its lifetime).
Hans also touched on this area in
Hi Bjorn,
Thanks a lot for your guide!
I'll tag it for stable in v2.
Thanks,
Zhiqiang
> -Original Message-
> From: Bjorn Helgaas
> Sent: 2018年10月30日 0:31
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> bhelg...@google.com; lorenzo.pieral...@arm.com; Roy
Hi Heikki,
url:
https://github.com/0day-ci/linux/commits/Heikki-Krogerus/device-property-Introducing-software-nodes/20181106-031310
smatch warnings:
drivers/base/swnode.c:391 fwnode_create_software_node() error: dereferencing
freed memory 'swnode'
#
https://github.com/0day-ci/li
The voltage range (min, max) provided in the device tree is from
the data manual and is pretty big, catering to a wide range of devices.
On a i2c read/write failure the regulator_set_voltage_triplet function
falls back to set voltage between min and max. The min value from Device
Tree can be lesser
_get_optimal_vdd_voltage call provides new_supply_vbb->u_volt
as the reference voltage while it should be really new_supply_vdd->u_volt.
Fixes: 9a835fa6e47 ("PM / OPP: Add ti-opp-supply driver")
Signed-off-by: Keerthy
---
drivers/opp/ti-opp-supply.c | 2 +-
1 file changed, 1 insertion(+), 1 dele
The series brings in couple of fixes to the ti-opp-supply driver.
One of them updates u_volt_min dynamically and avoids hang due
to lesser static u_volt_min and the other fixes the supply in
_get_optimal_vdd_voltage.
Keerthy (2):
power: opp: ti-opp-supply: Dynamically update u_volt_min
power:
Hi Leo,
Thanks a lot for your comments!
> -Original Message-
> From: Li Yang
> Sent: 2018年10月27日 5:01
> To: Z.q. Hou
> Cc: moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE
> ; lkml ;
> linux-...@vger.kernel.org; open list:OPEN FIRMWARE AND FLATTENED
> DEVICE TREE BINDINGS ; Rob H
Hi Leo,
Thanks a lot for your comments!
> -Original Message-
> From: Li Yang
> Sent: 2018年10月27日 4:58
> To: Z.q. Hou
> Cc: moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE
> ; lkml ;
> linux-...@vger.kernel.org; open list:OPEN FIRMWARE AND FLATTENED
> DEVICE TREE BINDINGS ; Rob H
1/ discard 'struct unx_cred'. We don't need any data that
is not already in 'struct rpc_cred'.
2/ Don't keep these creds in a hash table. When a credential
is needed, simply allocate it. When not needed, discard it.
This can easily be faster than performing a lookup on
a shared hash
This now always just does get_rpccred(), so we
don't need an operation pointer to know to do that.
Signed-off-by: NeilBrown
---
include/linux/sunrpc/auth.h|2 --
net/sunrpc/auth.c | 12 +---
net/sunrpc/auth_gss/auth_gss.c |2 --
net/sunrpc/auth_null.c |
SUNRPC has two sorts of credentials, both of which appear as
"struct rpc_cred".
There are "generic credentials" which are supplied by clients
such as NFS and passed in 'struct rpc_message' to indicate
which user should be used to authorize the request, and there
are low-level credentials such as AU
Just use ->cr_cred->fsuid directly.
Signed-off-by: NeilBrown
---
include/linux/sunrpc/auth.h|2 --
net/sunrpc/auth.c |1 -
net/sunrpc/auth_gss/auth_gss.c | 12 ++--
3 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/include/linux/sunrpc/auth.h b/inc
This is no longer used.
Signed-off-by: NeilBrown
---
include/linux/sunrpc/auth.h |6 -
net/sunrpc/Makefile |2
net/sunrpc/auth.c | 18
net/sunrpc/auth_generic.c | 199 ---
net/sunrpc/auth_null.c |2
5 files ch
The credential passed in rpc_message.rpc_cred is always a
generic credential except in one instance.
When gss_destroying_context() calls rpc_call_null(), it passes
a specific credential that it needs to destroy.
In this case the RPC acts *on* the credential rather than
being authorized by it.
This
When NFS creates a machine credential, it is a "generic" credential,
not tied to any auth protocol, and is really just a container for
the princpal name.
This doesn't get linked to a genuine credential until rpcauth_bindcred()
is called.
The lookup always succeeds, so various places that test if th
Rather than keying the access cache with 'struct rpc_cred',
use 'struct cred'. Then use cred_fscmp() to compare
credentials rather than comparing the raw pointer.
A benefit of this approach is that in the common case we avoid the
rpc_lookup_cred_nonblock() call which can be slow when the cred cac
This is no longer used.
Signed-off-by: NeilBrown
---
include/linux/sunrpc/auth.h |3 ---
net/sunrpc/auth_null.c |1 -
net/sunrpc/auth_unix.c |1 -
3 files changed, 5 deletions(-)
diff --git a/include/linux/sunrpc/auth.h b/include/linux/sunrpc/auth.h
index 0bdc2f4957ff..d8c
NFS needs to know when a credential is about to expire so that
it can modify write-back behaviour to finish the write inside the
expiry time.
It currently uses functions in SUNRPC code which make use of a
fairly complex callback scheme and flags in the generic credientials.
As I am working to disc
Use the common 'struct cred' to pass credentials for readdir.
Signed-off-by: NeilBrown
---
fs/nfs/dir.c| 15 +--
fs/nfs/nfs3proc.c | 11 +--
fs/nfs/nfs4proc.c | 13 ++---
fs/nfs/proc.c | 11 +--
include/linux/nfs_fs.h
In almost all cases the credential stored in rpc_message.rpc_cred
is a "generic" credential. One of the two expections is when an
AUTH_NULL credential is used such as for RPC ping requests.
To improve consistency, don't pass an explicit credential in
these cases, but instead pass NULL and set a t
Use cred->fsuid and cred->fsgid instead.
Signed-off-by: NeilBrown
---
fs/nfs/flexfilelayout/flexfilelayout.c | 14 --
fs/nfsd/nfs4callback.c |6 ++
include/linux/sunrpc/auth.h|3 ---
net/sunrpc/auth.c |6 +-
net/s
it is never used.
Signed-off-by: NeilBrown
---
include/linux/sunrpc/sched.h |1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/sunrpc/sched.h b/include/linux/sunrpc/sched.h
index 7b540c066594..f542dad8d4ab 100644
--- a/include/linux/sunrpc/sched.h
+++ b/include/linux/sunrpc/sche
This lock is no longer necessary.
If nfs4_get_renew_cred() needs to hunt through the open-state
creds for a user cred, it still takes the lock to stablize
the rbtree, but otherwise there are no races.
Note that this completely removes the lock from nfs4_renew_state().
It appears that the original
NFSv4 state management tries a root credential when no machine
credential is available, as can happen with kerberos.
It does this by replacing the cl_machine_cred with a root credential.
This means that any user of the machine credential needs to take
a lock while getting a reference to the machine
We can use cred->groupinfo (from the 'struct cred') instead.
Signed-off-by: NeilBrown
---
fs/nfs/flexfilelayout/flexfilelayout.c | 14 +-
include/linux/sunrpc/auth.h|1 -
net/sunrpc/auth.c |1 -
net/sunrpc/auth_generic.c | 17
The SUNRPC credential framework was put together before
Linux has 'struct cred'. Now that we have it, it makes sense to
use it.
This first step just includes a suitable 'struct cred *' pointer
in every 'struct auth_cred' and almost every 'struct rpc_cred'.
The rpc_cred used for auth_null has a NU
The cred is a machine_cred iff ->principal is set, so there is no
need for the extra flag.
There is one case which deserves some
explanation. nfs4_root_machine_cred() calls rpc_lookup_machine_cred()
with a NULL principal name which results in not getting a machine
credential, but getting a root cr
Sometimes we want to opportunistically get a
ref to a cred in an rcu_read_lock protected section.
get_task_cred() does this, and NFS does as similar thing
with its own credential structures.
To prepare for NFS converting to use 'struct cred' more
uniformly, define get_cred_rcu(), and use it in
get_
This is an updated version of a series I sent in Feb of this year.
Since then there have only been minor improvement and updates to sync
with the changing kernel.
There doesn't seem to be a maintainer for the 'cred' code, so I don't
know who to ask to approve the first 4 patches. Maybe if the NFS
It is common practice for helpers like this to silently,
accept a NULL pointer.
get_rpccred() and put_rpccred() used by NFS act this way
and using the same interface will ease the conversion
for NFS, and simplify the resulting code.
Signed-off-by: NeilBrown
---
include/linux/cred.h | 14 ++
NFS needs to compare to credentials, to see if they can
be treated the same w.r.t. filesystem access. Sometimes
an ordering is needed when credentials are used as a key
to an rbtree.
NFS currently has its own private credential management from
before 'struct cred' existed. To move it over to more
There is no reason that modules should not be able
to use this, and NFS will need it when converted to
use 'struct cred'.
Signed-off-by: NeilBrown
---
kernel/cred.c |1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/cred.c b/kernel/cred.c
index ba60162249e8..21f4a97085b4 100644
--- a/
On Tue, Nov 6, 2018 at 6:58 PM Christian Kujau wrote:
> FWIW, the issue I reported back in 2013[0] was not an ill-configured NFS
> export, but a read-only NFS export (and then a read-write exported NFS
> export, but the user compiling the kernel did not have write permission)
> and so "test -w .gi
Add a "invert-pwm" device-tree property to allow hardware designs to use
inverted logic on the PWM output. We intentionally preserve the invert
PWM output bit if the property is not found to allow for
bootloaders/bios which may have configured this earlier.
Signed-off-by: Chris Packham
---
drive
With the addition of the invert-pwm property the adt7475 needs its own
binding documentation rather being captured under trivial-devices.txt.
Signed-off-by: Chris Packham
---
.../devicetree/bindings/hwmon/adt7475.txt | 22 +++
.../devicetree/bindings/trivial-devices.txt |
PTRACE_GET_SYSCALL_INFO lets ptracer obtain details of the syscall
the tracee is blocked in. The request returns meaningful data only
when the tracee is in a syscall-enter-stop or a syscall-exit-stop.
There are two reasons for a special syscall-related ptrace request.
Firstly, with the current pt
On Fri, Nov 02, 2018 at 10:55:16AM +0800, Leo Yan wrote:
> Hi all,
>
> Now I found that if use the command 'perf script' for Arm CoreSight trace
> data, it fails to parse kernel symbols if we don't specify kernel vmlinux
> file. So when we don't specify kernel symbol files then perf tool will
>
On Tue, 06 Nov 2018, Andrew Morton wrote:
It would be interesting to know precisely which stat fields the
database-which-shall-not-be-named is looking for. Then we could cook
up a very whizzy way of getting at the info.
The ctxt field, afaik. In any case they have been able to work around
the
This fixes the following warnings:
arch/x86/kernel/irq.c:270:28: warning: no previous prototype for
‘smp_x86_platform_ipi’ [-Wmissing-prototypes]
__visible void __irq_entry smp_x86_platform_ipi(struct pt_regs *regs)
^
arch/x86/kernel/irq.c:301:16: warning: no previous
Hi Geert,
On 6 November 2018 at 23:57, Geert Uytterhoeven wrote:
> Hi Baolin,
>
> On Tue, Oct 2, 2018 at 6:39 PM Baolin Wang wrote:
>> This patch adds one new led trigger that LED device can configure
>> the software or hardware pattern and trigger it.
>>
>> Consumers can write 'pattern' file to
Hi Mathieu,
On Mon, Nov 05, 2018 at 03:26:30PM -0700, Mathieu Poirier wrote:
> This patch deals with the release of the CLAIM tag when the ETM is
> operated from perf. Otherwise the tag is left asserted and subsequent
> requests to use the device fail.
>
> Signed-off-by: Mathieu Poirier
> ---
>
On Fri, 2018-11-02 at 14:36 +0800, Ryder Lee wrote:
> On Thu, 2018-10-18 at 11:23 +0800, Honghui Zhang (张洪辉) wrote:
> > From: Honghui Zhang
> >
> > Use the devm_of_pci_get_host_bridge_resources() API in place of the PCI OF
> > DT parser.
> >
> > Signed-off-by: Honghui Zhang
> > ---
> > drivers
Hi all,
Changes since 20181106:
New trees: slimbus, nvmem
The tip tree still had its build failure for which I applied a fix patch.
Non-merge commits (relative to Linus' tree): 1408
1540 files changed, 69938 insertions(+), 65849 dele
On 11/6/18 6:58 PM, Christian Kujau wrote:
On Tue, 6 Nov 2018, Brian Norris wrote:
Perhaps both scenarios could be satisfied by having
scripts/setlocalversion first check if .git has write permissions, and
acting accordingly. Looking into history, this actually used to be
done, but cdf2bc632ebc
On Tue, 6 Nov 2018, Brian Norris wrote:
> > Perhaps both scenarios could be satisfied by having
> > scripts/setlocalversion first check if .git has write permissions, and
> > acting accordingly. Looking into history, this actually used to be
> > done, but cdf2bc632ebc ("scripts/setlocalversion on w
> -Original Message-
> From: Leonard Crestez
> Sent: Tuesday, November 6, 2018 11:34 PM
[...]
>
> On Tue, 2018-11-06 at 15:30 +, A.s. Dong wrote:
> > Gently Ping...
>
> > drivers/clk/imx/clk-composite.c| 85 +
>
> During review for 8m clocks a separate but
On Tue, 6 Nov 2018 at 20:51, Arnd Bergmann wrote:
>
> On 11/5/18, Kishon Vijay Abraham I wrote:
> > On 05/11/18 8:46 AM, Chunyan Zhang wrote:
> >>
> >> +sdhci_switch_extdma(host, true);
> >
> > A number of devices using sdhci-omap supports ADMA. So switching to
> > external
> > DMA shouldn't
1 - 100 of 772 matches
Mail list logo
