On Fri, Oct 16, 2015 at 05:01:36PM +0100, Sudeep Holla wrote:
> The keyboard driver for GPIO buttons(gpio-keys) checks for one of the
> two boolean properties to enable gpio buttons as wakeup source:
> 1. "wakeup-source" or
> 2. the legacy "gpio-key,wakeup"
>
> However juno, ste-snowball and emev2
On Thu, Oct 8, 2015 at 5:54 PM, Pushpal Sidhu wrote:
> Comparing the imx6qdl-gw54xx.dtsi and imx6qdl-sabersd.dtsi, I couldn't
> see too many differences between HDMI and LVDS, so I'm a little
> surprised you don't see this exact same behavior there. Note that I've
On a imx6q-sabresd I get HDMI a
On Tue, Oct 20, 2015 at 02:05:22PM +0100, Suzuki K. Poulose wrote:
> The CCI PMU driver sets the event counter to the half of the maximum
> value(2^31) it can count before we start the counters via
> pmu_event_set_period(). This is done to give us the best chance to
> handle the overflow interrupt,
On Wed, Oct 14, 2015 at 04:02:50PM +0200, Antoine Tenart wrote:
> Some drivers used on a Marvell Berlin kernel were missing from
> multi_v7_defconfig. This series add them:
>
> * The pxa168 Ethernet driver is added as a loadable module.
> * The Berlin ADC driver is added as a loadable module.
David Miller writes:
> From: Mans Rullgard
> Date: Thu, 22 Oct 2015 15:02:38 +0100
>
>> This adds a driver for the Aurora VLSI NB8800 Ethernet controller.
>> It is an almost complete rewrite of a driver originally found in
>> a Sigma Designs 2.6.22 tree.
>>
>> Signed-off-by: Mans Rullgard
>
>
The DAX implementation needs to protect new calls to ->direct_access()
and usage of its return value against unbind of the underlying block
device. Use blk_queue_enter()/blk_queue_exit() to either prevent
blk_cleanup_queue() from proceeding, or fail the dax_map_atomic() if the
request_queue is bei
Changes since v1:
https://lists.01.org/pipermail/linux-nvdimm/2015-October/002538.html
1/ Rename file_bd_inode to bdev_file_inode (Jan Kara)
2/ Clarify sb_start_pagefault() comment (Jan Kara)
3/ Collect Reviewed-by's
---
As requested [1], break out the block specific updates from the dax-gup
dax_clear_blocks is currently performing a cond_resched() after every
PAGE_SIZE memset. We need not check so frequently, for example md-raid
only calls cond_resched() at stripe granularity. Also, in preparation
for introducing a dax_map_atomic() operation that temporarily pins a dax
mapping move
Both, __dax_pmd_fault, and clear_pmem() were taking special steps to
clear memory a page at a time to take advantage of non-temporal
clear_page() implementations. However, x86_64 does not use
non-temporal instructions for clear_page(), and arch_clear_pmem() was
always incurring the cost of __arch_
If an application wants exclusive access to all of the persistent memory
provided by an NVDIMM namespace it can use this raw-block-dax facility
to forgo establishing a filesystem. This capability is targeted
primarily to hypervisors wanting to provision persistent memory for
guests.
Cc: Jeff Moye
Similar to the file_inode() helper, provide a helper to lookup the inode for a
raw block device itself.
Cc: Al Viro
Suggested-by: Jan Kara
Signed-off-by: Dan Williams
---
fs/block_dev.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/fs/block_dev.c b/
Fixed a coding style issue.
Signed-off-by: Nilesh kokane
---
drivers/staging/lustre/lustre/lov/lov_obd.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/lustre/lustre/lov/lov_obd.c
b/drivers/staging/lustre/lustre/lov/lov_obd.c
index 96c55ac..8e1729e 1006
On Wed, Oct 21, 2015 at 12:13 PM, Austin S Hemmelgarn
wrote:
> On 2015-10-21 14:53, Andy Lutomirski wrote:
>>
>> On Oct 19, 2015 7:25 AM, "Austin S Hemmelgarn"
>> wrote:
>>>
>>>
>>> On 2015-10-17 11:58, Tobias Markus wrote:
Add capability CAP_SYS_USER_NS.
Tasks having CAP_SYS_
On some host errors storvsc module tries to remove sdev by scheduling a job
which does the following:
sdev = scsi_device_lookup(wrk->host, 0, 0, wrk->lun);
if (sdev) {
scsi_remove_device(sdev);
scsi_device_put(sdev);
}
While this code seems correct the following crash is ob
On Thu, 22 Oct 2015 13:14:07 +0800
Minfei Huang wrote:
> On 10/15/15 at 10:25pm, Steven Rostedt wrote:
> > On Thu, 17 Sep 2015 00:19:42 +0800
> > Minfei Huang wrote:
> >
> > > Now, ftrace only calculate the dyn_ftrace number in the adding
> > > breakpoint loop, not in adding update and finish u
This fell through the abyss of my INBOX.
Arnaldo, can you take this.
Acked-by: Steven Rostedt
-- Steve
On Mon, 31 Aug 2015 16:16:37 -0500
Scott Wood wrote:
> Commits such as 65dd297ac25565 ("xfs: %pF is only for function
> pointers") caused a regression because pretty_print() didn't suppor
On 10/21/2015 04:29 PM, Rafael J. Wysocki wrote:
> On Wed, Oct 21, 2015 at 6:41 PM, Al Stone wrote:
>> On 09/30/2015 04:38 AM, Graeme Gregory wrote:
>>> As discussed when Shannon Zhao sent a patch to add platform_device support
>>> to pl061 driver. Russel and other maintainers prefered that ACPI l
On Thu, Oct 22 2015 at 12:59pm -0400,
Ming Lin wrote:
> From: Ming Lin
>
> In commit b49a087("block: remove split code in
> blkdev_issue_{discard,write_same}"), discard_granularity and alignment
> checks were removed. Ideally, with bio late splitting, the upper layers
> shouldn't need to depend
Linus,
The following changes since commit b10d92a54dac25a6152f1aa1ffc95c12908035ce:
KVM: x86: fix RSM into 64-bit protected mode (2015-10-14 16:39:52 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to a
From: Colin Cross
It is quite common for Android devices to utilize more
then 8 partitions on internal eMMC storage.
The vanilla kernel can support this via
CONFIG_MMC_BLOCK_MINORS, however that solution caps the
system to 256 minors total, which limits the number of
mmc cards the system can sup
Hello Mark,
This trivial series fixes some warnings that I noticed in the SPI
subsystem when builing the kernel DocBook. All the warnings were
due missing description for some functions return values.
Patch #1 fixes the warnings from the include/linux/spi/spi.h header
file and patch #2 fixes the
From: Ming Lin
In commit b49a087("block: remove split code in
blkdev_issue_{discard,write_same}"), discard_granularity and alignment
checks were removed. Ideally, with bio late splitting, the upper layers
shouldn't need to depend on device's limits.
Christoph reported a discard regression on the
When building docs with make htmldocs, warnings about not having
a description for the return value are reported, i.e:
warning: No description found for return value of 'spi_register_driver'
Fix these by following the kernel-doc conventions explained in
Documentation/kernel-doc-nano-HOWTO.txt.
S
When building docs with make htmldocs, warnings about not having
a description for the return value are reported, i.e:
warning: No description found for return value of 'spi_write'
Fix these by following the kernel-doc conventions explained in
Documentation/kernel-doc-nano-HOWTO.txt.
Signed-off-
Hello
I've been busy but finally had a chance to run perf_fuzzer on current git.
I am running on an AMD A10 system (my traditional Haswell system is
otherwise occupied).
I got the following WARNING which was followed by an NMI storm which
eventually managed to confuse ext4 enough that my / part
Hi Benjamin,
[auto build test WARNING on jlayton/linux-next -- if it's inappropriate base,
please suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Benjamin-Coddington/locks-introduce-locks_lock_inode_wait/20151022-233848
repr
This adds a driver for the Aurora VLSI NB8800 Ethernet controller.
It is an almost complete rewrite of a driver originally found in
a Sigma Designs 2.6.22 tree.
Signed-off-by: Mans Rullgard
---
Changes:
- fix 64-bit build warnings
---
drivers/net/ethernet/Kconfig |1 +
drivers/net/et
Signed-off-by: Fengguang Wu
---
locks.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/locks.c b/fs/locks.c
index daf4664..0d2b326 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -1173,7 +1173,7 @@ EXPORT_SYMBOL(posix_lock_file);
*
* Apply a POSIX style lock reques
> -Original Message-
> From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-
> ow...@vger.kernel.org] On Behalf Of Bjorn Helgaas
> Sent: Thursday, October 22, 2015 5:36 PM
> To: Gabriele Paoloni
> Cc: Wangzhou (B); Bjorn Helgaas; jingooh...@gmail.com;
> pratyush.an...@gmail.com; Arnd Ber
Hi Chao,
On Thu, Oct 22, 2015 at 07:24:01PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Thursday, October 22, 2015 6:30 AM
> > To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> > linux-f2fs-de...
On Thu, Oct 22, 2015 at 11:28:32PM +0900, Namhyung Kim wrote:
> The --call-graph option is complex so we should provide better guide for
> users. Also change help message to be consistent with config option
> names. Now perf top will show help like below:
>
> $ perf top --call-graph
> Erro
Hi Gabriele,
On Thu, Oct 22, 2015 at 07:21:41AM +, Gabriele Paoloni wrote:
> > -Original Message-
> > From: Bjorn Helgaas [mailto:helg...@kernel.org]
> > > #define PCIECTRL_DRA7XX_CONF_PHY_CS 0x010C
> > > #define LINK_UP
On Thu, Oct 22, 2015 at 02:43:34PM +0200, Thomas Gleixner wrote:
> On Thu, 22 Oct 2015, Russell King - ARM Linux wrote:
> > The solutions are:
> > * A patch to restore the pr_debug() which Thomas applies, and Catalin
> > and myself then pull Thomas' tree again, which potentially creates
> > a m
On Thu, 2015-10-22 at 10:16AM +0530, Kedareswara rao Appana wrote:
> Simply resetting the peripheral on bus off condition is not enough,
> Because we also need to re-initialize the whole device.
> This patch fixes this issue.
>
> Signed-off-by: Kedareswara rao Appana
> ---
> drivers/net/can/xili
On Fri, Oct 16, 2015 at 02:28:10AM +, Kosuke Tatsukawa wrote:
> Tatsukawa Kosuke wrote:
> > J. Bruce Fields wrote:
> >> On Thu, Oct 15, 2015 at 11:44:20AM +, Kosuke Tatsukawa wrote:
> >>> Tatsukawa Kosuke wrote:
> >>> > J. Bruce Fields wrote:
> >>> >> Thanks for the detailed investigation.
On Thu, Oct 22, 2015 at 1:02 AM, Geliang Tang wrote:
> This patch changes return type of pstore_is_mounted from int to bool.
>
> Signed-off-by: Geliang Tang
Sure! :)
Acked-by: Kees Cook
-Kees
> ---
> fs/pstore/inode.c| 2 +-
> fs/pstore/internal.h | 2 +-
> 2 files changed, 2 insertions
This adds a binding for the Aurora VLSI NB8800 Ethernet controller
using the "aurora,nb8800" compatible string. When used in Sigma
Designs chips a few additional control registers are available.
This variant is indicated by the "sigma,smp8640-ethernet" compatible
string.
Signed-off-by: Mans Rullg
Em Fri, Oct 23, 2015 at 01:05:45AM +0900, Namhyung Kim escreveu:
> On Thu, Oct 22, 2015 at 11:46 PM, Arnaldo Carvalho de Melo
> > At some point it would be nice to be able to use:
> >
> > perf top --call-graph caller
> >
> > And have that be equivalent to:
> >
> > perf top --callgra
Em Fri, Oct 23, 2015 at 12:51:01AM +0900, Namhyung Kim escreveu:
> On Thu, Oct 22, 2015 at 11:37 PM, Arnaldo Carvalho de Melo
> wrote:
> > Will we also flip the default to --no-children? I would advocate that,
> > together with showing a info box telling the user about this change and
> > how to
On Thu, 22 Oct 2015, Benjamin Coddington wrote:
> Users of the locks API commonly call either posix_lock_file_wait() or
> flock_lock_file_wait() depending upon the lock type. Add a new function
> locks_lock_inode_wait() which will check and call the correct function for
> the type of lock passed
Using constants for pinctrl allows better readability and removes
redundancy with comments.
Signed-off-by: Andrew F. Davis
---
arch/arm/boot/dts/am335x-boneblack.dts | 44 +-
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a/arch/arm/boot/dts/am335x-
On Wed, Oct 14, 2015 at 06:47:36PM +0900, byungchul.p...@lge.com wrote:
> From: Byungchul Park
>
> Even though the cpu is non-idle when its tick is stoped in full NOHZ,
> current "update_cpu_load" code considers as if the cpu has been idle
> unconditionally. It's wrong. This patch makes the "upda
On Thu, 2015-10-22 at 18:58 +0300, Or Gerlitz wrote:
> On Wed, Oct 21, 2015 at 10:20 PM, Alex Williamson
> wrote:
>
> > This is why the typical VF agnostic approach here is to using bonding
> > and fail over to a emulated device during migration, so performance
> > suffers, but downtime is someth
You're right. Sorry for the noise Please ignore.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, Oct 22, 2015 at 08:46:33AM -0700, Rick Jones wrote:
> On 10/22/2015 02:33 AM, Michael S. Tsirkin wrote:
> >On Thu, Oct 22, 2015 at 01:27:29AM -0400, Jason Wang wrote:
> >>This patch tries to poll for new added tx buffer for a while at the
> >>end of tx processing. The maximum time spent on
Hi Rob,
> On Oct 22, 2015, at 00:52 , Rob Herring wrote:
>
> On Wed, Oct 21, 2015 at 2:37 PM, Pantelis Antoniou
> wrote:
>> Hi Rob,
>>
>>> On Oct 21, 2015, at 00:54 , Rob Herring wrote:
>>>
>>> On Tue, Oct 20, 2015 at 4:11 PM, Pantelis Antoniou
>>> wrote:
Hi Rob,
> On Oct 21,
Em Wed, Oct 21, 2015 at 10:28:03AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Oct 21, 2015 at 11:31:57AM +0800, Wangnan (F) escreveu:
> > >bpf: config program 'do_fork'
> > >symbol:do_fork file:(null) line:0 offset:0 return:0 lazy:(null)
> > >bpf: 'do_fork': event name is missing
> >
> >
On Thu, Oct 22, 2015 at 04:52:33PM +0200, Arnd Bergmann wrote:
> The remove function of a device driver should not be marked
> __exit, because that section gets discarded for built-in drivers,
> and it is still possible to manually unbind a driver from a
> device, which would result in a runtime er
From: "Steven Rostedt (Red Hat)"
Add the necessary hooks to use the pids loaded in set_event_pid to filter
all the events enabled in the tracing instance that match the pids listed.
Two probes are added to both sched_switch and sched_wakeup tracepoints to be
called before other probes are called
From: "Steven Rostedt (Red Hat)"
Create a tracing directory called set_event_pid, which currently has no
function, but will be used to filter all events for the tracing instance or
the pids that are added to the file.
The reason no functionality is added with this commit is that this commit
focu
Currently the only way to filter pids for events is to add it to the
filter file in the tracefs directory. Something like:
echo 'common_pid == 2123 || common_pid == 4211' > filter
The problem with this is that there's a very limited size that the
filter can accept. Thus, trying to trace all pro
From: "Steven Rostedt (Red Hat)"
My tests found that if a task is running but not filtered when set_event_pid
is modified, then it can still be traced.
Call on_each_cpu() to check if the current running task should be filtered
and update the per cpu flags of tr->data appropriately.
Signed-off-b
Hi Mike,
On Thu, 2015-10-22 at 01:30PM +0200, Mike Looijmans wrote:
> Supplying pinmux configuration for e.g. gpio pins leads to deferred
> probes because the pinctrl device is probed much later than gpio.
> Move the init call to a much earlier stage so it probes before the
> devices that may need
From: "Steven Rostedt (Red Hat)"
In order to guarantee that a probe will be called before other probes that
are attached to a tracepoint, there needs to be a mechanism to provide
priority of one probe over the others.
Adding a prio field to the struct tracepoint_func, which lets the probes be
so
Hello Doug,
On 10/22/2015 05:34 PM, Doug Anderson wrote:
> Krzysztof,
>
> On Wed, Oct 21, 2015 at 6:43 PM, Krzysztof Kozlowski
> wrote:
>> I think at least one platform may be affected because it used
>> mmc-pwrseq-emmc and gpio-restart.
>>
>> Look at rk3288-veyron.dtsi.
>>
>> Both of restart ha
On Thu, Oct 22, 2015 at 11:46 PM, Arnaldo Carvalho de Melo
wrote:
> Em Thu, Oct 22, 2015 at 11:28:32PM +0900, Namhyung Kim escreveu:
>> The --call-graph option is complex so we should provide better guide for
>> users. Also change help message to be consistent with config option
>> names. Now pe
On Thu, 2015-10-22 at 11:35 +0200, Jan Kara wrote:
> On Thu 22-10-15 02:42:11, Dan Williams wrote:
> > If an application wants exclusive access to all of the persistent memory
> > provided by an NVDIMM namespace it can use this raw-block-dax facility
> > to forgo establishing a filesystem. This ca
On 10/22/2015 09:53 AM, Jeff Moyer wrote:
Jens Axboe writes:
I agree with the optimizing hot paths by cheaper percpu operation,
but how much does it affect the performance?
A lot, since the queue referencing happens twice per IO. The switch to
percpu was done to use shared/common code for th
-static int __exit ramoops_remove(struct platform_device *pdev)
+static int ramoops_remove(struct platform_device *pdev)
Arnd,
Thanks. I folded that fix into the commit that made the error and rebased (I
don't believe
anyone is foolish enough to base work on my "next" branch)
-Tony
--
To uns
On 10/21/2015 11:42 PM, Jassi Brar wrote:
> On 22 October 2015 at 05:35, Suman Anna wrote:
>
>>> Anyways I am OK too, if you guys want to fix it with a platform
>>> specific quirk. Let me know I'll pick this patch.
>>
>> I haven't gotten a chance to try #1, and I won't be able to look at it
>>
Hi Benjamin,
[auto build test ERROR on jlayton/linux-next -- if it's inappropriate base,
please suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Benjamin-Coddington/locks-introduce-locks_lock_inode_wait/20151022-233848
config: x
On Thu, Oct 22, 2015 at 11:41 PM, Arnaldo Carvalho de Melo
wrote:
> Em Thu, Oct 22, 2015 at 11:28:31PM +0900, Namhyung Kim escreveu:
>> It's annoying to see error or help message when command has many options
>> like in perf record, report or top. So setup pager when print parser
>> error or help
On 10/22/2015 08:27 AM, Jason A. Donenfeld wrote:
eth_skb_pad returns 0 if it was successful, or -ENOMEM if it was not. In
that case, this function exits early. Some early exits return with
NETDEV_TX_BUSY, which queues the skb up to be tried again, and so the
skb should not be freed. Other early
On Wed, Oct 21, 2015 at 10:20 PM, Alex Williamson
wrote:
> This is why the typical VF agnostic approach here is to using bonding
> and fail over to a emulated device during migration, so performance
> suffers, but downtime is something acceptable.
bonding in the VM isn't a zero touch solution, r
On 10/22/15 6:57 AM, Peter Zijlstra wrote:
On Wed, Oct 21, 2015 at 03:58:03PM -0700, Alexei Starovoitov wrote:
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 64754bfecd70..0b6333265872 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -3258,7 +3258,7 @@ static inlin
Jens Axboe writes:
>> I agree with the optimizing hot paths by cheaper percpu operation,
>> but how much does it affect the performance?
>
> A lot, since the queue referencing happens twice per IO. The switch to
> percpu was done to use shared/common code for this, the previous
> version was a ha
Am Donnerstag, 22. Oktober 2015, 08:34:38 schrieb Doug Anderson:
> Note that personally I would only choose the "highest" priority as an
> absolute last resort. Leaving a little extra slack in there means
> that when the next person comes up with a really good reason to run
> before you do that th
On 10/22/15 12:39 AM, Wangnan (F) wrote:
...
if (!perf_event_can_insert_to_map(attr))
Do you think redability is improved?
yes. makes sense. will respin.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.
On Thu, Oct 22, 2015 at 11:37 PM, Arnaldo Carvalho de Melo
wrote:
> Em Thu, Oct 22, 2015 at 11:22:40PM +0900, Namhyung Kim escreveu:
>> On Thu, Oct 22, 2015 at 11:13 PM, Arnaldo Carvalho de Melo
>> wrote:
>> > Em Thu, Oct 22, 2015 at 03:28:50PM +0900, Namhyung Kim escreveu:
>> >> +++ b/tools/per
On 10/22/2015 05:50 AM, Michael S. Tsirkin wrote:
On Wed, Oct 21, 2015 at 01:58:19PM -0700, Alexander Duyck wrote:
On 10/21/2015 09:37 AM, Lan Tianyu wrote:
In order to restore VF function after migration, add self emulation layer
to record regs' values during accessing regs.
Signed-off-by: La
On Fri 23-10-15 00:37:03, Tejun Heo wrote:
> On Thu, Oct 22, 2015 at 05:35:59PM +0200, Michal Hocko wrote:
> > But that shouldn't happen because the allocation path does cond_resched
> > even when nothing is really reclaimable (e.g. wait_iff_congested from
> > __alloc_pages_slowpath).
>
> cond_res
Dear Ezequiel Garcia,
On Thu, 22 Oct 2015 12:22:24 -0300, Ezequiel Garcia wrote:
> Could you compare NAND throughput using keep-config (keeping
> the bootloader timings) and without keep-config (with ONFI timings) ?
Seems like we are within the measurement noise. I did each test only
once, and t
On 10/22/2015 02:33 AM, Michael S. Tsirkin wrote:
On Thu, Oct 22, 2015 at 01:27:29AM -0400, Jason Wang wrote:
This patch tries to poll for new added tx buffer for a while at the
end of tx processing. The maximum time spent on polling were limited
through a module parameter. To avoid block rx, th
On Thu, 2015-10-22 at 16:23 +0200, Eric Auger wrote:
> On 10/22/2015 04:10 PM, Arnd Bergmann wrote:
> > On Thursday 22 October 2015 15:26:55 Eric Auger wrote:
> @@ -181,6 +182,8 @@ static int vfio_platform_open(void *device_data)
> if (ret)
> g
The following changes since commit 25cb62b76430a91cc6195f902e61c2cb84ade622:
Linux 4.3-rc5 (2015-10-11 11:09:45 -0700)
are available in the git repository at:
git+ssh://gitol...@ra.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/fixes-for-linus
for you to fetch changes up to 55f41
On Thu, Oct 22, 2015 at 2:45 AM, Jan Kara wrote:
> On Thu 22-10-15 02:42:05, Dan Williams wrote:
>> Similar to the file_inode() helper, provide a helper to lookup the inode for
>> a
>> raw block device itself.
>
> So I somewhat dislike the name file_bd_inode() since for struct file
> pointing to
Hi James,
Could you pull these changes into your next branch please?
There are three groups:
(1) Miscellaneous cleanups.
(2) Add scripts for extracting system cert list and module sigs.
(3) Condense the type-specific data in the key struct into the payload
data as it doesn't really mak
On 10/22/15 6:59 AM, Peter Zijlstra wrote:
+ if (unlikely(event->oncpu != smp_processor_id()))
>+ return -EOPNOTSUPP;
>+
>+ perf_sample_data_init(&sample_data, 0, 0);
>+ sample_data.raw = &raw;
>+ perf_event_output(event, &sample_data, regs);
>+ return 0;
>+}
Note that th
NFS has recently been moving things around to cope with the situation where
a struct file may not be available during an unlock. That work has
presented an opportunity to do a minor cleanup on the locks API.
Users of posix_lock_file_wait() (for FL_POSIX style locks) and
flock_lock_file_wait() (fo
On Thu, Oct 22, 2015 at 05:35:59PM +0200, Michal Hocko wrote:
> But that shouldn't happen because the allocation path does cond_resched
> even when nothing is really reclaimable (e.g. wait_iff_congested from
> __alloc_pages_slowpath).
cond_resched() isn't enough. The work item should go !RUNNING,
Users of the locks API commonly call either posix_lock_file_wait() or
flock_lock_file_wait() depending upon the lock type. Add a new function
locks_lock_inode_wait() which will check and call the correct function for
the type of lock passed in.
Signed-off-by: Benjamin Coddington
---
fs/locks.c
All callers use locks_lock_inode_wait() instead.
Signed-off-by: Benjamin Coddington
---
fs/locks.c |5 +
include/linux/fs.h | 24
2 files changed, 1 insertions(+), 28 deletions(-)
diff --git a/fs/locks.c b/fs/locks.c
index 94d50d3..b6f3c92 100644
--- a
Instead of having users check for FL_POSIX or FL_FLOCK to call the correct
locks API function, use the check within locks_lock_inode_wait(). This
allows for some later cleanup.
Signed-off-by: Benjamin Coddington
---
drivers/staging/lustre/lustre/llite/file.c |8 ++--
fs/9p/vfs_file.c
On Fri 23-10-15 00:15:28, Tejun Heo wrote:
> On Thu, Oct 22, 2015 at 05:06:23PM +0200, Michal Hocko wrote:
> > Do I get it right that if vmstat_update has its own workqueue with
> > WQ_MEM_RECLAIM then there is a _guarantee_ that the rescuer will always
> > be able to process vmstat_update work fro
Krzysztof,
On Wed, Oct 21, 2015 at 6:43 PM, Krzysztof Kozlowski
wrote:
> I think at least one platform may be affected because it used
> mmc-pwrseq-emmc and gpio-restart.
>
> Look at rk3288-veyron.dtsi.
>
> Both of restart handlers had the priority of 129 which means that the
> order of execution
On Tue, Oct 20, 2015 at 8:20 PM, Masahiro Yamada
wrote:
> Hi Peter,
> (+ Rob Herring, Stefan Agner)
>
> 2015-10-20 23:00 GMT+09:00 Peter Hurley :
>> On 10/19/2015 11:36 PM, Masahiro Yamada wrote:
>>> The input clock frequency varies from device to device, but the
>>> earlycon uses the fixed freque
Ok that also makes me rethink commit
ba4877b9ca51f80b5d30f304a46762f0509e1635 which seems to be a similar fix
this time related to idle mode not updating the counters.
Could we fix that by folding the counters before going to idle mode?
That fix seems to now create 2 separate application interupt
On Thu, Oct 22, 2015 at 01:06:03PM +0100, Suzuki K. Poulose wrote:
> On Thu, Oct 22, 2015 at 01:26:52PM +1100, Stephen Rothwell wrote:
> > Today's linux-next merge of the tip tree got a conflict in:
> >
> > arch/arm64/kernel/cpufeature.c
> >
> > between commit:
> >
> > da8d02d19ffd ("arm64/c
It's understandable nobody really cares about applying this patch,
since it's mostly just cosmetic. But it would be nice to know that
somebody out there cares about consistency like I do. It would also
help out the next person who's debugging time things and says "where
is that darn .bc file?".
On
On Thu, Oct 22, 2015 at 05:15:09PM +0200, Peter Zijlstra wrote:
> Indefinitely is such a long time, we should try and finish
> computation before the computer dies etc. :-)
Indefinitely as read_seqcount_retry, eventually it makes progress.
Even returning 0 from the page fault can trigger it again
Hello,
On Thu, Oct 22, 2015 at 10:42:21AM -0400, Vivek Goyal wrote:
> > It works with ext2 and 4 and btrfs. Will document it. Thanks.
>
> Oh, nice. Are there any plans to make it work with xfs too?
Hmmm... not right now but it shouldn't be *too* difficult to add.
Thanks.
--
tejun
--
To unsu
On Fri, 2015-10-16 at 10:31 +0200, Lucas Stach wrote:
> Am Freitag, den 16.10.2015, 09:37 +0800 schrieb YH Huang:
> > In order to match the panel power sequence, disable the enable_gpio
> > in the probe function. Also, reorder the code in the power_on and
> > power_off function to match the timing.
eth_skb_pad returns 0 if it was successful, or -ENOMEM if it was not. In
that case, this function exits early. Some early exits return with
NETDEV_TX_BUSY, which queues the skb up to be tried again, and so the
skb should not be freed. Other early exits return with NETDEV_TX_OK,
like this one, in wh
On 22 October 2015 at 12:12, Thomas Petazzoni
wrote:
> Hello Antoine,
>
> On Wed, 21 Oct 2015 10:28:59 +0200, Antoine Tenart wrote:
>
>> Antoine Tenart (5):
>> mtd: pxa3xx: prepare allowing compile test
>> mtd: nand: allow compile test of MTD_NAND_PXA3xx
>> mtd: pxa3xx_nand: add helpers to s
Am 2015-10-20 um 13:03 schrieb Martin Kepplinger:
> Am 2015-10-15 um 15:10 schrieb Martin Kepplinger:
>> This change is important in order for everyone to be easily able to use the
>> driver for one of the supported accelerometer chips!
>>
>> Until now, the driver blindly assumed that the INT1 inte
On Thu, Oct 22, 2015 at 04:18:31PM +0200, Andrea Arcangeli wrote:
> The risk of memory corruption is still zero no matter what happens
> here, in the extremely rare case the app will get a SIGBUS or a
That might still upset people, SIGBUS isn't something an app can really
recover from.
> I'm not
Hello,
On Thu, Oct 22, 2015 at 09:41:11AM -0500, Christoph Lameter wrote:
> > If this is actually a legit busy-waiting cyclic dependency, just let
> > me know.
>
> There is no dependency of the vmstat updater on anything.
> They can run anytime. If there is a dependency then its created by the
>
On Thu, Oct 22, 2015 at 05:06:23PM +0200, Michal Hocko wrote:
> Do I get it right that if vmstat_update has its own workqueue with
> WQ_MEM_RECLAIM then there is a _guarantee_ that the rescuer will always
> be able to process vmstat_update work from the requested CPU?
Yeah.
> That should be suffi
Hi Russell,
On 10/21/2015 09:28 PM, Russell King - ARM Linux wrote:
> On Wed, Oct 21, 2015 at 09:13:48PM +0300, Grygorii Strashko wrote:
>> But I worry a bit (and that my main point) about these few additional
>> rounds of deferred device probing which I have right now and which allows
>> some of
On 10/22/2015 03:15 AM, jason wrote:
On Thursday, October 22, 2015 04:47 PM, Tejun Heo wrote:
Hello,
On Mon, Oct 19, 2015 at 07:40:13AM -0700, Zhangqing Luo wrote:
> So every time blk_mq_freeze_queue_start, it runs in this way
>
> blk_mq_freeze_queue_start
> ->percpu_ref_kill->percpu_ref
401 - 500 of 898 matches
Mail list logo
