commit 47933ad41a86 ("arch: Introduce smp_load_acquire(), smp_store_release()")
allowed only 4- and 8-byte smp_load_acquire, smp_store_release.
So 1- and 2-byte cases weren't implemented in arm64.
Later commit 536fa402221f ("compiler: Allow 1- and 2-byte smp_load_acquire()
On Mon 06-04-15 15:58:07, Tejun Heo wrote:
> Now that bdi definitions are moved to backing-dev-defs.h,
> backing-dev.h can include blkdev.h and inline inode_to_bdi() without
> worrying about introducing circular include dependency. The function
> gets called from hot paths and fairly trivial.
>
>
From: Dinh Nguyen
All the necessary debug uart mapping is already being done in
debug_ll_io_init, there's no need for it here.
Signed-off-by: Dinh Nguyen
Cc: Russell King
---
arch/arm/mach-socfpga/socfpga.c | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/arm/mach-socfpga/socf
From: Dinh Nguyen
Add support for hardware uart1 for earlyprintk support on Arria10 devkit.
Signed-off-by: Dinh Nguyen
CC: Russell King
---
arch/arm/Kconfig.debug | 25 ++---
1 file changed, 18 insertions(+), 7 deletions(-)
diff --git a/arch/arm/Kconfig.debug b/arch/arm/K
Hi Andrey,
On Mon, Apr 20, 2015 at 04:45:53PM +0100, Andrey Ryabinin wrote:
> commit 47933ad41a86 ("arch: Introduce smp_load_acquire(),
> smp_store_release()")
> allowed only 4- and 8-byte smp_load_acquire, smp_store_release.
> So 1- and 2-byte cases weren't implemented in arm64.
> Later commit 5
On 4/20/15 10:16 AM, Michael Wang wrote:
On 04/20/2015 04:00 PM, Steve Wise wrote:
On 4/20/2015 3:40 AM, Michael Wang wrote:
[snip]
diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h
index 6805e3e..e4999f6 100644
--- a/include/rdma/ib_verbs.h
+++ b/include/rdma/ib_verbs.h
@@ -1818,
On 20.04.2015 21:12, Ming Lei wrote:
> On Mon, Apr 20, 2015 at 4:07 PM, Dongsu Park
> wrote:
> > Hi Ming,
> >
> > On 18.04.2015 00:23, Ming Lei wrote:
> >> > Does anyone have an idea?
> >>
> >> As far as I can see, at least two problems exist:
> >> - race between timeout and CPU hotplug
> >> - in
Hi, Jens,
This flag was introduced under the auspices that the nvme blk-mq
conversion would make use of it. That never materialized. Are there
still plans to make use of it? If not, I'd like to get rid of it. If
so, then let's document it better.
Cheers,
Jeff
--
To unsubscribe from this list:
On Sun, Apr 19, 2015 at 10:39 PM, Ingo Molnar wrote:
>
>>
>> So I _could_ imagine that somebody would want to do optimistic "prod
>> other cpu" calls that in all normal cases are for existing cpus, but
>> could be racy in theory.
>
> Yes, and I don't disagree with such optimizations in principle (
On Mon, Apr 20, 2015 at 08:33:18AM -0700, Stephen Hemminger wrote:
> On Mon, 20 Apr 2015 15:59:06 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Apr 16, 2015 at 02:21:10PM -0700, Stephen Hemminger wrote:
> > > On Thu, 16 Apr 2015 09:43:24 +0200
> > > "Michael S. Tsirkin" wrote:
> > >
> > > >
On Mon, 2015-04-20 at 10:14 -0400, Alan Stern wrote:
> On Mon, 20 Apr 2015, Ivan T. Ivanov wrote:
>
> > Hi Alan,
> >
> > Perhaps I have to resend this patch with updated commit
> > message? Are they any other obstacles?
>
> Instead of submitting this new patch, would it be okay to revert commit
On Fri 17-04-15 20:35:30, Boqun Feng wrote:
> Hi Al,
>
> On Sun, Apr 12, 2015 at 02:13:18AM +0100, Al Viro wrote:
> >
> > BTW, looking at the __getname() callers... Lustre one sure as hell looks
> > bogus:
> > char *tmp = __getname();
> >
> > if (!tmp)
> > return
On Mon, Apr 20, 2015 at 04:54:32PM +0200, Greg Kroah-Hartman wrote:
> On Sun, Apr 19, 2015 at 11:08:00PM -0600, Jason Gunthorpe wrote:
> > I still suspect the expected way to write a new mid layer is to create
> > your own struct device and not rely on misc_device,
>
> Yes, that is the way. You c
On Mon, Apr 20, 2015 at 5:53 AM, Christoph Hellwig wrote:
> [I haven't much time to look through the patches, so only high level
> hand wavey comments for now, sorry..]
>
> On Mon, Apr 20, 2015 at 01:14:42AM -0700, Dan Williams wrote:
>> > So why on earth is this whole concept and the naming itse
On Fri, Apr 17, 2015 at 05:49:44PM +0200, Arnd Bergmann wrote:
> On Friday 17 April 2015 15:46:57 Catalin Marinas wrote:
> > On Fri, Apr 17, 2015 at 02:17:32PM +0100, Arnd Bergmann wrote:
> > > g) create a new ABI that does things in exactly the way that we
> > > would use as the native sysc
On 04/20/2015 09:09 AM, Jeff Moyer wrote:
Hi, Jens,
This flag was introduced under the auspices that the nvme blk-mq
conversion would make use of it. That never materialized. Are there
still plans to make use of it? If not, I'd like to get rid of it. If
so, then let's document it better.
Y
Here's a test patch that makes better use of SEEK_DATA/SEEK_HOLE in
cachefiles_read_or_alloc_pages() by caching data/hole information to use on
the subsequent pages in the list.
Note that the pages list needs to be transited in reverse for this to work as
it seems that the list passed to the fs is
From: Colin Ian King
cppcheck detected an uninitialized variable:
[drivers/pinctrl/mediatek/pinctrl-mtk-common.c:897]:
(error) Uninitialized variable: unmask
unmask should be initialized to zero to ensure unmasking
only occurs if a previous mask occurred. The current situation
is that the unm
Jens Axboe writes:
> On 04/20/2015 09:09 AM, Jeff Moyer wrote:
>> Hi, Jens,
>>
>> This flag was introduced under the auspices that the nvme blk-mq
>> conversion would make use of it. That never materialized. Are there
>> still plans to make use of it? If not, I'd like to get rid of it. If
>>
On Sun, Apr 19, 2015 at 12:17 PM, Davidlohr Bueso wrote:
>
> Naturally, this can cause spurious wakeups. However there is core code
> that cannot handle them afaict, and furthermore tglx does have the point
> that other events can already trigger them anyway.
Indeed. We need to make this *very* e
Hi Kevin,
On Mon, Apr 20, 2015 at 8:12 AM, Kevin Cernekee wrote:
> On Mon, Apr 20, 2015 at 5:21 AM, Mark Brown wrote:
>> On Sat, Apr 18, 2015 at 01:07:07PM -0700, Kevin Cernekee wrote:
>>> On Sat, Apr 18, 2015 at 10:11 AM, Mark Brown wrote:
>>
>>> > Someone trying to use the atmel_wm8904 driver
On Tue, Apr 21, 2015 at 07:38:58AM +0800, qipeng.zha wrote:
> From: "qipeng.zha"
>
> There defined Whiskey Cove PMIC controller on one Intel platform,
> and all registers on this PMIC are accessed by IPC commands.
> This patch is to utilize regmap framework to access PMIC registers
> for PMIC cor
On Mon, Apr 20, 2015 at 09:56:48AM -0600, Jason Gunthorpe wrote:
> On Mon, Apr 20, 2015 at 04:54:32PM +0200, Greg Kroah-Hartman wrote:
> > On Sun, Apr 19, 2015 at 11:08:00PM -0600, Jason Gunthorpe wrote:
> > > I still suspect the expected way to write a new mid layer is to create
> > > your own str
On Mon, 20 Apr 2015 16:22:48 +0800
Xunlei Pang wrote:
> + rq = task_rq(p);
> +
> + if (new_weight > 1 &&
> + rt_task(rq->curr) &&
> + rq->rt.rt_nr_total > 1 &&
> + !test_tsk_need_resched(rq->curr)) {
> + /*
> + * We own p->pi_lock and rq->
On Mon, Apr 20, 2015 at 8:45 AM, Andrey Ryabinin wrote:
>
> Commit 8053871d0f7f ("smp: Fix smp_call_function_single_async() locking")
> started to use smp_load_acquire() to load 2-bytes csd->flags.
> That crashes arm64 kernel during the boot.
Ahh. I don't disagree with your patch, but we should j
On Mon, Apr 20, 2015 at 04:48:24PM +0100, Will Deacon wrote:
> Hi Andrey,
>
> On Mon, Apr 20, 2015 at 04:45:53PM +0100, Andrey Ryabinin wrote:
> > commit 47933ad41a86 ("arch: Introduce smp_load_acquire(),
> > smp_store_release()")
> > allowed only 4- and 8-byte smp_load_acquire, smp_store_release
Hi Jonathan,
Thank you for reporting this issue!
On 03/30/2015 06:41 PM, Valdez, Jonathan wrote:
>
> Hello,
>
>
>
> I’ve been supporting the TCA8418 and have been pointed to your
> document by a few customers
> (http://lxr.free-electrons.com/source/drivers/input/keyboard/tca8418_keypad.c)
>
>
On Mon, Apr 20, 2015 at 05:08:37PM +0100, Linus Torvalds wrote:
> On Mon, Apr 20, 2015 at 8:45 AM, Andrey Ryabinin
> wrote:
> >
> > Commit 8053871d0f7f ("smp: Fix smp_call_function_single_async() locking")
> > started to use smp_load_acquire() to load 2-bytes csd->flags.
> > That crashes arm64 ke
> -Original Message-
> From: Christoph Lameter [mailto:c...@linux.com]
> Sent: 20 April 2015 16:43
> To: Daniel Sanders
> Cc: Pekka Enberg; David Rientjes; Joonsoo Kim; Andrew Morton; linux-
> m...@kvack.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v5] slab: Correct size_index ta
On Mon, Apr 20, 2015 at 06:45:53PM +0300, Andrey Ryabinin wrote:
> commit 47933ad41a86 ("arch: Introduce smp_load_acquire(),
> smp_store_release()")
> allowed only 4- and 8-byte smp_load_acquire, smp_store_release.
> So 1- and 2-byte cases weren't implemented in arm64.
> Later commit 536fa402221f
On Mon, Apr 20, 2015 at 10:51:58AM -0500, Tom Tucker wrote:
> On 4/20/15 10:16 AM, Michael Wang wrote:
> >On 04/20/2015 04:00 PM, Steve Wise wrote:
> >>On 4/20/2015 3:40 AM, Michael Wang wrote:
> >[snip]
> >>>diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h
> >>>index 6805e3e..e4999f6
When a resource is initialized via of_platform_populate.
resource->parent is initialized to NULL via kzalloc.
(of_platform_populate->of_device_alloc->of_address_to_resource)
If of_platform_depopulate is called later, resource->parent is
accessed (Offset 0x30 of address 0), causing a kernel error.
On 4/10/2015 4:24 AM, Tetsuo Handa wrote:
> This patchset seems to be blocked for waiting for an ACK from AppArmor
> people. John, can you give us ACK?
>
> Apart from ACK from John, I wrote a cleanup patch (shown below) which
> we might want to append to this patchset, though we anyway need to
> re
From: Guenter Roeck
Date: Sun, 19 Apr 2015 22:17:21 -0700
> The debug option is intended for all _other_ architectures, to
> ensure that changes made for those don't break alpha/s390
> builds. alpha/s390 have ARCH_NEEDS_WEAK_PER_CPU and don't need the
> debug option.
Ironically this would not cr
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Tuesday, April 07, 2015 9:23 PM
> To: Mehresh Ramneek-B31383
> Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org; ba...@ti.com;
> gre...@linuxfoundation.org
> Subject: Re: [PATCH 2/9][v2]usb:fsl:o
On Sat, 18 Apr 2015 19:05:42 -0700
"Paul E. McKenney" wrote:
> > > > Real-time priority to use for RCU worker threads
> > > > (RCU_KTHREAD_PRIO) [0] (NEW)
> > >
> > > Indeed, Linus complained about this one. ;-)
> >
> > :-) Yes, it's an essentially unanswerable question.
> >
> > > Th
t; implicit declaration of function 'ioread32be'
>
> Cc: Kevin Cernekee
> Cc: Rob Herring
> Cc: Greg Kroah-Hartman
> Fixes: c627f2ceb692 ("serial: 8250: Add support for big-endian MMIO
> accesses")
> Signed-off-by: Guenter Roeck
&g
> implicit declaration of function 'ioread32be'
>
> Cc: Kevin Cernekee
> Cc: Rob Herring
> Cc: Greg Kroah-Hartman
> Fixes: c627f2ceb692 ("serial: 8250: Add support for big-endian MMIO
> accesses")
> Signed-off-by: Guenter Roeck
>
On 4/20/15 11:19 AM, Jason Gunthorpe wrote:
On Mon, Apr 20, 2015 at 10:51:58AM -0500, Tom Tucker wrote:
On 4/20/15 10:16 AM, Michael Wang wrote:
On 04/20/2015 04:00 PM, Steve Wise wrote:
On 4/20/2015 3:40 AM, Michael Wang wrote:
[snip]
diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_v
> -Original Message-
> From: Mehresh Ramneek-B31383
> Sent: Monday, April 20, 2015 10:05 PM
> To: 'Alan Stern'
> Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org; ba...@ti.com;
> gre...@linuxfoundation.org
> Subject: RE: [PATCH 2/9][v2]usb:fsl:otg: Add support to add/remove usb
On Mon, Apr 20, 2015 at 12:25:19PM -0400, David Miller wrote:
> From: Guenter Roeck
> Date: Sun, 19 Apr 2015 22:17:21 -0700
>
> > The debug option is intended for all _other_ architectures, to
> > ensure that changes made for those don't break alpha/s390
> > builds. alpha/s390 have ARCH_NEEDS_WEA
On Mon, 2015-04-20 at 15:41 +0200, Mateusz Guzik wrote:
> On Sat, Apr 18, 2015 at 12:41:38PM -0700, Eric Dumazet wrote:
> > On Sat, 2015-04-18 at 00:02 +0100, Al Viro wrote:
> > > On Sat, Apr 18, 2015 at 12:16:48AM +0200, Mateusz Guzik wrote:
> > >
> > > > I would say this makes the use of seq cou
On Mon, 2015-04-20 at 09:46 -0700, Eric Dumazet wrote:
>
> Hey, that's because I really meant (during the week end)
old = xchg(&fdt->fd[fd], file);
if (unlikely(old && old != file))
filp_close(old, files);
That's going to be hard.
If you thought this problem was trivial, it probably me
On Mon, 20 Apr 2015 17:52:40 +0200
Dongsu Park wrote:
> On 20.04.2015 21:12, Ming Lei wrote:
> > On Mon, Apr 20, 2015 at 4:07 PM, Dongsu Park
> > wrote:
> > > Hi Ming,
> > >
> > > On 18.04.2015 00:23, Ming Lei wrote:
> > >> > Does anyone have an idea?
> > >>
> > >> As far as I can see, at least
From: Guenter Roeck
Date: Mon, 20 Apr 2015 09:44:31 -0700
> On Mon, Apr 20, 2015 at 12:25:19PM -0400, David Miller wrote:
>> From: Guenter Roeck
>> Date: Sun, 19 Apr 2015 22:17:21 -0700
>>
>> > The debug option is intended for all _other_ architectures, to
>> > ensure that changes made for thos
> If you don't care about sampling and only care about totals, then you
> can just open the events concurrently *without* grouping them, as I
> stated previously.
perf record doesn't really support that. We need some group reader
that runs regularly. The best choice for the leader is a CPU sample
On 17/04/2015 22:18, Marcelo Tosatti wrote:
> The bug which this is fixing is very rare, have no memory of a report.
>
> In fact, its even difficult to create a synthetic reproducer.
But then why was the task migration notifier even in Jeremy's original
code for Xen? Was it supposed to work ev
Hi Dudley.
Just a minor commit message nit. Thanks!
On Sun, Apr 19, 2015 at 10:43 PM, Dudley Du wrote:
> Fix update suspend scareate always set to max 1000 issue, the root cause is
s/scareate/scanrate
> the missed using max_t as min_t.
> TEST=test on Chromebook.
>
> Signed-off-by: Dudley Du
Re
On Fri, Apr 17, 2015 at 8:43 PM, Dmitry Torokhov
wrote:
> Let's zero-extend hardware id number when forming firmware file name,
> to avoid kernel requesting firmware like "elants_i2c_ 0.bin", which
> is quite unexpected.
>
> Signed-off-by: Dmitry Torokhov
> ---
> drivers/input/touchscreen/elan
On Mon, Apr 20, 2015 at 10:00:42AM -0700, Benson Leung wrote:
> Hi Dudley.
>
> Just a minor commit message nit. Thanks!
>
> On Sun, Apr 19, 2015 at 10:43 PM, Dudley Du wrote:
> > Fix update suspend scareate always set to max 1000 issue, the root cause is
> s/scareate/scanrate
> > the missed usin
On 4/20/2015 4:33 AM, Michael Wang wrote:
>
> Use raw management helpers to reform IB-core cm.
>
> Cc: Hal Rosenstock
> Cc: Steve Wise
> Cc: Tom Talpey
> Cc: Jason Gunthorpe
> Cc: Doug Ledford
> Cc: Ira Weiny
> Cc: Sean Hefty
> Signed-off-by: Michael Wang
> ---
> drivers/infiniband/core/
On Sun, Apr 19, 2015 at 12:46 AM, Boaz Harrosh wrote:
> On 04/18/2015 04:35 AM, Dan Williams wrote:
[..]
>> diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
>> index 11cc7d54ec3f..410af501a941 100644
>> --- a/arch/x86/kernel/e820.c
>> +++ b/arch/x86/kernel/e820.c
>> @@ -137,6 +137,8 @@
On Mon, Apr 20, 2015 at 11:35:54AM -0500, Clark Williams wrote:
> On Sat, 18 Apr 2015 19:05:42 -0700
> "Paul E. McKenney" wrote:
> > > > > Real-time priority to use for RCU worker threads
> > > > > (RCU_KTHREAD_PRIO) [0] (NEW)
> > > >
> > > > Indeed, Linus complained about this one. ;-)
There appears to be no formal statement of what pv_irq_ops.save_fl() is
supposed to return precisely. Native returns the full flags, while lguest and
Xen only return the Interrupt Flag, and both have comments by the
implementations stating that only the Interrupt Flag is looked at. This may
have
On 20/04/15 18:09, Andrew Cooper wrote:
> There appears to be no formal statement of what pv_irq_ops.save_fl() is
> supposed to return precisely. Native returns the full flags, while lguest and
> Xen only return the Interrupt Flag, and both have comments by the
> implementations stating that only
On Mon, 2015-04-20 at 17:10 +0200, Mateusz Guzik wrote:
> Sorry for spam but I came up with another hack. :)
>
> The idea is that we can have a variable which would signify the that
> given thread is playing with fd table in fd_install (kind of a lock
> embedded into task_struct). We would also h
On Mon, Apr 20, 2015 at 10:52:28AM -0400, Steven Rostedt wrote:
> On Mon, 20 Apr 2015 16:22:47 +0800
> Xunlei Pang wrote:
>
> > static inline void enqueue_pushable_task(struct rq *rq, struct task_struct
> > *p)
> > {
> > }
> > @@ -1506,8 +1526,21 @@ static void put_prev_task_rt(struct rq *rq,
On Mon, Apr 20, 2015 at 06:55:39AM -0700, Davidlohr Bueso wrote:
> I have been using this from Peter to test against:
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 6d77432..fdf1f68 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -214,9 +214,10 @@ pr
On Mon, Apr 20, 2015 at 03:51:41PM +0200, Wolfram Sang wrote:
> My Pengutronix address is not valid anymore, redirect people to the
> Pengutronix
> kernel team.
>
> Reported-by: Harald Geyer
> Signed-off-by: Wolfram Sang
> Acked-by: Robert Schwebel
> ---
> These patches shall go via the indivi
On Mon, 2015-04-20 at 16:57 +0200, Peter Zijlstra wrote:
> Haha, you dug that out did you ;-)
>
> Does this patch on its own actually help anything? Back when I wrote
> that there was the vague hope it would actually help some of the
> client-server ping-pong workloads, where the client does sync
Shaohua Li writes:
> Previous post of the patch is lost, so I repost. This is helpful, for
> example, using scsi-mq for a sata drive.
>
> plug is still helpful for workload with IO merge, but it can be harmful
> otherwise especially with multiple hardware queues, as there is (supposed) no
> lock
Hi Sascha,
Thank you for the comments.
On Mon, Apr 20, 2015 at 11:45:41AM +0200, Sascha Hauer wrote:
> On Tue, Apr 14, 2015 at 10:39:11PM -0700, Nicolin Chen wrote:
> > The SDMA on imx6sx has a few DMA event remapping configurations
> > inside the GPR (General Purpose Register) of that SoC. When
On Fri, Feb 27, 2015 at 05:16:56PM +0100, Wolfram Sang wrote:
> This tool allows to construct and concat multiple I2C messages into one
> single transfer. Its aim is to test I2C master controllers, and so there
> is no SMBus fallback.
>
> Signed-off-by: Wolfram Sang
> ---
>
> I've been missing s
On Mon, 20 Apr 2015, Ivan T. Ivanov wrote:
>
> On Mon, 2015-04-20 at 10:14 -0400, Alan Stern wrote:
> > On Mon, 20 Apr 2015, Ivan T. Ivanov wrote:
> >
> > > Hi Alan,
> > >
> > > Perhaps I have to resend this patch with updated commit
> > > message? Are they any other obstacles?
> >
> > Instead
On Mon, 20 Apr 2015, Ramneek Mehresh wrote:
> > > This is the wrong way to connect platform-private data with the
> > > ehci_hcd structure. The right way is to use an ehci_driver_overrides
> > > structure, like in ehci-omap.c and quite a few other EHCI platform
> > > drivers.
> > >
> >
> Hi Alan
On Monday 20 April 2015 16:56:00 Catalin Marinas wrote:
> On Fri, Apr 17, 2015 at 05:49:44PM +0200, Arnd Bergmann wrote:
> > On Friday 17 April 2015 15:46:57 Catalin Marinas wrote:
> > > On Fri, Apr 17, 2015 at 02:17:32PM +0100, Arnd Bergmann wrote:
> > | typedef unsigned short __kernel_mo
* Brown, Len wrote:
> > What's the cutoff for 'modern hardware' - which CPUs stopped requiring
> > the delay?
>
> This is the topic of ongoing research, and I'm not ready to send
> the patch setting a new default until I've heard back from a few more HW
> people.
>
> Every system I've tested
On Mon, 20 Apr 2015 19:20:48 +0200
Peter Zijlstra wrote:
> > > + */
> > > + if (preempt_count() & PREEMPT_ACTIVE)
> > > + enqueue_pushable_task_preempted(rq, p);
> > > + else
> > > + enqueue_pushable_task(rq, p);
> > > + }
> > > }
>
> Thi
On 04/19/2015 11:42 PM, Lee Jones wrote:
> On Fri, 17 Apr 2015, York Sun wrote:
>
>> Resend to LKML
>>
>> Lee,
>>
>> This question is actually more about MFD. Can you point me to the possible
>> causes for my failure below?
>
> It's hard to tell exactly without code, but it looks like you're
>
On Mon, Apr 20, 2015 at 05:02:31PM +0200, Jan Kara wrote:
> Maybe bdi_wb_destroy() would be somewhat more descriptive than
> bdi_wb_exit()? Otherwise the patch looks good to me. You can add:
> Reviewed-by: Jan Kara
Hmmm... maybe, I don't know. I feel weird matching up destroy with
init instead
On Mon, Apr 20, 2015 at 03:02:03PM +0200, Jens Wiklander wrote:
> > It appeared to me this driver was copying TPM's old architecture,
> > which is very much known to be broken.
>
> The struct tee_device holds a shared memory pool from which shared
> memory objects are allocated. These shared memor
On Mon, 20 Apr 2015, David Vrabel wrote:
> On 20/04/15 12:07, Chen Baozi wrote:
> > On Mon, Apr 20, 2015 at 11:53:47AM +0100, David Vrabel wrote:
> >> On 20/04/15 11:48, Chen Baozi wrote:
> >>> Make sure that xen_swiotlb_init allocates buffers that is DMA capable.
> >>>
> >>> Signed-off-by: Chen Ba
On Fri, 2015-04-17 at 15:49 +0200, Greg Kroah-Hartman wrote:
> On Thu, Apr 16, 2015 at 09:42:31AM +, Kweh, Hock Leong wrote:
> > > -Original Message-
> > > From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org]
> > > Sent: Wednesday, April 15, 2015 9:19 PM
> > >
> > > On Wed, Apr
On Mon, 20 Apr 2015 10:09:03 -0700
"Paul E. McKenney" wrote:
> On Mon, Apr 20, 2015 at 11:35:54AM -0500, Clark Williams wrote:
> > On Sat, 18 Apr 2015 19:05:42 -0700
> > "Paul E. McKenney" wrote:
> > > > > > Real-time priority to use for RCU worker threads
> > > > > > (RCU_KTHREAD_PRIO) [0]
On Mon, Apr 20, 2015 at 10:09:03AM -0700, Paul E. McKenney wrote:
>
> The sysfs knob might be nice, but as far as I know nobody has been
> complaining about it.
>
> Besides, we already have the rcutree.kthread_prio= kernel-boot parameter.
> So how about if the Kconfig parameter selects either SCH
On Fri, 2015-04-17 at 16:27 -0400, Havoc Pennington wrote:
> Hi,
>
> On Fri, Apr 17, 2015 at 3:27 PM, James Bottomley
> wrote:
> >
> > This is why I think kdbus is a bad idea: it solidifies as a linux kernel
> > API something which runs counter to granular OS virtualization (and
> > something whi
On Mon, Apr 20, 2015 at 05:09:50PM +0200, Jan Kara wrote:
> On Mon 06-04-15 15:58:02, Tejun Heo wrote:
> > Currently, a bdi (backing_dev_info) embeds single wb (bdi_writeback)
> > and the role of the separation is unclear. For cgroup support for
> > writeback IOs, a bdi will be updated to host mul
* Namhyung Kim wrote:
> As the --children option changes the output of perf report (and perf
> top) it sometimes confuses users. Add more words and examples to help
> understanding of the option's behavior - and how to disable it ;-).
Nice! :-)
> +++ b/tools/perf/Documentation/overhead.txt
A
* Steven Rostedt wrote:
> On Mon, Apr 20, 2015 at 10:09:03AM -0700, Paul E. McKenney wrote:
> >
> > The sysfs knob might be nice, but as far as I know nobody has been
> > complaining about it.
> >
> > Besides, we already have the rcutree.kthread_prio= kernel-boot
> > parameter. So how about i
From: Sowmini Varadhan
Date: Sun, 19 Apr 2015 13:13:29 -0400
> This patchset has fixes for 2 architectures
> - Part 1: x86_64 warnings generated by sparse
> - Part 2: allmodconfig build error for powerpc, identified by Guenter Roeck.
Series applied, thank you.
--
To unsubscribe from this list:
The patchset below gets rid of recursion in pathname resolution.
As the result, stack footprint of fs/namei.c stuff doesn't depend upon
the symlink nesting anymore and is much less than the worst cases in
mainline - as the matter of fact, it's around the footprint mainline gets
with just on
From: NeilBrown
No ->inode_follow_link() methods use the nameidata arg, and
it is about to become private to namei.c.
So remove from all inode_follow_link() functions.
Signed-off-by: NeilBrown
Signed-off-by: Al Viro
---
fs/namei.c | 2 +-
include/linux/security.h | 9 +++--
From: NeilBrown
ovl_follow_link current calls ->put_link on an error path.
However ->put_link is about to change in a way that it will be
impossible to call it from ovl_follow_link.
So rearrange the code to avoid the need for that error path.
Specifically: move the kmalloc() call before the ->fo
From: Al Viro
a) instead of storing the symlink body (via nd_set_link()) and returning
an opaque pointer later passed to ->put_link(), ->follow_link() _stores_
that opaque pointer (via nd_pin_link()) and returns the symlink body.
Returning ERR_PTR() on error, NULL on jump (procfs magic symlinks)
From: Al Viro
same story as the previous commit
Signed-off-by: Al Viro
---
fs/namei.c | 37 +++--
1 file changed, 15 insertions(+), 22 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index a8d6751..425986a 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -878,10 +
From: Al Viro
seriously improves the stack *and* I-cache footprint...
Signed-off-by: Al Viro
---
fs/namei.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index f1ec430..80edea9 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -1595,8 +1595,7 @@ static
From: Al Viro
What we do after the second walk_component() + put_link() + depth
decrement in there is exactly equivalent to what's done right
after the first walk_component(). Easy to verify and not at all
surprising, seeing that there we have just walked the last
component of nested symlink.
S
From: Al Viro
move the stack of saved states out of link_path_walk() stack frame to
that of callers, put a reference to it into struct nameidata as
nd->stack, move nd->saved_names[] elements in there.
Signed-off-by: Al Viro
---
fs/namei.c | 35 ---
1 file change
From: Al Viro
Deal with skipping leading slashes before what used to be the
recursive call. That way we can get rid of that goto completely.
Signed-off-by: Al Viro
---
fs/namei.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index 975918f
From: Al Viro
All remaining callers of the former are preceded by the latter
Signed-off-by: Al Viro
---
fs/namei.c | 21 ++---
1 file changed, 6 insertions(+), 15 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index 71c9546..e03c18f 100644
--- a/fs/namei.c
+++ b/fs/namei.c
From: Al Viro
don't bother with separate variables for link and cookie in trailing
symlink loops; use nd->stack[0] for that. That makes *all* callers
of put_link() (and follow_link()) operate on nd->stack[nd->depth].link
and nd->stack[nd->depth].cookie. Trim the argument lists.
Signed-off-by:
From: Al Viro
reduce the number of returns in there - turn all places
where it returns zero into goto OK and places where it
returns non-zero into goto Err. The only non-trivial
detail is that all breaks in the loop are guaranteed
to be with non-zero err.
Signed-off-by: Al Viro
---
fs/namei.c
From: Al Viro
Signed-off-by: Al Viro
---
fs/namei.c | 40 +---
1 file changed, 17 insertions(+), 23 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index 4b98f4b..975918f 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -1883,23 +1883,6 @@ Walked:
From: Al Viro
absolutely straightforward now - the only variables we need to preserve
across the recursive call are name, link and cookie, and recursion depth
is limited (and can is equal to nd->depth). So arrange an array of
triples to hold instances of those and be done with that.
Signed-off-
From: Al Viro
Calling conventions for ->follow_link() are rather unfortunate. It
would be better to have it return ERR_PTR(error) on error, NULL on
jumps and link body for normal symlinks. What we currently return
(opaque pointer used by ->put_link() once we are done) should've
been given to an
On Mon, 20 Apr 2015, York Sun wrote:
>
>
> On 04/19/2015 11:42 PM, Lee Jones wrote:
> > On Fri, 17 Apr 2015, York Sun wrote:
> >
> >> Resend to LKML
> >>
> >> Lee,
> >>
> >> This question is actually more about MFD. Can you point me to the possible
> >> causes for my failure below?
> >
> > It'
From: Al Viro
Pull the block after the if-else in the end of what used to be do-while
body into all branches there. We are almost done with the massage...
Signed-off-by: Al Viro
---
fs/namei.c | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/fs/namei.c
From: Al Viro
... it does nothing if nd->last_type is LAST_BIND.
Signed-off-by: Al Viro
---
fs/namei.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index 6e6630c..5366b6d 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -1854,7 +1854,11 @@ s
From: Al Viro
Signed-off-by: Al Viro
---
fs/namei.c | 61 -
1 file changed, 32 insertions(+), 29 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index 5366b6d..86d54e5 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -1832,6 +1832,10 @@
From: Al Viro
... and strip __always_inline from follow_link() - remaining callers
don't need that.
Now link_path_walk() recursion is a direct one.
Signed-off-by: Al Viro
---
fs/namei.c | 26 ++
1 file changed, 22 insertions(+), 4 deletions(-)
diff --git a/fs/namei.c
301 - 400 of 693 matches
Mail list logo
