Commit-ID: 450c86c9a3301db5165172bcaced73d036f9c582
Gitweb: http://git.kernel.org/tip/450c86c9a3301db5165172bcaced73d036f9c582
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 20 Jul 2017 10:46:34 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 20 Jul 2017 11:02:51 -0300
Commit-ID: 33396a3a6a6b16784291ac19708e3a6cf85db6c5
Gitweb: http://git.kernel.org/tip/33396a3a6a6b16784291ac19708e3a6cf85db6c5
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 19 Jul 2017 16:15:17 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 20 Jul 2017 11:03:04 -0300
Commit-ID: 15bed2742a8d60210b958963ca1091d3cfc4f332
Gitweb: http://git.kernel.org/tip/15bed2742a8d60210b958963ca1091d3cfc4f332
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 19 Jul 2017 16:52:59 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 20 Jul 2017 11:03:10 -0300
* Dan Williams wrote:
> On Wed, Jul 26, 2017 at 4:29 AM, Ingo Molnar wrote:
> >
> > * Dan Williams wrote:
> >
> >> On Tue, Jul 25, 2017 at 4:55 PM, Arnaldo Carvalho de Melo
> >> wrote:
> >> > Em Tue, Jul 25, 2017 at 03:36:26PM -0700, Dan Williams escreveu:
> >> >> Replace the ccan
Commit-ID: dd1a50377c92321f78fa4d0601bb4d88d88670ab
Gitweb: http://git.kernel.org/tip/dd1a50377c92321f78fa4d0601bb4d88d88670ab
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 20 Jul 2017 11:17:51 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 20 Jul 2017 11:17:51 -0300
On Wed, Jul 26, 2017 at 10:11:08AM -0700, Dan Williams wrote:
> Until HMAT came along we had no data in the kernel how to pick a sane
> default, but we could now very easily make a "if pmem performance <
> dram, disable dax by default" policy in the kernel.
I'd rather do it the other way around -
Commit-ID: 082ab9a18e532864d1ceecfb50221df62b1d5a92
Gitweb: http://git.kernel.org/tip/082ab9a18e532864d1ceecfb50221df62b1d5a92
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 20 Jul 2017 11:32:05 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 20 Jul 2017 15:16:25 -0300
On Wed, 26 Jul 2017 14:30:41 +0200
Michal Hocko wrote:
> On Wed 26-07-17 13:45:39, Heiko Carstens wrote:
> [...]
> > In general I do like your idea, however if I understand your patches
> > correctly we might have an ordering problem on s390: it is not possible to
> > access hot-added memory on
Commit-ID: 896bccd3cb8d95cbc565687715516009c5169e71
Gitweb: http://git.kernel.org/tip/896bccd3cb8d95cbc565687715516009c5169e71
Author: Taeung Song
AuthorDate: Thu, 20 Jul 2017 06:36:45 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 21 Jul 2017 08:23:38 -0300
perf annotate:
Commit-ID: 8e99b6d4533cf3f49dcd813155a513a5b572baef
Gitweb: http://git.kernel.org/tip/8e99b6d4533cf3f49dcd813155a513a5b572baef
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 20 Jul 2017 15:27:39 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 20 Jul 2017 15:46:10 -0300
Commit-ID: 8158683da3d30e0346275702a8e08f2b22726c45
Gitweb: http://git.kernel.org/tip/8158683da3d30e0346275702a8e08f2b22726c45
Author: Taeung Song
AuthorDate: Thu, 20 Jul 2017 06:36:51 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 21 Jul 2017 08:23:49 -0300
perf annotate:
On Wed, Jul 26, 2017 at 5:52 AM, Daniel Micay wrote:
> It should just be renamed from fortify_panic -> fortify_error, including
> in arch/x86/boot/compressed/misc.c and arch/x86/boot/compressed/misc.c.
Somehow I missed these. I'll send a v2. I wonder why those didn't trip
in my build...
> It
Commit-ID: 461c17f00f400f95116880d91d20a7fcd84263a9
Gitweb: http://git.kernel.org/tip/461c17f00f400f95116880d91d20a7fcd84263a9
Author: Taeung Song
AuthorDate: Thu, 20 Jul 2017 17:18:05 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 21 Jul 2017 12:02:38 -0300
perf annotate:
Commit-ID: bab89f6aed7e745893e009014354d0caaf62acf7
Gitweb: http://git.kernel.org/tip/bab89f6aed7e745893e009014354d0caaf62acf7
Author: Taeung Song
AuthorDate: Thu, 20 Jul 2017 16:28:53 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 21 Jul 2017 08:23:50 -0300
perf hists:
Commit-ID: b99e4850df86dfd9dc2cf3f3494e403ff8b46876
Gitweb: http://git.kernel.org/tip/b99e4850df86dfd9dc2cf3f3494e403ff8b46876
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 20 Jul 2017 15:35:33 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 20 Jul 2017 15:47:33 -0300
Commit-ID: ecd5f9959d2c9540482977ff1208ea67fbfb8cc9
Gitweb: http://git.kernel.org/tip/ecd5f9959d2c9540482977ff1208ea67fbfb8cc9
Author: Taeung Song
AuthorDate: Fri, 21 Jul 2017 11:38:48 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 21 Jul 2017 12:02:52 -0300
perf annotate:
This is useful for directly looking up a task based on class id rather than
having to scan through all open file descriptors.
Signed-off-by: Sasha Levin
---
include/uapi/linux/inet_diag.h | 1 +
net/ipv4/inet_diag.c | 10 ++
2 files changed, 11 insertions(+)
diff --git
Commit-ID: 585d93c5ffccced26689e34095c0d74ef20a07d6
Gitweb: http://git.kernel.org/tip/585d93c5ffccced26689e34095c0d74ef20a07d6
Author: Taeung Song
AuthorDate: Fri, 21 Jul 2017 11:58:20 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 11:23:36 -0300
perf annotate
Hi Doug,
Clearly you are a "discerning user", who understands the limitations
of the kernel sysfs interface,
both new and old, for communicating frequency. With the limitations
of the (old and new)
sysfs interfaces, why are you using it, rather than turbostat?
>> As with previous methods of
Hi Egil
> +/* forward special tagged packets from port 0 to port 1 *or* port 2 */
> +static int lan9303_setup_tagging(struct lan9303 *chip)
> +{
> + int ret;
Blank line please.
> + /* enable defining the destination port via special VLAN tagging
> + * for port 0
> + */
> +
Commit-ID: 2b04e0f88291c0dc7e12459bd3c3661d42209b4e
Gitweb: http://git.kernel.org/tip/2b04e0f88291c0dc7e12459bd3c3661d42209b4e
Author: Jiri Olsa
AuthorDate: Fri, 21 Jul 2017 14:12:09 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 11:23:53 -0300
perf evsel: Add
Commit-ID: f4849599086c6462d65543637058c9b55f4803e4
Gitweb: http://git.kernel.org/tip/f4849599086c6462d65543637058c9b55f4803e4
Author: David Carrillo-Cisneros
AuthorDate: Tue, 18 Jul 2017 18:18:38 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 11:23:52 -0300
Commit-ID: cb281fea4b0a326d2a2104f8ffae2b6895c561fd
Gitweb: http://git.kernel.org/tip/cb281fea4b0a326d2a2104f8ffae2b6895c561fd
Author: David Carrillo-Cisneros
AuthorDate: Tue, 18 Jul 2017 18:18:37 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 11:23:51 -0300
Commit-ID: cd8dd032f61abeb08d2c03bab4968a9de231a1be
Gitweb: http://git.kernel.org/tip/cd8dd032f61abeb08d2c03bab4968a9de231a1be
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 18 Jul 2017 20:20:19 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 11:23:50 -0300
Commit-ID: 868a832918f621b7576655c00067f20326ef3931
Gitweb: http://git.kernel.org/tip/868a832918f621b7576655c00067f20326ef3931
Author: Krister Johansen
AuthorDate: Wed, 5 Jul 2017 18:48:12 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:43:16 -0300
perf top:
Commit-ID: 2ec5cab604b2bbc5abe7138b537199762bea59ce
Gitweb: http://git.kernel.org/tip/2ec5cab604b2bbc5abe7138b537199762bea59ce
Author: Dan Carpenter
AuthorDate: Sat, 22 Jul 2017 10:36:10 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:43:17 -0300
perf script:
Commit-ID: 5d90faf45427dd76fadbe7a4dc4fce3b6f87b550
Gitweb: http://git.kernel.org/tip/5d90faf45427dd76fadbe7a4dc4fce3b6f87b550
Author: Sudeep Holla
AuthorDate: Tue, 18 Jul 2017 18:18:39 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 11:23:53 -0300
perf jvmti:
Commit-ID: 3f056b66647bafc39f060a57289320765915972c
Gitweb: http://git.kernel.org/tip/3f056b66647bafc39f060a57289320765915972c
Author: Andi Kleen
AuthorDate: Mon, 24 Jul 2017 17:16:38 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:46:36 -0300
perf jevents:
> > > Hmm... I'm not seeing any implementation that would allow setting
> > > between firmware first, hardware first or "auto", as we've discussed.
> >
> > This is all coming up. As the 0/3 message said, these 3 patches are the
> > bare minimum of reorganizing stuff only and should serve as a
Commit-ID: b49a821ed9e05fa0ccbaec2555052b2a920be517
Gitweb: http://git.kernel.org/tip/b49a821ed9e05fa0ccbaec2555052b2a920be517
Author: Jin Yao
AuthorDate: Mon, 8 May 2017 18:43:02 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:46:03 -0300
perf report: Make
Commit-ID: a1a8bed32de197801bb861fbf13cd01496df3e05
Gitweb: http://git.kernel.org/tip/a1a8bed32de197801bb861fbf13cd01496df3e05
Author: Jin Yao
AuthorDate: Mon, 24 Jul 2017 19:09:07 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:46:35 -0300
perf report: Tag
Commit-ID: e9f9a9ca8588e58dc0800b44adc41d32f6fc813a
Gitweb: http://git.kernel.org/tip/e9f9a9ca8588e58dc0800b44adc41d32f6fc813a
Author: Arun Kalyanasundaram
AuthorDate: Fri, 21 Jul 2017 15:04:18 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:43:18 -0300
perf
Commit-ID: 38d2dcd0ccf85b55d783edbfc14fd8dea4d55b73
Gitweb: http://git.kernel.org/tip/38d2dcd0ccf85b55d783edbfc14fd8dea4d55b73
Author: Taeung Song
AuthorDate: Tue, 25 Jul 2017 06:28:42 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:46:37 -0300
perf annotate
Commit-ID: 892e76b2e8c5e85e69514478e3319575a68b9770
Gitweb: http://git.kernel.org/tip/892e76b2e8c5e85e69514478e3319575a68b9770
Author: Arun Kalyanasundaram
AuthorDate: Fri, 21 Jul 2017 15:04:19 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:43:19 -0300
perf
Commit-ID: 62e6039f02888efdd824e8c596c4927616a97ce3
Gitweb: http://git.kernel.org/tip/62e6039f02888efdd824e8c596c4927616a97ce3
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 25 Jul 2017 14:14:27 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:46:37 -0300
Commit-ID: 74ec14f3893c3065053b91cec850cffa2d565e0a
Gitweb: http://git.kernel.org/tip/74ec14f3893c3065053b91cec850cffa2d565e0a
Author: Arun Kalyanasundaram
AuthorDate: Fri, 21 Jul 2017 15:04:20 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:43:19 -0300
perf
Commit-ID: a641860550f05a4b8889dca61aab73c84b2d5e16
Gitweb: http://git.kernel.org/tip/a641860550f05a4b8889dca61aab73c84b2d5e16
Author: Arun Kalyanasundaram
AuthorDate: Fri, 21 Jul 2017 15:04:22 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:43:21 -0300
perf
Commit-ID: f38d281663b011d1d8a1b0119bb8357706d134a8
Gitweb: http://git.kernel.org/tip/f38d281663b011d1d8a1b0119bb8357706d134a8
Author: Arun Kalyanasundaram
AuthorDate: Fri, 21 Jul 2017 15:04:21 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 25 Jul 2017 22:43:20 -0300
perf
On Wed, Jul 26, 2017 at 10:19 AM, Ingo Molnar wrote:
>
> * Dan Williams wrote:
>
>> On Wed, Jul 26, 2017 at 4:29 AM, Ingo Molnar wrote:
>> >
>> > * Dan Williams wrote:
>> >
>> >> On Tue, Jul 25, 2017 at 4:55 PM, Arnaldo Carvalho de Melo
>> >> wrote:
>> >> > Em Tue, Jul 25, 2017 at 03:36:26PM
On Wed, Jul 26, 2017 at 06:30:49PM +0200, Borislav Petkov wrote:
> On Wed, Jul 26, 2017 at 09:19:49AM -0700, Greg KH wrote:
> > On Wed, Jul 26, 2017 at 05:55:48PM +0200, Borislav Petkov wrote:
> > > On Wed, Jul 26, 2017 at 05:45:15PM +0200, Jan Glauber wrote:
> > > > The PMU/EDAC devices are all
On Wednesday, July 26, 2017 11:59:12 AM Viresh Kumar wrote:
> On 24-07-17, 15:47, Peter Zijlstra wrote:
> > I said nothing about the shared locking. That is indeed required. All I
> > said is that those two tests you add could be left out.
>
> I was right, I didn't understood your comment at all
On 07/26/2017 03:07 AM, Michal Hocko wrote:
> On Wed 26-07-17 11:53:38, Michal Hocko wrote:
>> On Mon 17-07-17 15:28:01, Mike Kravetz wrote:
>>> Use the common definitions from hugetlb_encode.h header file for
>>> encoding hugetlb size definitions in shmget system call flags. In
>>> addition,
On Wed, 26 Jul 2017, Pavel Machek wrote:
> Hi!
>
> > > > > Unfortunately, that would mean shifting 400GB data 8KB forward, and
> > > > > compatibility problems. So I'd prefer adding bcache superblock into
> > > > > the reserved space, so I can have caching _and_ compatibility with
> > > > >
Hi Egil
> +/* This function will wait a while until mask & reg == value */
> +/* Otherwise, return timeout */
> +static int lan9303_csr_reg_wait(struct lan9303 *chip, int regno,
> + int mask, char value)
> +{
> + int i;
> +
> + for (i = 0; i < 0x1000; i++) {
>
Greetings
While I am not getting the original error anymore, using dm-crypt
still fails at cryptsetup luksOpen with [rk_ablk_rx:331] Lack of data
https://users.aalto.fi/~jkarlson/files/rk3288-fail_2017-07-24.jpg
Test platform: Asus chromebook C201/rk3288 linux-4.12.3+ this patchset
Best Regards
On 07/19/2017 06:08 AM, Mark Brown wrote:
> On Tue, Jul 18, 2017 at 02:20:04PM -0500, Michael Stecklein wrote:
>
>> +if (!tx_mask) {
>> +dev_err(codec->dev, "tdm mask must not be 0\n");
>> +return -EINVAL;
>> +}
> Setting the mask to 0 is used when turning off TDM.
Dne 25.7.2017 v 21:50 Alan Stern napsal(a):
On Tue, 25 Jul 2017, Zdenek Kabelac wrote:
08:18 usb 2-2: USB disconnect, device number 2
08:25 usb 2-2: new high-speed USB device number 3 using ehci-pci
08:26 usb 2-2: new high-speed USB device number 4 using ehci-pci
If the drive were working
On Wednesday, July 26, 2017 02:52:32 PM Viresh Kumar wrote:
> We do not call cpufreq callbacks from scheduler core for remote
> (non-local) CPUs currently. But there are cases where such remote
> callbacks are useful, specially in the case of shared cpufreq policies.
>
> This patch updates the
On 07/25/2017 05:22 PM, Stefano Stabellini wrote:
> Send PVCALLS_ACCEPT to the backend. Allocate a new active socket. Make
> sure that only one accept command is executed at any given time by
> setting PVCALLS_FLAG_ACCEPT_INFLIGHT and waiting on the
> inflight_accept_req waitqueue.
>
>
> > So I really want to group the patches into only a few series in order
> > to not spend months on the process.
I strongly agree with Vivien here. Good patches get accepted in about
3 days. You should expect feedback within a day or two. That allows
you to have fast cycle times for getting
On 7/25/2017 8:58 PM, Kees Cook wrote:
> On Tue, Jul 18, 2017 at 3:25 PM, Kees Cook wrote:
>> The Smack bprm_secureexec hook can be merged with the bprm_set_creds
>> hook since it's dealing with the same information, and all of the details
>> are finalized during the first call to the
From: Jeff Layton
This means that we need to export the new file_fdatawait_range symbol.
Also, fix a place where a writeback error might get dropped in the
gfs2_is_jdata case.
Signed-off-by: Jeff Layton
---
fs/gfs2/file.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff
From: Jeff Layton
sync_file_range doesn't call down into the filesystem directly at all.
It only kicks off writeback of pagecache pages and optionally waits
on the result.
Convert sync_file_range to use errseq_t based error tracking, under the
assumption that most users will prefer this
From: Jeff Layton
We have this complex conditional copied to several places. Turn it into
a helper function.
Signed-off-by: Jeff Layton
---
mm/filemap.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/mm/filemap.c b/mm/filemap.c
index
From: Jeff Layton
Some filesystem fsync routines will need these.
Signed-off-by: Jeff Layton
---
include/linux/fs.h | 7 ++-
mm/filemap.c | 56 ++
2 files changed, 62 insertions(+), 1 deletion(-)
diff --git a/include/linux/fs.h
From: Jeff Layton
I sent a small patch earlier this week to make sync_file_range use
errseq_t reporting.
This set respins that patch into a patch that adds a bit more file_*
infrastructure, and then patches to make sync_file_range and fsync
on gfs2 report writeback errors properly.
There's
> Maybe we could do two phases? One to s/BUG/WARN/ and the second to
> improve the message?
s/fortify_panic/fortify_overflow/ + use WARN + remove __noreturn makes
sense as one commit. Still think the *option* of __noreturn + BUG should
be kept there even just for measuring the size overhead.
> On Jul 26, 2017, at 11:50 AM, Juergen Gross wrote:
>
>> On 26/07/17 15:48, Andy Lutomirski wrote:
>>> On Mon, Jul 24, 2017 at 7:28 AM, Juergen Gross wrote:
>>> When running as Xen pv-guest the exception frame on the stack contains
>>> %r11 and %rcx additional to the other data pushed by the
Em Wed, Jul 26, 2017 at 10:31:48AM -0700, Dan Williams escreveu:
> On Wed, Jul 26, 2017 at 10:19 AM, Ingo Molnar wrote:
> > * Dan Williams wrote:
> >> On Wed, Jul 26, 2017 at 4:29 AM, Ingo Molnar wrote:
> > which I could initially mistake for a commit about scheduler completions ;-)
> >
> > Or:
- On Jul 26, 2017, at 11:42 AM, Paul E. McKenney paul...@linux.vnet.ibm.com
wrote:
> On Wed, Jul 26, 2017 at 09:46:56AM +0200, Peter Zijlstra wrote:
>> On Tue, Jul 25, 2017 at 10:50:13PM +, Mathieu Desnoyers wrote:
>> > This would implement a MEMBARRIER_CMD_PRIVATE_EXPEDITED (or such)
On 7/26/2017 9:34 AM, Dou Liyang wrote:
Commit a7be6e5a7f8d ("mm: drop useless local parameters of
__register_one_node()") removes the last user of parent_node().
The parent_node() macro in tile platform is unnecessary.
Remove it for cleanup.
Reported-by: Michael Ellerman
Signed-off-by: Dou
This patch series addresses some issues found during further testing of
Secure Memory Encryption (SME).
The following fixes are included in this update series:
- Fix a cache-related memory corruption when kexec is invoked in
successive instances
- Remove the encryption mask from the protection
The function arch_apei_get_mem_attributes() is used to set the page
protection type for ACPI physical addresses. When SME is active, the
associated protection type needs to not have the encryption mask set
since the ACPI tables live in un-encrypted memory. Modify the
arch_apei_get_mem_attributes()
After issuing successive kexecs it was found that the SHA hash failed
verification when booting the kexec'd kernel. When SME is enabled, the
change from using pages that were marked encrypted to now being marked as
not encrypted (through new identify mapped page tables) results in memory
On Thu 29 Jun 07:17 PDT 2017, Sricharan R wrote:
> qcom_mdt_load function loads the mdt type firmware and
> authenticates it as well. Make the authentication only
> when requested by the caller, so that the function can be used
> by self-authenticating remoteproc as well.
>
This is good, we
On Wed, Jul 26, 2017 at 10:57 AM, Arnaldo Carvalho de Melo
wrote:
> Em Wed, Jul 26, 2017 at 10:31:48AM -0700, Dan Williams escreveu:
>> On Wed, Jul 26, 2017 at 10:19 AM, Ingo Molnar wrote:
>> > * Dan Williams wrote:
>> >> On Wed, Jul 26, 2017 at 4:29 AM, Ingo Molnar wrote:
>> > which I could
It'd be better to retry writing atomic pages when we get -ENOMEM.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index f964b68718c1..f5d139f897dc 100644
--- a/fs/f2fs/segment.c
Em Wed, 26 Jul 2017 17:27:12 +
"Luck, Tony" escreveu:
> > > > Hmm... I'm not seeing any implementation that would allow setting
> > > > between firmware first, hardware first or "auto", as we've discussed.
> > >
> > > This is all coming up. As the 0/3 message said, these 3 patches are the
>
On 07/25/2017 06:29 AM, Måns Rullgård wrote:
> Marc Gonzalez writes:
>
>> On 25/07/2017 15:16, Måns Rullgård wrote:
>>
>>> What happened to the patch adding the proper combined function?
>>
>> It appears you're not CCed on v2.
>>
>> https://patchwork.kernel.org/patch/9859799/
>>
>> Doug wrote:
On Wed, Jul 26, 2017 at 07:20:22AM -0700, Thomas Garnier wrote:
> On Wed, Jul 26, 2017 at 5:02 AM, Will Deacon wrote:
> > I looked to see what you've done for x86, but it looks like you check/clear
> > the flag before the work pending loop (exit_to_usermode_loop), which
> > subsequently
By the way Ding, two issues:
1. Did we ever get any acknowledgement from either Intel or AMD
on this patch? I know that we can't ensure that, but it sure would
be nice since the PCI Quirks that we're putting in affect their
products.
2. I just realized that there's still a small
Le Tue, 25 Jul 2017 14:00:21 +0200,
Alexander Dahl a écrit :
> Hello,
>
> this small patch series based on v4.13-rc2 fixes three things I found
> when trying to run the latest rc on an at91samg20 based platform with
> a SRAM like memory connected to the EBI interface, for which the
> timings
On Wed, Jul 26, 2017 at 11:25 AM, Russell King - ARM Linux
wrote:
> On Wed, Jul 26, 2017 at 07:20:22AM -0700, Thomas Garnier wrote:
>> On Wed, Jul 26, 2017 at 5:02 AM, Will Deacon wrote:
>> > I looked to see what you've done for x86, but it looks like you check/clear
>> > the flag before the
On 07/26/2017 12:05 PM, Oliver Hartkopp wrote:
> On 07/26/2017 06:41 PM, Andrew Lunn wrote:
>> On Mon, Jul 24, 2017 at 06:05:19PM -0500, Franklin S Cooper Jr wrote:
>
>>> +
>>> +Optional:
>>> + max-arbitration-speed: a positive non 0 value that determines the max
>>> +speed that CAN
On Wed, Jul 26, 2017 at 06:01:15PM +, Mathieu Desnoyers wrote:
> - On Jul 26, 2017, at 11:42 AM, Paul E. McKenney
> paul...@linux.vnet.ibm.com wrote:
>
> > On Wed, Jul 26, 2017 at 09:46:56AM +0200, Peter Zijlstra wrote:
> >> On Tue, Jul 25, 2017 at 10:50:13PM +, Mathieu Desnoyers
On Wednesday, July 26, 2017 03:53:11 PM Arnd Bergmann wrote:
> ACPI_VIDEO keeps causing problems with circular Kconfig dependencies,
> as it depends on a couple of other symbols, and it gets selected by
> drivers that may end up being depending on others.
>
> This is an attempt to simplify this
cap_inode_need_killpriv returns 1 if security.capability exists,
0 otherwise. Fix the description of the return value to reflect this.
Signed-off-by: Stefan Berger
---
security/commoncap.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/security/commoncap.c
On Sun, Jun 25, 2017 at 8:52 PM, Wu Hao wrote:
Hi Hao,
> This patch adds region_id to fpga_image_info data structure, it
> allows driver to pass region id information to fpga-mgr via
> fpga_image_info for fpga reconfiguration function.
>
> Signed-off-by: Wu Hao
> ---
>
On 07/20/2017 01:04 PM, David Miller wrote:
> From: Nitin Gupta
> Date: Thu, 13 Jul 2017 14:53:24 -0700
>
>> Testing:
>>
>> Tested with the stream benchmark which allocates 48G of
>> arrays backed by 16G hugepages and does RW operation on
>> them in parallel.
>
> It would be great if we
On Tue, Jul 25, 2017 at 10:20:50PM -0700, Palmer Dabbelt wrote:
> On Tue, 25 Jul 2017 19:57:17 PDT (-0700), j.neuschae...@gmx.net wrote:
> > On Tue, Jul 11, 2017 at 06:31:30PM -0700, Palmer Dabbelt wrote:
[...]
> >> +config ISA_C
> >> + bool "Emit compressed instructions when building Linux"
> >
On 26/07/17 19:57, Andy Lutomirski wrote:
>
>
>> On Jul 26, 2017, at 11:50 AM, Juergen Gross wrote:
>>
>>> On 26/07/17 15:48, Andy Lutomirski wrote:
On Mon, Jul 24, 2017 at 7:28 AM, Juergen Gross wrote:
When running as Xen pv-guest the exception frame on the stack contains
%r11
Hi,
In testing nowait aio on ext4, I found that when appending to a file
the return value is EAGAIN/EWOULDBLOCK, because as mentioned in the
commit this will potentially trigger an allocation. However, the EAGAIN,
seems somewhat misleading to me, in that if I continuously try the
write, it
On Wed, Jul 26, 2017 at 10:39:30AM -0700, Mike Kravetz wrote:
> In the overview of this RFC, I mentioned still needing to address the
> comment from Aneesh about splitting SHM_HUGE_* definitions into arch
> specific header files. This is how it is done for mmap. If an arch
> supports multiple
While CONFIG_FORTIFY_SOURCE continues to shake out, don't unconditionally
use BUG(), opting instead for WARN(). This also renames fortify_panic()
to fortify_overflow() which better matches what it is being called for.
Cc: Daniel Micay
Suggested-by: Linus Torvalds
Signed-off-by: Kees Cook
---
Hi,
On Tue, Jul 25, 2017 at 11:36 AM, Matthias Kaehlcke wrote:
> Apparently netpoll_setup() assumes that netpoll.dev_name is a pointer
> when checking if the device name is set:
>
> if (np->dev_name) {
> ...
>
> However the field is a character array, therefore the condition always
> yields
On 7/26/17 12:53 AM, Mike Rapoport wrote:
+
/*
* For non-cooperative userfaultfd test we fork() a process that will
* generate pagefaults, will mremap the area monitored by the
@@ -585,19 +598,54 @@ static int userfaultfd_open(int features)
* The release of the pages currently
On Friday, July 21, 2017 03:33:05 PM Frank Rowand wrote:
> On 07/21/17 15:03, Rafael J. Wysocki wrote:
> > On Thursday, July 20, 2017 12:13:24 PM frowand.l...@gmail.com wrote:
> >> From: Frank Rowand
> >>
> >> ACPI is impacted by changes to fwnode.h, add a file entry
> >> to ACPI
> >>
> >>
Commit 87b132bc0315 ("ASoC: samsung: s3c24{xx,12}-i2s: port to use
generic dmaengine API") moved ioremap() call from
s3c-i2s-v2.c:s3c_i2sv2_probe() to s3c2412-i2s.c:s3c2412_iis_dev_probe()
and converted it to devm- resource managed interface.
However the error path in first of them -
s3c2412_i2s_probe() might fail so driver has to revert work done by
s3c_i2sv2_probe() (clock enabling). Missing doing this would lead to
clock enable in-balance.
Signed-off-by: Krzysztof Kozlowski
---
Please, kindly test on S3C24xx hardware.
---
sound/soc/samsung/s3c-i2s-v2.c | 9 +
-Use devm_clk_get() to make cleanup paths more simple.
-clk_prepare_enable() can fail here and we must check its return value.
-Add s3c_i2sv2_remove cleanup function of s3c_i2sv2_probe.
-No need to iounmap. Here, mapping done by devm_ioremap_resource.
Signed-off-by: Arvind Yadav
---
On 2017-07-26 13:41, Eric Wheeler wrote:
On Wed, 26 Jul 2017, Pavel Machek wrote:
Hi!
Unfortunately, that would mean shifting 400GB data 8KB forward, and
compatibility problems. So I'd prefer adding bcache superblock into
the reserved space, so I can have caching _and_ compatibility with
On Sunday, July 23, 2017 12:14:27 AM Rafael J. Wysocki wrote:
> On Sun, Jul 23, 2017 at 12:13 AM, Andy Shevchenko
> wrote:
> > On Sun, Jul 23, 2017 at 1:02 AM, Rafael J. Wysocki
> > wrote:
> >> On Saturday, July 22, 2017 04:53:52 AM Andy Shevchenko wrote:
> >>> On Sat, Jul 22, 2017 at 1:25 AM,
On 7/26/17 7:27 AM, Andrea Arcangeli wrote:
On Tue, Jul 25, 2017 at 12:47:42AM -0400, Prakash Sangappa wrote:
Signed-off-by: Prakash Sangappa
---
tools/testing/selftests/vm/userfaultfd.c | 121 +-
1 files changed, 118 insertions(+), 3 deletions(-)
Like Mike
On Sunday, July 23, 2017 12:01:10 AM Rafael J. Wysocki wrote:
> On Saturday, July 22, 2017 07:59:54 AM Borislav Petkov wrote:
> > On Fri, Jul 21, 2017 at 11:24:37AM -0700, Loc Ho wrote:
> > > X-Gene platforms describe multiple GHES error sources with the same
> > > hardware
> > > error
| From: Alexander Duyck
| Sent: Wednesday, July 26, 2017 11:44 AM
|
| On Jul 26, 2017 11:26 AM, "Casey Leedom" wrote:
| |
| | I think that the patch will need to be extended to modify
| | drivers/pci.c/iov.c:sriov_enable() to explicitly turn off
| | Relaxed Ordering Enable if the
On Monday, July 24, 2017 06:30:46 PM Prakash, Prashanth wrote:
>
> On 7/24/2017 2:32 PM, Rafael J. Wysocki wrote:
> > On Friday, July 21, 2017 03:09:29 PM Hoan Tran wrote:
> >> When PCCT is not available, kernel crashes as below when requests PCC
> >> channel 0. This patch fixes this issue.
> >>
On Wednesday, July 26, 2017 01:03:03 PM Andy Shevchenko wrote:
> On Wed, 2017-07-26 at 02:27 +0200, Rafael J. Wysocki wrote:
> > On Wednesday, July 26, 2017 03:35:01 AM Andy Shevchenko wrote:
> > > On Wed, Jul 26, 2017 at 3:21 AM, Rafael J. Wysocki > > t> wrote:
>
> > > > Andy, do you want me to
On Thu 29 Jun 07:17 PDT 2017, Sricharan R wrote:
> IPQ8074 has an integrated Hexagon dsp core Q6v5 and a wireless lan
> (Lithium) IP. This patch adds the remoteproc driver to reset, load
> and boot Q6 firmware.
>
There is a fair amount of code in this driver that seems to be
equivalent to
On Wed, Jul 26, 2017 at 04:46:40PM +0200, Arnd Bergmann wrote:
> I only saw these warnings once, they are either very rare, or were introduced
> recently:
>
> arch/x86/kvm/vmx.o: warning: objtool: .altinstr_replacement+0x0:
> unreachable instruction
> arch/x86/kvm/svm.o: warning: objtool:
On Thu, Jul 27, 2017 at 12:28:52AM +0530, Arvind Yadav wrote:
> -Use devm_clk_get() to make cleanup paths more simple.
> -clk_prepare_enable() can fail here and we must check its return value.
> -Add s3c_i2sv2_remove cleanup function of s3c_i2sv2_probe.
> -No need to iounmap. Here, mapping done by
1601 - 1700 of 1946 matches
Mail list logo