On Fri, Dec 08, 2017 at 03:12:26PM +0530, Sricharan R wrote:
> From: Stephen Boyd
>
> The ACC and GCC regions present in KPSSv1 contain registers to
> control clocks and power to each Krait CPU and L2. For CPUfreq
> purposes probe these devices and expose a mux clock that chooses
> between PXO an
On Fri, Dec 08, 2017 at 03:12:22PM +0530, Sricharan R wrote:
> From: Stephen Boyd
>
> On some devices (MSM8974 for example), the HFPLLs are
> instantiated within the Krait processor subsystem as separate
> register regions. Add a driver for these PLLs so that we can
> provide HFPLL clocks for use
On 12/12/2017 12:01 PM, Tejun Heo wrote:
> Changes from the last version[1]
>
> - BLK_EH_RESET_TIMER handling fixed.
>
> - s/request->gstate_seqc/request->gstate_seq/
>
> - READ_ONCE() added to blk_mq_rq_udpate_state().
>
> - Removed left over blk_clear_rq_complete() invocation from
> blk_mq_
On Sun, 10 Dec 2017 21:47:37 +0100
Stefan Brüns wrote:
> On Sunday, December 10, 2017 6:31:57 PM CET Jonathan Cameron wrote:
> > On Fri, 8 Dec 2017 18:41:50 +0100
> >
> > Stefan Brüns wrote:
> > > The iio timestamp clock is user selectable and may be non-monotonic. Also,
> > > only part of th
On 12/12/2017 11:21 AM, Thomas Gleixner wrote:
> The only critical interaction is the return to user path (user CS/SS) and
> we made sure with the LAR touching that these are precached in the CPU
> before we go into fragile exit code.
How do we make sure that it _stays_ cached?
Surely there is we
On Tue, 2017-12-12 at 18:23 +0100, Laurent Vivier wrote:
> When we migrate a VM from a POWER8 host (XICS) to a POWER9 host
> (XICS-on-XIVE), we have an error:
>
> qemu-kvm: Unable to restore KVM interrupt controller state \
> (0xff00) for CPU 0: Invalid argument
>
> This is because
On Fri, Dec 08, 2017 at 09:20:53AM +, srinivas.kandaga...@linaro.org wrote:
> From: Srinivas Kandagatla
>
> This patch adds supplies that are required for msm8996. Two of them vdda
> and vdda-1p8 are analog supplies that go in to controller, and the rest
> of the two vddpe's are supplies to P
On Sun, 10 Dec 2017 21:53:42 +0100
Stefan Brüns wrote:
> On Sunday, December 10, 2017 6:27:33 PM CET Jonathan Cameron wrote:
> > On Fri, 8 Dec 2017 18:41:48 +0100
> >
> > Stefan Brüns wrote:
> > > Although the datasheet states the CNVR flag is cleared by reading the
> > > BUS_VOLTAGE register
On Fri, Dec 08, 2017 at 05:12:13PM +0800, Greentime Hu wrote:
> From: Greentime Hu
>
> This patch adds nds32 SoC(AE3XX and AG101P) binding documents.
>
> Signed-off-by: Greentime Hu
> ---
> .../devicetree/bindings/nds32/andestech-boards | 40
>
> 1 file changed, 40
On 12/12/2017 11:56 AM, Kees Cook wrote:
On Tue, Dec 12, 2017 at 11:52 AM, Laura Abbott wrote:
On 12/12/2017 11:23 AM, Kees Cook wrote:
On Tue, Dec 12, 2017 at 2:58 AM, Tomáš Trnka wrote:
Hello,
Commit 04e35f4495dd560db30c25efca4eecae8ec8c375 "exec: avoid RLIMIT_STACK
races with prlimit()
On Fri, Dec 08, 2017 at 05:12:12PM +0800, Greentime Hu wrote:
> From: Greentime Hu
>
> This patch adds nds32 CPU binding documents.
>
> Signed-off-by: Vincent Chen
> Signed-off-by: Rick Chen
> Signed-off-by: Zong Li
> Signed-off-by: Greentime Hu
> ---
> Documentation/devicetree/bindings/nds
On Thu, Dec 07, 2017 at 08:57:39PM -0600, David Lechner wrote:
> This adds optional nvmem consumer properties to the ti,wlink-st device tree
> bindings to allow specifying the BD address.
>
> Signed-off-by: David Lechner
> ---
>
> v2 changes:
> * Renamed "mac-address" to "bd-address"
> * Fixed t
On Sun, 10 Dec 2017 21:22:13 +0100
Stefan Brüns wrote:
> On Sunday, December 10, 2017 6:36:54 PM CET Jonathan Cameron wrote:
> > On Fri, 8 Dec 2017 18:41:45 +0100
> >
> > Stefan Brüns wrote:
> > > Currently, the INA2xx driver may end up causing 100% load on a single core
> > > and fully loadi
On Thu, Dec 07, 2017 at 01:31:15PM -0800, Dhaval Shah wrote:
> Add Device Tree binding document for logicoreIP. This logicoreIP
> provides the isolation between the processing system and
> programmable logic. Also provides the clock related information.
>
> Signed-off-by: Dhaval Shah
> ---
> Chan
On Mon, Dec 11, 2017 at 02:11:55PM -0800, David Rientjes wrote:
> --- a/drivers/misc/sgi-gru/grutlbpurge.c
> +++ b/drivers/misc/sgi-gru/grutlbpurge.c
> @@ -298,6 +298,7 @@ struct gru_mm_struct *gru_register_mmu_notifier(void)
> return ERR_PTR(-ENOMEM);
> STAT(gms
On Tue, 12 Dec 2017 19:45:32 +, Al Viro wrote:
> On Tue, Dec 12, 2017 at 06:20:02AM +, Al Viro wrote:
>
> > Umm... What's wrong with
> >
> > #define FIELD_FOO 0,4
> > #define FIELD_BAR 6,12
> > #define FIELD_BAZ 18,14
> >
> > A macro can bloody well expand to any sequence of tokens - le
The vfio_info_add_capability() helper requires the caller to pass a
capability ID, which it then uses to fill in header fields, assuming
hard coded versions. This makes for an awkward and rigid interface.
The only thing we want this helper to do is allocate sufficient
space in the caps buffer and
On Mon, 31 Jul 2017 21:17:45 +0200
Wolfram Sang wrote:
> Hi Boris,
>
> > This patch series is a proposal for a new I3C [1] subsystem.
>
> Nice. Good luck with that!
>
> Some hi-level comments from me related to I2C. I can't say a lot more
> because the specs are not public :(
>
> > - the bu
On Tue, Dec 12, 2017 at 11:52 AM, Laura Abbott wrote:
> On 12/12/2017 11:23 AM, Kees Cook wrote:
>>
>> On Tue, Dec 12, 2017 at 2:58 AM, Tomáš Trnka wrote:
>>>
>>> Hello,
>>>
>>> Commit 04e35f4495dd560db30c25efca4eecae8ec8c375 "exec: avoid RLIMIT_STACK
>>> races with prlimit()" that made it into 4
On Mon, 11 Dec 2017 09:35:43 +0100
Quentin Schulz wrote:
> Hi Jonathan,
>
> On 10/12/2017 17:49, Jonathan Cameron wrote:
> > On Mon, 4 Dec 2017 15:12:51 +0100
> > Quentin Schulz wrote:
> >
> >> The X-Powers AXP813 PMIC has got some slight differences from
> >> AXP20X/AXP22X PMICs:
> >> - t
On 12/12/2017 11:23 AM, Kees Cook wrote:
On Tue, Dec 12, 2017 at 2:58 AM, Tomáš Trnka wrote:
Hello,
Commit 04e35f4495dd560db30c25efca4eecae8ec8c375 "exec: avoid RLIMIT_STACK
races with prlimit()" that made it into 4.14.4 effectively changes the default
hard RLIMIT_STACK on machines with SELinu
On Tue, Dec 12, 2017 at 11:21 AM, Thomas Gleixner wrote:
>
> That has nothing to do with the user installed LDT. The kernel does not use
> and rely on LDT at all.
Sure it does. We end up loading the selector for %gs and %fs, and
those selectors end up being connected with whatever user-mode has s
Hi Pavel,
On Sat, 2017-12-09 at 18:20 +0100, Pavel Machek wrote:
> On Mon 2017-12-04 11:50:40, Jose Abreu wrote:
> >
> > Hi Alexey,
> >
> > On 04-12-2017 11:32, Alexey Brodkin wrote:
> > >
> > > My first [probably incorrect] assumption is Xserver requires fbdev
> > > (/dev/fbX)
> > > and it ca
On Mon, 2017-12-11 at 15:36 -0800, Richard Cochran wrote:
> On Mon, Dec 11, 2017 at 05:14:31PM +0300, Aleksey Makarov wrote:
> > @@ -880,6 +889,46 @@ static void nic_pause_frame(struct nicpf *nic, int vf,
> > struct pfc *cfg)
> > }
> > }
> >
> > +/* Enable or disable HW timestamping by BGX
On Tue, Dec 12, 2017 at 06:20:02AM +, Al Viro wrote:
> Umm... What's wrong with
>
> #define FIELD_FOO 0,4
> #define FIELD_BAR 6,12
> #define FIELD_BAZ 18,14
>
> A macro can bloody well expand to any sequence of tokens - le32_get_bits(v,
> FIELD_BAZ)
> will become le32_get_bits(v, 18, 14) j
On Tuesday, 12 December 2017 20:23:47 CET Kees Cook wrote:
> This is an interesting state for the system to be in, though, it means
> AT_SECURE is being set for virtually all processes too? I would expect
> that might break a lot too (but clearly it hasn't).
Not really. AT_SECURE is set only for t
On Tue, Dec 12, 2017 at 05:37:59PM +, Russell King - ARM Linux wrote:
> On Tue, Dec 12, 2017 at 09:20:59AM -0800, Paul E. McKenney wrote:
> > The ARM implementation of arch_cpu_idle_dead() invokes complete(), but
> > does so after RCU has stopped watching the outgoing CPU, which results
> > in
Recently I got a Caldigit TS3 Thunderbolt 3 dock, and noticed that upon
hotplugging my kernel would immediately crash due to igb:
[ 680.825801] kernel BUG at drivers/pci/msi.c:352!
[ 680.828388] invalid opcode: [#1] SMP
[ 680.829194] Modules linked in: igb(O) thunderbolt i2c_algo_bit joyde
On Tue, Dec 12, 2017 at 07:40:46PM +0200, Baruch Siach wrote:
> Hi Paul,
>
> On Tue, Dec 12, 2017 at 09:20:59AM -0800, Paul E. McKenney wrote:
> > The ARM implementation of arch_cpu_idle_dead() invokes complete(), but
> > does so after RCU has stopped watching the outgoing CPU, which results
> > i
This patch remove two unused variable and some dead "code" using it.
Fixes: 92932d03c2b3 ("crypto: seqiv - Remove AEAD compatibility code")
Signed-off-by: Corentin Labbe
---
crypto/seqiv.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/crypto/seqiv.c b/crypto/seqiv.c
index 570b7d1aa0ca
This patch remove two unused variable and some dead "code" using it.
Fixes: 66008d4230f6 ("crypto: echainiv - Remove AEAD compatibility code")
Signed-off-by: Corentin Labbe
---
crypto/echainiv.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/crypto/echainiv.c b/crypto/echainiv.c
index e
On Tue, Dec 12, 2017 at 06:07:31PM +, Lorenzo Pieralisi wrote:
> On Tue, Dec 12, 2017 at 11:25:37AM -0600, Bjorn Helgaas wrote:
> > On Mon, Dec 11, 2017 at 10:42:33AM +, Lorenzo Pieralisi wrote:
> > > On Mon, Dec 11, 2017 at 11:29:55AM +0100, Johan Hovold wrote:
> > > > On Fri, Nov 17, 2017
On Thu, Dec 07, 2017 at 11:15:19AM +0100, Geert Uytterhoeven wrote:
> If CONFIG_DEBUG_SLAB=y, and no PCIe card is inserted, the kernel crashes
> during probe on r8a7791/koelsch:
>
> rcar-pcie fe00.pcie: PCIe link down
> Unable to handle kernel paging request at virtual address 6b6b6b6b
This reverts commit 04e35f4495dd560db30c25efca4eecae8ec8c375.
SELinux runs with secureexec for all non-"noatsecure" domain transitions,
which means lots of processes end up hitting the stack hard-limit change
that was introduced in order to fix a race with prlimit(). That race fix
will need to be
On Tue, 12 Dec 2017 14:39:21 +0900
Sergey Senozhatsky wrote:
> p.s.
> frankly, I don't see any "locking issues" in Steven's patch.
Should I push out another revision of mine?
-- Steve
> On Dec 12, 2017, at 11:05 AM, Linus Torvalds
> wrote:
>
>> On Tue, Dec 12, 2017 at 9:32 AM, Thomas Gleixner wrote:
>>
>> There is one exception; IRET will immediately load CS/SS and unrecoverably
>> #GP. To avoid this issue access the LDT descriptors used by CS/SS before
>> the IRET to use
On Tue, Dec 12, 2017 at 01:10:13PM -0500, Mike Snitzer wrote:
> On Mon, Dec 11 2017 at 11:00am -0500,
> Scott Bauer wrote:
>
> OK, but I'm left wondering: why doesn't the user avoid striping across
> the cores?
>
> Do the Intel NVMe drives not provide the ability to present 1 device per
> NVMe c
On Tue, Dec 12, 2017 at 2:58 AM, Tomáš Trnka wrote:
> Hello,
>
> Commit 04e35f4495dd560db30c25efca4eecae8ec8c375 "exec: avoid RLIMIT_STACK
> races with prlimit()" that made it into 4.14.4 effectively changes the default
> hard RLIMIT_STACK on machines with SELinux (seen on Fedora 27).
>
> selinux_
On Tue, 12 Dec 2017, Linus Torvalds wrote:
> On Tue, Dec 12, 2017 at 9:32 AM, Thomas Gleixner wrote:
> > From: Thomas Gleixner
> >
> > When the LDT is mapped RO, the CPU will write fault the first time it uses
> > a segment descriptor in order to set the ACCESS bit (for some reason it
> > doesn'
Hello Jason,
On 12/12/2017 07:57 PM, Jason Gunthorpe wrote:
> On Tue, Dec 12, 2017 at 12:38:00PM +0100, Javier Martinez Canillas wrote:
>
>> I'm not familiar with LPC so please let me know if my assumptions are wrong,
>> but I find suspicious that a driver for a single device attached to the bus
On Tue, Dec 12, 2017 at 9:32 AM, Thomas Gleixner wrote:
>
> There is one exception; IRET will immediately load CS/SS and unrecoverably
> #GP. To avoid this issue access the LDT descriptors used by CS/SS before
> the IRET to userspace.
Ok, so the other patch made me nervous, this just makes me go
On Tue, Dec 12, 2017 at 07:41:39PM +0100, Thomas Gleixner wrote:
> The pages are populated _before_ the new ldt is installed. So no memory
> pressure issue, nothing. If the populate fails, then modify_ldt() returns
> with an error.
Also, these pages are not visible to reclaim. They're not pagecach
Currently, blk-mq protects only the issue path with RCU. This patch
puts the completion path under the same RCU protection. This will be
used to synchronize issue/completion against timeout by later patches,
which will also add the comments.
Signed-off-by: Tejun Heo
---
block/blk-mq.c | 16 +++
blk_mq_check_inflight() and blk_mq_poll_hybrid_sleep() test
REQ_ATOM_COMPLETE to determine the request state. Both uses are
speculative and we can test REQ_ATOM_STARTED and blk_mq_rq_state() for
equivalent results. Replace the tests. This will allow removing
REQ_ATOM_COMPLETE usages from blk-mq.
After the recent updates to use generation number and state based
synchronization, blk-mq no longer depends on REQ_ATOM_COMPLETE for
anything.
Remove all REQ_ATOM_COMPLETE usages. This removes atomic bitops from
hot paths too.
v2: Removed blk_clear_rq_complete() from blk_mq_rq_timed_out().
Sign
Currently, blk-mq timeout path synchronizes against the usual
issue/completion path using a complex scheme involving atomic
bitflags, REQ_ATOM_*, memory barriers and subtle memory coherence
rules. Unfortunatley, it contains quite a few holes.
There's a complex dancing around REQ_ATOM_STARTED and
After the recent updates to use generation number and state based
synchronization, we can easily replace REQ_ATOM_STARTED usages by
adding an extra state to distinguish completed but not yet freed
state.
Add MQ_RQ_COMPLETE and replace REQ_ATOM_STARTED usages with
blk_mq_rq_state() tests. REQ_ATOM
With issue/complete and timeout paths now using the generation number
and state based synchronization, blk_abort_request() is the only one
which depends on REQ_ATOM_COMPLETE for arbitrating completion.
There's no reason for blk_abort_request() to be a completely separate
path. This patch makes bl
Changes from the last version[1]
- BLK_EH_RESET_TIMER handling fixed.
- s/request->gstate_seqc/request->gstate_seq/
- READ_ONCE() added to blk_mq_rq_udpate_state().
- Removed left over blk_clear_rq_complete() invocation from
blk_mq_rq_timed_out().
Currently, blk-mq timeout path synchronizes
On Tue, Dec 12, 2017 at 9:32 AM, Thomas Gleixner wrote:
> From: Thomas Gleixner
>
> When the LDT is mapped RO, the CPU will write fault the first time it uses
> a segment descriptor in order to set the ACCESS bit (for some reason it
> doesn't always observe that it already preset). Catch the faul
From: Borislav Petkov
... to denote that we have enabled page table isolation. Which is not a
bug but a feature! :-)
Signed-off-by: Borislav Petkov
Cc: Linus Torvalds
Cc: Andy Lutomirsky
Cc: Peter Zijlstra
Cc: Dave Hansen
Cc: Greg KH
Cc: keesc...@google.com
Cc: hu...@google.com
Cc: Brian G
Update the driver to conform with the LED framework.
Use devm_led_classdev_register
Destroy mutex on exit
Remove dependency on CONFIG_OF in the driver and move
to the Kconfig
Update the MODULE_LICENSE to GPL v2
Remove setting of MAX brightness as the LED framework
does this.
Signed-off-by: Dan Mur
Add a default trigger optional node to the child node.
This will allow the driver to set the trigger for a backlight.
Signed-off-by: Dan Murphy
---
v3 - Removed optional and rebased - https://patchwork.kernel.org/patch/10093755/
v2 - Moved binding changes to first patch in the series.
Documen
Update the lp8860 label binding to the LED
standard as documented in
Documentation/devicetree/bindings/leds/common.txt
Signed-off-by: Dan Murphy
---
v3 - Added address and size cells, updated label with color and inserted spaces
around the reg node - https://patchwork.kernel.org/patch/10093749/
Update the DT parsing for the label node so that
the label is retrieved from the device child as
opposed to being part of the parent.
This will align this driver with the LED
binding documentation
Documentation/devicetree/bindings/leds/common.txt
Signed-off-by: Dan Murphy
---
v3 - Changed the
Add the ability to parse the DT and set the default
trigger mode for the LED.
Signed-off-by: Dan Murphy
---
v3 - no changes - https://patchwork.kernel.org/patch/10093751/
v2 - no changes
drivers/leds/leds-lp8860.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/leds/leds-lp8860
Update the lp8860 bindings to fix various issues
found. Add address-cells and size-cells, rename
enable-gpio to enable-gpios, update the node name
to the device name and indent the node example.
Signed-off-by: Dan Murphy
---
v3 - Indicatd enable-gpios is active high, moved address and size cell
Update the driver to conform with the LED framework.
Use devm_led_classdev_register
Destroy mutex on exit
Remove dependency on CONFIG_OF in the driver and move
to the Kconfig
Update the MODULE_LICENSE to GPL v2
Remove setting of MAX brightness as the LED framework
does this.
Signed-off-by: Dan Mur
All
v3 - Made changes to the patch set to address concerns on DT node naming
conventions
based on discussion in the RFC patch
https://patchwork.kernel.org/patch/10089047/
also made requested changes to the DT and driver based on feedback. Patchworks
links in each patch.
v2 - Added an initial p
On Tue, Dec 12, 2017 at 12:38:00PM +0100, Javier Martinez Canillas wrote:
> I'm not familiar with LPC so please let me know if my assumptions are wrong,
> but I find suspicious that a driver for a single device attached to the bus
> can control the CLKRUN# signal which AFAIU may be needed for othe
Thanks, applied.
Ralf
On 12/12/2017 01:38 PM, Christian König wrote:
> Am 12.12.2017 um 19:12 schrieb Bjorn Helgaas:
>> [+cc Boris, Juergen, xen-devel]
>>
>> On Mon, Dec 11, 2017 at 04:04:52PM +0100, Christian König wrote:
>>> Xen hides a bit of system memory from the OS for its own purpose by
>>> intercepting e820. Thi
On Tue, 12 Dec 2017, Peter Zijlstra wrote:
> On Tue, Dec 12, 2017 at 09:58:58AM -0800, Andy Lutomirski wrote:
> > On Tue, Dec 12, 2017 at 9:32 AM, Thomas Gleixner wrote:
>
> > > +bool __ldt_write_fault(unsigned long address)
> > > +{
> > > + struct ldt_struct *ldt = current->mm->context.ldt
On 12/12/2017 06:31 PM, Paolo Bonzini wrote:
> After the vcpu_load/vcpu_put pushdown, the handling of asynchronous VCPU
> ioctl is already much clearer in that it is obvious that they bypass
> vcpu_load and vcpu_put.
>
> However, it is still not perfect in that the different state of the VCPU
> mu
On Tue, 12 Dec 2017, Peter Zijlstra wrote:
> On Tue, Dec 12, 2017 at 10:22:48AM -0800, Andy Lutomirski wrote:
> >
> > Also, why is LAR deferred to user exit? And I thought that LAR didn't
> > set the accessed bit.
>
> LAR does not set the ACCESSED bit indeed, we need to explicitly set that
> wh
On Tue, Dec 12, 2017 at 12:24:02PM -0600, Derald D. Woods wrote:
> On Tue, Dec 12, 2017 at 10:15:03AM -0800, Tony Lindgren wrote:
> > Well that's good to hear :) My only concern with your patch is what
> > happens if somebody boots with older u-boot with different partition
> > sizes?
>
> I agree.
From: Martin Brandenburg
Signed-off-by: Martin Brandenburg
---
fs/orangefs/file.c | 95 +++---
1 file changed, 19 insertions(+), 76 deletions(-)
diff --git a/fs/orangefs/file.c b/fs/orangefs/file.c
index 1668fd645c45..44879b1ff33e 100644
--- a/fs
Le 12/12/2017 à 16:58, Marek Vasut a écrit :
> On 12/12/2017 02:40 PM, Cyrille Pitchen wrote:
>> This reverts commit b07815d4eaf658b683c345d6e643895a20d92f29.
>>
>> The reverted commit was merged into v4-15-rc1 by mistake: it was taken
>> from the IMX tree but the patch has never been sent to linux
From: Martin Brandenburg
Signed-off-by: Martin Brandenburg
---
fs/orangefs/orangefs-utils.c | 4
1 file changed, 4 deletions(-)
diff --git a/fs/orangefs/orangefs-utils.c b/fs/orangefs/orangefs-utils.c
index 97fe93129f38..553b3ded51cd 100644
--- a/fs/orangefs/orangefs-utils.c
+++ b/fs/oran
From: Martin Brandenburg
Signed-off-by: Martin Brandenburg
---
fs/orangefs/dcache.c | 17 +++--
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/fs/orangefs/dcache.c b/fs/orangefs/dcache.c
index ae782df5c063..c7aa5c923477 100644
--- a/fs/orangefs/dcache.c
+++ b/fs/oran
Am 12.12.2017 um 19:12 schrieb Bjorn Helgaas:
[+cc Boris, Juergen, xen-devel]
On Mon, Dec 11, 2017 at 04:04:52PM +0100, Christian König wrote:
Xen hides a bit of system memory from the OS for its own purpose by
intercepting e820. This memory is unfortunately not reported as
reserved, but rather
From: Martin Brandenburg
Signed-off-by: Martin Brandenburg
---
fs/orangefs/file.c | 132
fs/orangefs/inode.c | 132
2 files changed, 132 insertions(+), 132 deletions(-)
diff --git a/fs/or
From: Martin Brandenburg
It's a copy of the loop which runs if it's not implemented from
read_pages from mm/readahead.c. Best to just use the generic code.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/file.c | 39 +--
1 file changed, 1 insertion(+), 38
From: Martin Brandenburg
Signed-off-by: Martin Brandenburg
---
fs/orangefs/file.c| 6 ++
fs/orangefs/orangefs-kernel.h | 5 -
2 files changed, 2 insertions(+), 9 deletions(-)
diff --git a/fs/orangefs/file.c b/fs/orangefs/file.c
index 3e5d467e24e6..afb94ed7cef3 100644
--- a/
From: Martin Brandenburg
This can't happen since it would have been caught (and a graceful
error returned) earlier.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/inode.c | 14 --
fs/orangefs/orangefs-utils.c | 4
2 files changed, 8 insertions(+), 10 deletions(-)
From: Martin Brandenburg
Since orangefs_file_read_iter now calls generic_file_read_iter, O_DIRECT
now goes through direct_IO in the read case. In the write case,
orangefs_file_write_iter never calls direct_IO, but handles the direct
write manually.
Signed-off-by: Martin Brandenburg
---
fs/ora
From: Martin Brandenburg
No need to manually implement this. The generic implementation handles
direct IO as well.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/file.c | 17 +++--
1 file changed, 3 insertions(+), 14 deletions(-)
diff --git a/fs/orangefs/file.c b/fs/orangefs/f
On Tue, Dec 12, 2017 at 10:05 AM, Andy Lutomirski wrote:
>>
>> - do NOT use "load_gs_index()", which does that swapgs dance (twice!)
>> and plays with interrupt state. Just load the segment register, and
>> then do the wrmsrl() of the {FS,GS,KERNEL_GS}_BASE values. There is no
>> need for the swap
From: Martin Brandenburg
Signed-off-by: Martin Brandenburg
---
fs/orangefs/file.c | 4 +---
fs/orangefs/namei.c | 4
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/fs/orangefs/file.c b/fs/orangefs/file.c
index afb94ed7cef3..8dfa0e8c7326 100644
--- a/fs/orangefs/file.c
+++
From: Martin Brandenburg
With this and the previous commit, OrangeFS is capable of writing
through the page cache.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/file.c | 132 +++-
fs/orangefs/inode.c | 2 +
fs/orangefs/super.c | 8
Now inodes will be marked dirty and written back at the appopriate time.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/acl.c | 11 +++
fs/orangefs/inode.c | 17 -
fs/orangefs/namei.c | 17 -
fs/orangefs/orangefs-kernel.h
This uses the same timeout as the getattr cache. This substantially
increases performance when writing files with smaller buffer sizes.
When writing, the size is (often) changed, which causes a call to
notify_change which calls security_inode_need_killpriv which needs a
getxattr. Caching it redu
From: Martin Brandenburg
This is a heavily modified revert of
70823b9bf3290855a7df895d89bd8209182b52e3.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/super.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/fs/orangefs/super.c b/fs/orangefs/super.c
From: Martin Brandenburg
This is a big change, but it boils down to implementing write_inode,
changing generic_delete_inode to generic_drop_inode, and changing
set/getattr to set/get from the in-memory inode.
The OrangeFS client requires a real getattr prior to any directory
operations.
Signed-
From: Martin Brandenburg
Must retrieve size before running filemap_fault so the kernel has
an up-to-date size.
This should have been caught by xfstests generic/246, but it was masked
by orangefs_new_inode, which set i_size to PAGE_SIZE. When nothing
caused a getattr prior to a pagefault, i_size
From: Martin Brandenburg
Signed-off-by: Martin Brandenburg
---
fs/orangefs/inode.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/orangefs/inode.c b/fs/orangefs/inode.c
index 5c451e245cf7..cf6924c36a22 100644
--- a/fs/orangefs/inode.c
+++ b/fs/orangefs/inode.c
@@ -187,
The first five patches were sent up two weeks ago.
https://marc.info/?l=linux-fsdevel&m=151190064825337&w=2
There is a bug in the original "implement vm_ops->fault" which is fixed
here. When expanding generic_file_readonly_mmap, I neglected to include
the test for VM_SHARED and VM_MAYWRITE. The
From: Martin Brandenburg
When an inode is created, we fetch attributes from the server. There is
no need to turn around and invalidate them.
No need to initialize attributes after the getattr either. Either we'll
do nothing or do something wrong.
Signed-off-by: Martin Brandenburg
---
fs/ora
On rk3288-veyron devices on Chrome OS it was found that plugging in an
Arduino-based USB device could cause the system to lockup, especially
if the CPU Frequency was at one of the slower operating points (like
100 MHz / 200 MHz).
Upon tracing, I found that the following was happening:
* The USB de
Hi,
On Tue, Dec 12, 2017 at 3:06 AM, Felipe Balbi wrote:
>
> Hi,
>
> Douglas Anderson writes:
>> On rk3288-veyron devices on Chrome OS it was found that plugging in an
>> Arduino-based USB device could cause the system to lockup, especially
>> if the CPU Frequency was at one of the slower operat
On Tue, Dec 12, 2017 at 10:22:48AM -0800, Andy Lutomirski wrote:
>
> Also, why is LAR deferred to user exit? And I thought that LAR didn't
> set the accessed bit.
LAR does not set the ACCESSED bit indeed, we need to explicitly set that
when creating the descriptor.
It also works if you do the L
On Tue, 12 Dec 2017 16:54:44 +0800
Ma Shimiao wrote:
> If source string longer than max, kstrndup will alloc max+1 space.
> So, we should make sure the result will not over limit.
>
> Signed-off-by: Ma Shimiao
Did you read the TODO file in drivers/staging/irda?
The irda code w
On Tue, Dec 12, 2017 at 10:06:51AM -0800, Andy Lutomirski wrote:
> On Tue, Dec 12, 2017 at 10:05 AM, Peter Zijlstra wrote:
> > gup would find the page. These patches do in fact rely on that through
> > the populate things.
> >
>
> Blech. So you can write(2) from the LDT to a file and you can ev
On Tue, Dec 12, 2017 at 06:31:55PM +0100, Paolo Bonzini wrote:
> After the vcpu_load/vcpu_put pushdown, the handling of asynchronous VCPU
> ioctl is already much clearer in that it is obvious that they bypass
> vcpu_load and vcpu_put.
>
> However, it is still not perfect in that the different stat
On Tue, Dec 12, 2017 at 10:15:03AM -0800, Tony Lindgren wrote:
> * Derald D. Woods [171212 18:11]:
> > On Tue, Dec 12, 2017 at 06:50:54PM +0100, Ladislav Michl wrote:
> > > On Tue, Dec 12, 2017 at 08:55:42AM -0800, Tony Lindgren wrote:
> > > > * Derald D. Woods [171212 16:34]:
> > > > > I am test
On Tue, 12 Dec 2017 08:34:45 -0500 (EST)
David Miller wrote:
> From: Jia-Ju Bai
> Date: Tue, 12 Dec 2017 16:38:12 +0800
>
> > According to drivers/net/ethernet/marvell/skge.c, the driver may sleep
> > under a spinlock.
> > The function call path is:
> > skge_remove (acquire the spinlock)
> >
> On Dec 12, 2017, at 10:10 AM, Andy Lutomirski wrote:
>
>> On Tue, Dec 12, 2017 at 10:09 AM, Peter Zijlstra
>> wrote:
>>> On Tue, Dec 12, 2017 at 10:03:02AM -0800, Andy Lutomirski wrote:
>>> On Tue, Dec 12, 2017 at 9:32 AM, Thomas Gleixner wrote:
>>
@@ -171,6 +172,9 @@ static void exi
* Ladislav Michl [171212 18:06]:
> On Tue, Dec 12, 2017 at 09:00:54AM -0800, Tony Lindgren wrote:
> > Hmm what do you mean? We don't want to export tons of custom functions from
> > the timers in and then be in trouble when at some point we have a Linux
> > generic hw timer framework. We already h
Hi Dongjiu Geng,
On 11/12/17 16:05, Dongjiu Geng wrote:
> do_sea() calls arm64_notify_die() which will always signal
> user-space. It also returns whether APEI claimed the external
> abort as a RAS notification. If it returns failure do_mem_abort()
> will signal user-space too.
>
> do_mem_abort()
Hi Brian,
Am Dienstag, 12. Dezember 2017, 09:43:43 CET schrieb Brian Norris:
> We generally leave the GPIO clock disabled, unless an interrupt is
> requested or we're accessing IO registers. We forgot to do this for the
> ->get_direction() callback, which means we can sometimes [1] get
> incorrect
601 - 700 of 1630 matches
Mail list logo
