Andy Shevchenko writes:
> On Mon, 2015-12-21 at 15:19 -0400, Julian Margetson wrote:
>> On 12/21/2015 2:27 PM, Måns Rullgård wrote:
>> > The hard drive is recognized .
>> > > These system gets unresponsive with USB devices like the mouse
>> > > and
>> > > keyboard not responding when I start Gpa
Commit 3759824da87b30ce7a35b4873b62b0ba38905ef5 (tcp: PRR uses CRB mode by
default and SS mode conditionally) introduced changes to net/ipv4/tcp_input.c
tcp_cwnd_reduction() that, possibly, cause division by zero, and therefore,
kernel panic in interrupt handler [1].
Reverting 3759824da87b30ce7
On Tue, Dec 15, 2015 at 1:36 PM, Michal Hocko wrote:
> From: Michal Hocko
>
> This is based on the idea from Mel Gorman discussed during LSFMM 2015 and
> independently brought up by Oleg Nesterov.
>
[...]
Since this is built-in always, can we
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
>
> Roman Volkov mail.ru> writes:
>
> >
> > From: Roman Volkov v1ros.org>
> >
> > vt8500 timer requires special synchronization for accessing some of
> > its registers. Define special read and write functions to handle
> > this process transparently.
>
> Maybe introduce such accessor functions
On Mon, 2015-12-21 at 18:17 +, Mans Rullgard wrote:
> This lock is already taken in ata_scsi_queuecmd() a few levels up the
> call stack so attempting to take it here is an error. Moreover, it
> is
> pointless in the first place since it only protects a single, atomic
> assignment.
>
> Enabli
Hi Julia,
Thank you for the patch.
On Monday 21 December 2015 17:39:46 Julia Lawall wrote:
> for_each_child_of_node performs an of_node_get on each iteration, so a
> goto out of the loop requires an of_node_put.
>
> A simplified version of the semantic patch that fixes this problem is as
> follo
2162.709998] CPU: 4 PID: 28801 Comm: trinity-c375 Tainted: GB
4.4.0-rc5-next-20151221-sasha-00020-g840272e-dirty #2753
[ 2162.711847] f17e6fcd 880292d5fe08
a4045334
[ 2162.713108] 41b58ab3 af66686b a4045289
8802
From: Tadeusz Struk
Created on top of patchset from Stephan Mueller
https://patchwork.kernel.org/patch/7877921/
https://patchwork.kernel.org/patch/7877971/
https://patchwork.kernel.org/patch/7877961/
This patch adds support for asymmetric key type to AF_ALG.
It will work as follows: A new PF_AL
On Mon, 2015-12-21 at 19:27 +, Måns Rullgård wrote:
> Andy Shevchenko writes:
>
> > On Mon, 2015-12-21 at 01:19 +, Måns Rullgård wrote:
> > > Andy Shevchenko writes:
> > >
> > > > P.S. I also noticed that original driver enables interrupt per
> > > > each
> > > > block
> > >
> > > And
Hi,
On 12/19/2015 03:49 PM, kbuild test robot wrote:
> Hi Tadeusz,
>
> [auto build test ERROR on crypto/master]
> [also build test ERROR on v4.4-rc5 next-20151218]
>
> url:
> https://github.com/0day-ci/linux/commits/Tadeusz-Struk/crypto-KEYS-convert-public-key-to-akcipher-api/20151213-103429
On 21 December 2015 at 18:11, Andy Shevchenko wrote:
> On Mon, Dec 21, 2015 at 4:49 PM, Aleksey Makarov
> wrote:
>> From: Graeme Gregory
>>
>> In ACPI this device is only defined in SBSA mode so
>> if we are coming from ACPI use this mode.
>>
>> Signed-off-by: Graeme Gregory
>> Signed-off-by: A
Andy Shevchenko writes:
>> > 4. CHECK: PROTCTL bit (documentation says that recommended value is
>> > 0x01)
>>
>> Any idea what the value of 0x3 used by the old sata driver means?
>> Presumably that's decided by the bus.
>
> Nope, documentation says that it is direct representation of hprot[3:1]
On 12/21/2015 03:28 PM, Sasha Levin wrote:
> On 12/21/2015 08:08 AM, Christoph Lameter wrote:
>> > On Fri, 18 Dec 2015, Sasha Levin wrote:
>> >
>> > [ 531.164630] RIP vmstat_update (mm/vmstat.c:1408)
>> > Hmmm.. Yes we need to fold the diffs first before disabling the timer
>> > otherwise th
Hello, again.
On Mon, Dec 21, 2015 at 03:07:21PM -0500, Tejun Heo wrote:
> Hello, Artem.
>
> Can you please apply the following patch on top and see whether
> anything changes? If it does make the issue go away, can you please
> revert the ".can_queue" part and test again?
If the patch doesn't
On Tue, Dec 15, 2015 at 04:27:28PM -0800, K. Y. Srinivasan wrote:
>
> Signed-off-by: K. Y. Srinivasan
No changelog text? Sorry, I can't take this :(
You know better...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.o
On 21 December 2015 at 18:19, Andy Shevchenko wrote:
> On Mon, Dec 21, 2015 at 6:41 PM, Aleksey Makarov
> wrote:
>> From: Graeme Gregory
>>
>> On ARM64 some devices use the AMBA device and not the platform bus for
>> probing so add support for this. Uses a dummy clock for apb_pclk as ACPI
>> doe
On Mon, 21 Dec 2015, Sasha Levin wrote:
> I've also noticed a new warning from the workqueue code which my scripts
> didn't pick up before:
>
> [ 3462.380681] BUG: workqueue lockup - pool cpus=2 node=2 flags=0x4 nice=0
> stuck for 54s!
> [ 3462.522041] workqueue vmstat: flags=0xc
> [ 3462.527795]
On Thu, Dec 17, 2015 at 03:51:29PM -0800, K. Y. Srinivasan wrote:
> Add vendor and device attributes to VMBUS devices. These will be used
> by Hyper-V tools as well user-level RDMA libraries that will use the
> vendor/device tuple to discover the RDMA device.
>
> Signed-off-by: K. Y. Srinivasan
>
On 12/21/2015 6:56 AM, Caesar Wang wrote:
> Add the description for rt5616 codec.
>
> Signed-off-by: Caesar Wang
>
> ---
>
> Changes in v1:
> - As Heiko comments, remove the not exist option properties.
>
> Documentation/devicetree/bindings/sound/rt5616.txt | 36
> ++
> 1
Hi Julia,
Am Montag, 21. Dezember 2015, 17:39:47 schrieb Julia Lawall:
> for_each_child_of_node performs an of_node_get on each iteration, so a
> return from the loop requires an of_node_put.
>
> A simplified version of the semantic patch that fixes this problem is as
> follows (http://coccinelle
On Mon, Dec 21, 2015 at 12:46:51AM +0300, Alexey Khoroshilov wrote:
> If hif_read_reg() or hif_write_reg() fail in wilc_wlan_cleanup(),
> it calls release_bus() and continues execution. But it leads to double
> release_bus() call that means double unlock of g_linux_wlan->hif_cs mutex.
>
> Found by
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Monday, December 21, 2015 1:10 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com
> Subj
> Since early in the 4.3-rcx series, my Dell Latitude D600 with a 32-bit kernel
> fails to boot. Unfortunately, I did not discover this until late in the
> 4.4-rcX
> cycle. The symptom is that the kernel echos the "Loading initial ramdisk ..."
> message and then hangs.
>
> The problem was bisecte
I am announcing the release of the Linux 3.13.11-ckt32 kernel.
The updated 3.13.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.13.y
and can be browsed at:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.13.y
The diff from v3.13.11-ckt31 is posted
diff --git a/Makefile b/Makefile
index 7606094..4267a0d 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 3
PATCHLEVEL = 13
SUBLEVEL = 11
-EXTRAVERSION = -ckt31
+EXTRAVERSION = -ckt32
NAME = King of Alienated Frog Porn
# *DOCUMENTATION*
@@ -597,10 +597,24 @@ ifneq ($(CONFIG_FRAM
Am Montag, 21. Dezember 2015, 12:51:07 schrieb Tadeusz Struk:
Hi Tadeusz,
> From: Tadeusz Struk
>
> Created on top of patchset from Stephan Mueller
> https://patchwork.kernel.org/patch/7877921/
> https://patchwork.kernel.org/patch/7877971/
> https://patchwork.kernel.org/patch/7877961/
>
> Thi
From: Markus Elfring
Date: Mon, 21 Dec 2015 22:24:18 +0100
Another update suggestion was taken into account after a patch was applied
from static source code analysis.
Markus Elfring (2):
Change return type of cpu_set_cclk() to that of clk_set_rate()
Mark cpu_set_cclk() as static
drivers/c
From: Markus Elfring
Date: Mon, 21 Dec 2015 21:56:27 +0100
The return type "unsigned long" was used by the cpu_set_cclk() function
while the type "int" is provided by the clk_set_rate() function.
Let us make this usage consistent.
This issue was detected by using the Coccinelle software.
Signed
From: Markus Elfring
Date: Mon, 21 Dec 2015 22:12:26 +0100
The cpu_set_cclk() function was only used in a single source file so far.
Indicate this setting also by the corresponding linkage specifier.
Signed-off-by: Markus Elfring
Acked-by: Viresh Kumar
---
drivers/cpufreq/blackfin-cpufreq.c |
Am Donnerstag, 17. Dezember 2015, 13:56:12 schrieb Dmitry Vyukov:
Hi Dmitry,
> Hello,
>
> The following program triggers use-after-free in skcipher_sock_destruct:
This issue is not evident after applying Herbert's patch converting the
algif_skcipher from using ablkcipher to skcipher API.
>
>
On Mon, Dec 21, 2015 at 07:14:43PM +0800, Dongsheng Yang wrote:
> Sometimes, cpuacct.usage is not detialed enough to user
> to see how much usage a group used. We want to know how
> much time it used in user mode and how much in kernel mode.
cpuusage is being phased out. If you need these stats,
On Wed, Nov 25, 2015 at 11:59:37AM -0800, Jin Qian wrote:
> From: Greg Hackmann
>
> Signed-off-by: Greg Hackmann
> (cherry picked from commit 3c56d07eb796066530e93a40e74dea3bc59bf4cf)
What is this commit id here for?
confused,
greg k-h
--
To unsubscribe from this list: send the line "unsubscr
Cleanup vmbus_set_event() by inlining the hypercall to post
the event and since the return value of vmbus_set_event() is not checked,
make it void. As part of this cleanup, get rid of the function
hv_signal_event() as it is only callled from vmbus_set_event().
Signed-off-by: K. Y. Srinivasan
---
On 12/21/2015 4:41 PM, Andy Shevchenko wrote:
On Mon, 2015-12-21 at 18:17 +, Mans Rullgard wrote:
This lock is already taken in ata_scsi_queuecmd() a few levels up the
call stack so attempting to take it here is an error. Moreover, it
is
pointless in the first place since it only protects a
On Fri, Nov 20, 2015 at 03:35:34PM +0530, Shivnandan Kumar wrote:
> When a driver register as a misc driver and
> it tries to allocate minor number dynamically.
> Then there is a chance of minor number overflow.
> The problem is that 64(DYNAMIC_MINORS) is not enough
> for dynamic minor numb
On Sat, Dec 19, 2015 at 03:34:45PM +0200, Nikolay Borisov wrote:
> Ping as Tejun might have missed this email. I'm also interested in knowing
> the logic behind the comment.
Didn't I already reply to that?
http://thread.gmane.org/gmane.linux.kernel/2104051
--
tejun
--
To unsubscribe from this l
On Mon, Dec 21, 2015 at 4:44 PM, Tejun Heo wrote:
> On Sat, Dec 19, 2015 at 03:34:45PM +0200, Nikolay Borisov wrote:
>> Ping as Tejun might have missed this email. I'm also interested in knowing
>> the logic behind the comment.
>
> Didn't I already reply to that?
>
> http://thread.gmane.org/gmane.
On Mon, 21 Dec 2015 20:45:23 +0900 Tetsuo Handa
wrote:
> >
> > And it would be helpful to add a comment to hung_timeout_jiffies()
> > which describes the behaviour and explains the reasons for it.
>
> But before doing it, I'd like to confirm hung task maintainer's will.
>
> The reason I propos
On Wednesday, December 16, 2015 11:23:19 AM Steve Grubb wrote:
> On Wednesday, December 16, 2015 10:42:32 AM Richard Guy Briggs wrote:
> > Nothing prevents a new auditd starting up and replacing a valid
> > audit_pid when an old auditd is still running, effectively starving out
> > the old auditd s
This brings SECCOMP_MODE_STRICT and SECCOMP_MODE_FILTER support through
prctl(2) and seccomp(2) to User-mode Linux for i386 and x86_64
subarchitectures.
secure_computing() is called first in handle_syscall() so that the
syscall emulation will be aborted quickly if matching a seccomp rule.
This is
I am announcing the release of the Linux 3.19.8-ckt12 kernel.
The updated 3.19.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.19.y
and can be browsed at:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.19.y
The diff from v3.19.8-ckt11 is posted as
diff --git a/Makefile b/Makefile
index d160d27..921cb4a 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 3
PATCHLEVEL = 19
SUBLEVEL = 8
-EXTRAVERSION = -ckt11
+EXTRAVERSION = -ckt12
NAME = Sedated Swine
# *DOCUMENTATION*
diff --git a/arch/arc/kernel/unwind.c b/arch/arc/kernel/u
On Mon, Dec 21, 2015 at 1:23 PM, Souptick Joarder wrote:
> Hi Brent,
>
> On Tue, Dec 1, 2015 at 11:11 AM, Brent Taylor wrote:
>> Since commit 8437754c83351d6213c1a47ff029c1126d6042a7, ar->fw is expected to
>> be pointing to memory allocated by vmalloc. If the api1 method (via
>> ath6kl_fetch_f
On Mon, Dec 21, 2015 at 12:10 AM, Jon Masters wrote:
> On 12/2/15, 6:55 PM, John Stultz wrote:
>>
>> On Wed, Dec 2, 2015 at 3:42 PM, Andy Lutomirski wrote:
>
>
On a hunch, are you running chrony instead of ntpd?
>>>
>>>
>>> Yes, this is indeed chrony.
>>
>>
>> Ok. I'll have to look closer. T
Hello, Alex.
On Fri, Dec 18, 2015 at 08:08:03PM +, Alex Ng (LIS) wrote:
> Hi,
>
> I was running a "git clone" of the linux-next source tree and hit the
> following BUG_ON condition. My box is running kernel
> 4.4.0-rc5-next-20151217-52.27. Any ideas on how to pin down the cause?
>
> The tr
On Thu, Dec 17, 2015 at 11:33 AM, Luis R. Rodriguez wrote:
> Please no, instead of adding yet-another kernel file-loading facility which is
> likely error prone we should consolidate *all kernel file-loading facilities*
> into a *common generic shared one*. So please work to make that happen since
On Monday 21 December 2015, Laura Abbott wrote:
> ARM no longer uses bootmem, just memblock (see
> 84f452b1e8fc73ac0e31254c66e3e2260ce5263d
> ARM: mm: Remove bootmem code and switch to NO_BOOTMEM). Any bootmem calls
> just go to mm/nobootmem.c which is a wrapper around memblock for
> compatibilit
> On Thu, Dec 17, 2015 at 12:01:17PM -0500, Sinan Kaya wrote:
>> Add documentation for the Qualcomm Technologies HIDMA driver.
>>
>> Signed-off-by: Sinan Kaya
>> ---
>> .../devicetree/bindings/dma/qcom_hidma_mgmt.txt| 79
>> ++
>> 1 file changed, 79 insertions(+)
>> creat
Dongsheng Yang writes:
> On 12/20/2015 05:47 PM, Eric W. Biederman wrote:
>> Dongsheng Yang writes:
>>
>>> On 12/20/2015 10:37 AM, Al Viro wrote:
On Sun, Dec 20, 2015 at 10:14:29AM +0800, Dongsheng Yang wrote:
> On 12/17/2015 07:23 PM, Dongsheng Yang wrote:
>> Hi guys,
>>
Hello.
On 11/17/2015 06:19 AM, Magnus Damm wrote:
From: Magnus Damm
Add missing r8a7794 DU dot clock output signals and in
particular the DU1_DOTCLKOUT0 signal on GP4_25 which is
needed by DU1 on the r8a7794 ALT board.
The groups "du0_clk_out" and "du1_clk_out" are replaced by
"du0_dotclkout
> Hi Sinan,
>
> [auto build test ERROR on v4.4-rc5]
> [also build test ERROR on next-20151218]
>
> url:
> https://github.com/0day-ci/linux/commits/Sinan-Kaya/dma-add-Qualcomm-Technologies-HIDMA-driver/20151218-010637
> config: sparc64-allmodconfig (attached as .config)
> reproduce:
> wget
>
On Sat, Dec 19, 2015 at 12:37 PM, Andy Shevchenko
wrote:
>> +static int __init hidma_mgmt_of_populate_channels(struct device_node *np)
>> +{
>> + struct platform_device *pdev_parent = of_find_device_by_node(np);
>> + struct platform_device_info pdevinfo;
>> + struct of_phandle_ar
On Sun, Nov 08, 2015 at 11:34:59AM -0500, James Simmons wrote:
> We need cfs_str2mask exported for our server code.
> Even with the server code not available upstream
> it would be nice to use the upstream code on Lustre
> servers.
Nope, sorry, we don't export symbols for any non-in-tree users, th
On Fri, Nov 27, 2015 at 04:31:39AM +, Dilger, Andreas wrote:
> On 2015/11/08, 09:34, "James Simmons" wrote:
>
> >The ioctl IOC_LIBCFS_PING_TEST has not been used in
> >ages. The recent nidstring changes which moved all
> >the nidstring operations from libcfs to the LNet
> >layer but this ioct
Hi Brent and Souptick,
On 12/21/15, 2:23 PM, "ath6kl on behalf of Souptick Joarder"
wrote:
>Hi Brent,
>
>On Tue, Dec 1, 2015 at 11:11 AM, Brent Taylor wrote:
>> Since commit 8437754c83351d6213c1a47ff029c1126d6042a7, ar->fw is expected to
>> be pointing to memory allocated by vmalloc. If t
On Mon, 21 Dec 2015 00:43:17 +0800 kbuild test robot
wrote:
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: 69c37a92ddbf79d9672230f21a04580d7ac2f4c3
> commit: 71458cfc782eafe4b27656e078d379a34e472adf ke
On Sun, Nov 08, 2015 at 11:34:55AM -0500, James Simmons wrote:
> For UMP and SMP machines the struct cfs_cpt_table are
> defined differently. In the case handled by this patch
> nodemask is defined as a integer for the UMP case and
> as a pointer for the SMP case. This will cause a problem
> for os
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Monday, December 21, 2015 1:15 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com
> Subj
ebied...@xmission.com (Eric W. Biederman) writes:
> "H. Peter Anvin" writes:
>
>> Does it matter if it mounts devpts twice? It seems like a waste of a
>> minuscule amount of memory, and nothing else.
> It breaks system("mknod /tmp/ptmx c 5 2"); open("/tmp/ptmx");
Correction.
It does break the
On Monday 21 December 2015, Dr. Philipp Tomsich wrote:
>
> > On 18 Dec 2015, at 13:47, Arnd Bergmann wrote:
> >
> >> 3. Follow the PCS up to glibc but always pass syscall arguments in W
> >> registers, like AArch32 compat support (the least preferred option,
> >> the only advantage is a sing
Hi Arnd,
On Mon, 21 Dec 2015 14:49:29 +0100 Arnd Bergmann wrote:
>
> Orangefs fails to build on 32-bit SMP configurations due to a simple
> misspelling, this does the obvious fix.
>
> Signed-off-by: Arnd Bergmann
> Fixes: 575e946125f7 ("Orangefs: change pvfs2 filenames to orangefs")
I will add
On Monday, December 21, 2015 04:48:00 PM Paul Moore wrote:
> On Wednesday, December 16, 2015 11:23:19 AM Steve Grubb wrote:
> > On Wednesday, December 16, 2015 10:42:32 AM Richard Guy Briggs wrote:
> > > Nothing prevents a new auditd starting up and replacing a valid
> > > audit_pid when an old aud
On Mon, Dec 21, 2015 at 2:06 PM, Greg Kroah-Hartman
wrote:
>
> No one told me it fixed a bug, let me see if it's still even needed...
You were definitely cc'd on a couple of the threads..
But it's done now (well, two weeks ago), I applied it as commit
d035e336287b ("staging/lustre: remove IOC_LI
On Monday 21 December 2015, Catalin Marinas wrote:
> On Fri, Dec 18, 2015 at 01:47:55PM +0100, Arnd Bergmann wrote:
> > On Friday 18 December 2015 11:42:19 Catalin Marinas wrote:
> > > 2. Follow the PCS up to glibc and get glibc to zero the top part (not
> > >always safe with hand-written assem
On Mon, Dec 21, 2015 at 02:18:18PM -0800, Linus Torvalds wrote:
> On Mon, Dec 21, 2015 at 2:06 PM, Greg Kroah-Hartman
> wrote:
> >
> > No one told me it fixed a bug, let me see if it's still even needed...
>
> You were definitely cc'd on a couple of the threads..
>
> But it's done now (well, two
On Mon, Dec 21, 2015 at 2:03 PM, Eric W. Biederman
wrote:
>
> What actually breaks is "echo NNN > /proc/sys/kernel/pty/reserve"
> Which allows the primary instance of devpts to have access to more
> ptys than any other instance.
Ok. We'll probably need to fix that similarly (make it look up
/dev/
On Sat, 19 Dec 2015 17:03:15 -0500 Sasha Levin wrote:
> On 12/19/2015 02:52 PM, Kirill A. Shutemov wrote:
> > On Fri, Dec 18, 2015 at 08:04:51PM -0500, Sasha Levin wrote:
> >> > Commit "mm, oom: introduce oom reaper" forgot to initialize the two new
> >> > fields
> >> > of struct zap_details in
Hi all,
I will be taking a break over Christmas, so that tomorrow will be the
last linux-next release until Jan 4 - unless I get really bored :-) If
Linus sticks to his normal release schedule, he will do a release on
Jan 3, so tomorrow will be the last linux-next release before the v4.5
merge wi
Hi Stephan,
On 12/21/2015 01:27 PM, Stephan Mueller wrote:
>> @@ -192,7 +194,30 @@ static int alg_setkey(struct sock *sk, char __user
>> > *ukey, if (copy_from_user(key, ukey, keylen))
>> >goto out;
>> >
>> > - err = setkey(ask->private, key, keylen);
>> > + if (key_id) {
> Wouldn't
On Tuesday 15 December 2015, Yury Norov wrote:
> +
> +#define compat_sys_open_by_handle_at sys_open_by_handle_at
> +#define compat_sys_openat sys_openat
> +
One more thing I just remembered: I think we want this behavior for all new
32-bit architectures, it was a bug to call compat_
On Monday, December 21, 2015 05:18:15 PM Steve Grubb wrote:
> On Monday, December 21, 2015 04:48:00 PM Paul Moore wrote:
> > On Wednesday, December 16, 2015 11:23:19 AM Steve Grubb wrote:
> > > On Wednesday, December 16, 2015 10:42:32 AM Richard Guy Briggs wrote:
> > > > Nothing prevents a new audi
On Monday 21 December 2015, ok...@codeaurora.org wrote:
> Thanks, I won't be touching the acpi tables then and I will assume the
> hack had a problem. It was trying to remap the io range of the second root
> port to the first port io address map.
If all domains share the same I/O space, you shoul
On Monday 21 December 2015, David Daney wrote:
> On 12/21/2015 06:10 AM, Arnd Bergmann wrote:
> > On Monday 21 December 2015, Gabriele Paoloni wrote:
>
> > or require the BIOS to work around the hardware
> > quirks differently (e.g. by trapping config space access through secure
> > firmware, or g
ile switching context
tracking on a runtime. (Can you even do that?)
--Andy
>
> [ 2162.706868] [ cut here ]
> [ 2162.708021] WARNING: CPU: 4 PID: 28801 at arch/x86/entry/common.c:44
> enter_from_user_mode+0x1c/0x50()
> [ 2162.709466] Modules linked in:
>
On 12/21/2015 03:24 PM, Busch, Keith wrote:
Since early in the 4.3-rcx series, my Dell Latitude D600 with a 32-bit kernel
fails to boot. Unfortunately, I did not discover this until late in the 4.4-rcX
cycle. The symptom is that the kernel echos the "Loading initial ramdisk ..."
message and then
On Mon, Dec 21, 2015 at 9:54 AM, Laura Abbott wrote:
> On 12/20/2015 04:20 AM, Andy Lutomirski wrote:
>>
>> I hit this warning fairly frequently when resuming 4.4-rc5:
>>
>> ret = usermodehelper_read_trylock();
>> if (WARN_ON(ret)) {
>> dev_err(device, "firmware: %s
Am Donnerstag, 17. Dezember 2015, 14:00:23 schrieb Dmitry Vyukov:
Hi Herbert,
After digging a bit here, I find the following:
- When using the test app on my system, I get a GPF in twofish, which means
that the problem is not tied to a particular cipher implementation.
- When analyzing gf128mu
On Tue, Dec 22, 2015 at 3:35 AM, Tejun Heo wrote:
>
>> [ 74.367632] XXX cmd=ee9e0260 cmd_tbl=ee9ed600 ahci_sg=ee9ed680
>> [ 74.367634] XXX opts=140005 st=0 addr=2e9ed600 addr_hi=0 rsvd=0:0:0:0
>> [ 74.367637] XXX fis=00608027:40218900:0704:0898
>> :::1fff
Am Donnerstag, 17. Dezember 2015, 14:00:23 schrieb Dmitry Vyukov:
Hi Dmitry,
> Hello,
>
> The following program causes GPF in gf128mul_64k_bbe:
This looks very much like the issue you reported for lrw_crypt.
>
> // autogenerated by syzkaller (http://github.com/google/syzkaller)
> #include
> #
On Dec 22, 2015 2:04 AM, "Dave Hansen" wrote:
>
> On 12/18/2015 03:16 PM, Andy Lutomirski wrote:
> > Hrm. We might also want an option to change pkru and/or baseline_pkru
> > in all threads in the current mm. That's optional but it could be
> > handy. Maybe it would be as simple as having the a
Am Montag, 21. Dezember 2015, 23:53:14 schrieb Stephan Mueller:
Hi,
> Am Donnerstag, 17. Dezember 2015, 14:00:23 schrieb Dmitry Vyukov:
>
> Hi Dmitry,
>
> > Hello,
>
> > The following program causes GPF in gf128mul_64k_bbe:
> This looks very much like the issue you reported for lrw_crypt.
Oop
inelle/api/alloc/kzalloc-simple.cocci)
>
> Patch was compile tested with: x86_64_defconfig +
> CONFIG_WL12XX=m (implies CONFIG_WLCORE=m)
>
> Patch is against linux-next (localversion-next is -next-20151221)
>
> drivers/net/wireless/ti/wlcore/main.c | 3 +--
> 1 file changed,
Am Donnerstag, 17. Dezember 2015, 13:59:11 schrieb Dmitry Vyukov:
Hi Dmitry,
> Hello,
>
> The following program causes GPF in lrw_crypt:
Here we are: this problem looks very much like the error reprt about a GFP in
gf128mul_64_bbe.
>
> // autogenerated by syzkaller (http://github.com/google/s
On 12/21/2015 02:52 PM, Andy Lutomirski wrote:
> Perhaps this is silly, but what if the default were changed to deny
> reads and writes for unallocated keys? Is there a use case that
> breaks?
It's probably a reasonable debugging feature.
But, anything that takes an XSAVE feature out of its "ini
On Mon, Dec 21, 2015 at 10:48:22AM -0500, Luiz Capitulino wrote:
> On Sat, 19 Dec 2015 22:57:30 -0200
> Marcelo Tosatti wrote:
>
> > On Sat, Dec 19, 2015 at 11:42:57AM +0100, Thomas Gleixner wrote:
> > > On Thu, 17 Dec 2015, Fenghua Yu wrote:
> > >
> > > > From: Fenghua Yu
> > > >
> > > > From
On Mon, Dec 21, 2015 at 3:00 PM, Dave Hansen
wrote:
> On 12/21/2015 02:52 PM, Andy Lutomirski wrote:
>> Perhaps this is silly, but what if the default were changed to deny
>> reads and writes for unallocated keys? Is there a use case that
>> breaks?
>
> It's probably a reasonable debugging featur
This text refers to the "first 7 functions", which was correct when
written but became incorrect when Johannes Weiner added another function
to the list in 139e561660fe ("lib: radix_tree: tree node interface").
Remove the sentence because it doesn't add any additional information
and would need to
On 12/18/2015 02:28 PM, Andy Lutomirski wrote:
...
>> I could imagine that some kernel person would want to use even more
>> keys, but I think two fixed keys are kind of the minimal we'd want to
>> use.
>
> I imagine we'd reserve key 0 for normal page and key 1 for deny-read.
> Let me be a bit mor
On 12/21/2015 03:02 PM, Andy Lutomirski wrote:
> On Mon, Dec 21, 2015 at 3:00 PM, Dave Hansen
> wrote:
>> On 12/21/2015 02:52 PM, Andy Lutomirski wrote:
>>> Perhaps this is silly, but what if the default were changed to deny
>>> reads and writes for unallocated keys? Is there a use case that
>>>
On Monday 21 December 2015, Bjorn Andersson wrote:
> I disagree with this "recommendation" as it's only outcome will be asymmetry.
>
> I think this script should be changed to only warn if there's a single
> IS_ERR/PTR_ERR at the end of the function, not if there's a list of
> them and this would
On Mon, 21 Dec 2015 11:13:15 +0100 Vitaly Kuznetsov wrote:
> Andrew Morton writes:
>
> > On Fri, 18 Dec 2015 15:50:24 +0100 Vitaly Kuznetsov
> > wrote:
> >
> >> Out of memory condition is not a bug and while we can't add new memory in
> >> such case crashing the system seems wrong. Propagatin
On Mon, Dec 21, 2015 at 3:04 PM, Dave Hansen
wrote:
> On 12/18/2015 02:28 PM, Andy Lutomirski wrote:
> ...
>>> I could imagine that some kernel person would want to use even more
>>> keys, but I think two fixed keys are kind of the minimal we'd want to
>>> use.
>>
>> I imagine we'd reserve key 0 f
Alexander Aring writes:
> On Fri, Dec 18, 2015 at 11:08:26AM +0100, Alexander Aring wrote:
> ...
>> Uncompressing Linux... done, booting the kernel.
>> [0.00] Booting Linux on physical CPU 0x0
>> [0.00] Initializing cgroup subsys cpuset
>> [0.00] Initializing cgroup subsys
Alexander Aring writes:
> Hi Eric,
>
> On Wed, Dec 16, 2015 at 03:55:11PM -0800, Eric Anholt wrote:
>> The set of peripherals remained constant across bcm2835 (Raspberry Pi
>> 1) and bcm2836 (Raspberry Pi 2), but the CPU was swapped out. Split
>> the files so that we can include just peripheral
On Sunday 20 December 2015, Alexander Aring wrote:
> On Fri, Dec 18, 2015 at 11:08:26AM +0100, Alexander Aring wrote:
> > [0.00] Memory policy: Data cache writeback
> > [0.00] BUG: mapping for 0x3f201000 at 0xf0201000 out of vmalloc
> > space
This is a separate bug, right?
> > [
Sorry for top-posting. A quick note that SMBIOS3 is required by SBBR so it can
be presumed that compliant platforms will provide quirks via DMI.
--
Computer Architect | Sent from my 64-bit #ARM Powered phone
> On Dec 21, 2015, at 09:11, Arnd Bergmann wrote:
>
> On Monday 21 December 2015, Gab
Instead of integrating the iAMT watchdog within the mei core driver
we will create a watchdog device on the mei client bus and
create a proper watchdog driver for it.
V3:
1. Rrevert to dynamically alocated watchdog device wrapper
2. Export activation state to via debugfs
3. Move runtime unregistra
From: Alexander Usyskin
For Intel Broadwell and newer platforms, the ME device can inform
the host whether the watchdog functionality is activated or not.
If the watchdog functionality is not activated then the watchdog interface
can be not registered and eliminate unnecessary pings and hence low
Add entry for dumping current watchdog internal state
Signed-off-by: Tomas Winkler
---
V2: new in the series
V3: rebase
drivers/watchdog/mei_wdt.c | 88 ++
1 file changed, 88 insertions(+)
diff --git a/drivers/watchdog/mei_wdt.c b/drivers/watchdog/me
From: Alexander Usyskin
For Intel SKL platform the ME device can inform the host via
asynchronous notification that the watchdog feature was activated
on the device. The activation doesn't require reboot.
In that case the driver registers the watchdog device with the kernel.
Signed-off-by: Alexa
401 - 500 of 854 matches
Mail list logo
