On Fri, Aug 17, 2018 at 5:08 PM Venkata Narendra Kumar Gutta
wrote:
>
> Currently, boradcast base is set to end of the LLCC banks, which may
s/boradcast/broadcast/
> not be correct always. As the number of banks may vary for each chipset
> and the broadcast base could be at a different address a
Perf can record user stack data in response to a synchronous request, such
as a tracepoint firing. If this happens under set_fs(KERNEL_DS), then we
end up reading user stack data using __copy_from_user_inatomic() under
set_fs(KERNEL_DS). I think this conflicts with the intention of using
set_fs(KER
On Thu, 23 Aug 2018 14:29:34 +0200
Martin Liška wrote:
> The patch changes interpretation of:
> callq *0x8(%rbx)
>
> from:
> 0.26 │ → callq *8
> to:
> 0.26 │ → callq *0x8(%rbx)
>
> in this can an address is followed by a register, thus
> one can't parse only address.
>
> Signed-
Hi
On 07/31/2018 05:52 PM, Frederic Weisbecker wrote:
> Before updating the full nohz tick or the idle time on IRQ exit, we
> check first if we are not in a nesting interrupt, whether the inner
> interrupt is a hard or a soft IRQ.
>
> There is a historical reason for that: the dyntick idle mode u
On Fri, 24 Aug 2018, Tetsuo Handa wrote:
> > For those of us who are tracking CVE-2016-10723 which has peristently been
> > labeled as "disputed" and with no clear indication of what patches address
> > it, I am assuming that commit 9bfe5ded054b ("mm, oom: remove sleep from
> > under oom_lock")
Hi all,
Today's linux-next merge of the mips tree got a conflict in:
include/linux/compiler_types.h
between commit:
815f0ddb346c ("include/linux/compiler*.h: make compiler-*.h mutually
exclusive")
from Linus' tree and commit:
04f264d3a8b0 ("compiler.h: Allow arch-specific asm/compiler.
Nick Desaulniers wrote on Thu, Aug 23, 2018:
> > On a side note, I noticed tools/include/linux/compiler.h includes
> > linux/compiler-gcc.h but maybe it should include linux/compiler_types.h?
> > (I'm not sure at who uses that header, so it really is an open question
> > here)
>
> Without looking
On Thu, Aug 23, 2018 at 10:05:20PM +0200, Michal Hocko wrote:
> On Thu 23-08-18 12:38:33, Andi Kleen wrote:
> > > There are people who care about L1TF mitigations. I am not going to
> > > question their motivation. In any case a hint how to make the mitigation
> > > active again sounds more useful
On 8/23/18 3:56 PM, Kees Cook wrote:
>>
>> - clk_data = kzalloc(sizeof(*clk_data) + (sizeof(*clk_data->hws) * 2),
>> - GFP_KERNEL);
>> + clk_data = kzalloc(struct_size(clk_data, hws, 2), GFP_KERNEL);
>> if (!clk_data) {
>> kfree(rtc);
On Thu, Aug 23, 2018 at 11:51 AM, Gustavo A. R. Silva
wrote:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct foo {
>
On Thu, Aug 23, 2018 at 12:33 PM, Gustavo A. R. Silva
wrote:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct foo {
>
If gcc (e.g. 4.1.2) decides not to inline init_mtd_structs() and
read_id_reg(), this will cause section mismatches, and crashes:
WARNING: drivers/mtd/nand/raw/docg4.o(.text+0xc10): Section mismatch in
reference from the function docg4_attach_chip() to the function
.init.text:init_mtd_structs
On 8/23/2018 2:18 PM, Brendan Higgins wrote:
On Thu, Aug 23, 2018 at 1:56 PM Jae Hyun Yoo
wrote:
In most of cases, interrupt bits are set one by one but there are
also a lot of other cases that Aspeed I2C IP sends multiple
interrupt bits with combining master and slave events using a
single in
On Thu, Aug 23, 2018 at 8:21 PM John Johansen
wrote:
>
> On 08/23/2018 07:09 AM, Arnd Bergmann wrote:
>
> thank you for the patch, but a fix for this issue was pushed to apparmor-next
> yesterday
>
Ok, good. As several people pointed out, my patch was also wrong, so that
saves me doing another o
With gcc 4.1.2:
drivers/tty/serial/qcom_geni_serial.c: In function ‘qcom_geni_serial_probe’:
drivers/tty/serial/qcom_geni_serial.c:1261: warning: ‘drv’ may be used
uninitialized in this function
Indeed, if dev.of_node is NULL, drv will be used uninitialized, and
dereferenced in uart_add_
On Thu, 23 Aug 2018 14:33:32 -0500
"Gustavo A. R. Silva" wrote:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct foo
With gcc 4.1.2:
drivers/iio/proximity/isl29501.c: In function ‘isl29501_register_write’:
drivers/iio/proximity/isl29501.c:235: warning: ‘msb’ may be used
uninitialized in this function
While this is a false positive, it can easily be avoided by removing the
"msb" intermediate variable.
R
With gcc 4.1.2:
drivers/ata/libata-core.c:7396:33: warning: no newline at end of file
Fixes: 2fa4a32613c9182b ("scsi: libsas: dynamically allocate and free ata host")
Signed-off-by: Geert Uytterhoeven
---
drivers/ata/libata-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Thu, Aug 23, 2018 at 1:59 PM, Jann Horn wrote:
> Some while back (commit 2deb4be28077 ("x86/dumpstack: When OOPSing,
> rewind the stack before do_exit()")), Andy added
> rewind_stack_do_exit(), which is used in kernel oops handling to
> discard the current stack contents and reset the stack poi
On Thu, 2018-08-23 at 14:03 -0700, Nick Desaulniers wrote:
> One reply for a bunch of the various threads, to keep the number of emails
> down:
>
> On Wed, Aug 22, 2018 at 5:20 PM Joe Perches wrote:
> > On Wed, 2018-08-22 at 16:37 -0700, Nick Desaulniers wrote:
> > > +/* Compiler specific macros
On Thu, Aug 23, 2018 at 1:56 PM Jae Hyun Yoo
wrote:
>
> In most of cases, interrupt bits are set one by one but there are
> also a lot of other cases that Aspeed I2C IP sends multiple
> interrupt bits with combining master and slave events using a
> single interrupt call. It happens much more in m
On Thu, 2018-08-23 at 14:03 -0700, Nick Desaulniers wrote:
> One of these days, I'll get frustrated enough to
> rewrite checkpatch.pl as a set of clang tidy checks (so that it
> actually parses the code), but I'll have to learn how to read perl
> first to start translating.
Good luck with that, re
One reply for a bunch of the various threads, to keep the number of emails down:
On Wed, Aug 22, 2018 at 5:20 PM Joe Perches wrote:
> On Wed, 2018-08-22 at 16:37 -0700, Nick Desaulniers wrote:
> > +/* Compiler specific macros. */
> > #ifdef __clang__
> > #include
>
> probably better as
>
> #if
On 2018/08/24 5:06, David Rientjes wrote:
> For those of us who are tracking CVE-2016-10723 which has peristently been
> labeled as "disputed" and with no clear indication of what patches address
> it, I am assuming that commit 9bfe5ded054b ("mm, oom: remove sleep from
> under oom_lock") and thi
Some while back (commit 2deb4be28077 ("x86/dumpstack: When OOPSing,
rewind the stack before do_exit()")), Andy added
rewind_stack_do_exit(), which is used in kernel oops handling to
discard the current stack contents and reset the stack pointer,
ensuring that the whole kernel stack is available for
When fixing an issue with PMD sharing and migration, it was discovered
via code inspection that other callers of huge_pmd_unshare potentially
have an issue with cache and tlb flushing.
Use the routine adjust_range_if_pmd_sharing_possible() to calculate
worst case ranges for mmu notifiers. Ensure
Correct a data corruption issue caused by improper handling of shared
huge PMDs during page migration. This issue was observed in a customer
environment and can be recreated fairly easily with a test program.
Patch 0001 addresses this issue only and is copied to stable with the
intention that this
The page migration code employs try_to_unmap() to try and unmap the
source page. This is accomplished by using rmap_walk to find all
vmas where the page is mapped. This search stops when page mapcount
is zero. For shared PMD huge pages, the page map count is always 1
no matter the number of mapp
In most of cases, interrupt bits are set one by one but there are
also a lot of other cases that Aspeed I2C IP sends multiple
interrupt bits with combining master and slave events using a
single interrupt call. It happens much more in multi-master
environment than single-master. For an example, whe
On Thu, Aug 23, 2018 at 11:51 AM, Gustavo A. R. Silva
wrote:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct foo {
>
On Thu, Aug 23, 2018 at 09:52:17PM +0200, Bernd Petrovitsch wrote:
> Hi all!
>
> On Thu, 2018-08-23 at 10:43 -0700, Paul E. McKenney wrote:
> > [...]
> > Does anyone do kernel-only deployments, for example, setting up an
> > embedded device having a Linux kernel and absolutely no userspace
> > wha
Hi all!
On Thu, 2018-08-23 at 10:43 -0700, Paul E. McKenney wrote:
> [...]
> Does anyone do kernel-only deployments, for example, setting up an
> embedded device having a Linux kernel and absolutely no userspace
> whatsoever?
[...]
> You see, rcutorture runs entirely out of initrd, never mounting
On Thu, Aug 23, 2018 at 01:12:22PM -0700, Guenter Roeck wrote:
> On Thu, Aug 23, 2018 at 09:56:26AM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.18.5 release.
> > There are 22 patches in this series, all will be posted as a response
> > to this one. I
On Thu, Aug 23, 2018 at 10:21:24AM -0700, Guenter Roeck wrote:
> On Thu, Aug 23, 2018 at 06:56:21PM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Aug 23, 2018 at 09:30:21AM -0700, Guenter Roeck wrote:
> > > On Thu, Aug 23, 2018 at 09:52:36AM +0200, Greg Kroah-Hartman wrote:
> > > > This is the start
On Thu, Aug 23, 2018 at 9:26 AM, Paolo Bonzini wrote:
> On 23/08/2018 18:24, Vitaly Kuznetsov wrote:
>> nested_run_pending is set 20 lines above and check_vmentry_prereqs()/
>> check_vmentry_postreqs() don't seem to be resetting it (the later, however,
>> checks it).
>>
>> Signed-off-by: Vitaly Ku
On Thu, Aug 23, 2018 at 11:09:01AM -0700, Nathan Chancellor wrote:
> On Thu, Aug 23, 2018 at 09:51:56AM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.124 release.
> > There are 130 patches in this series, all will be posted as a response
> > to this o
On Thu, Aug 23, 2018 at 03:22:48PM -0400, Ray Clinton wrote:
> On Thu, Aug 23, 2018 at 7:44 PM Paul E. McKenney
> wrote:
> > Does anyone do kernel-only deployments, for example, setting up an
> > embedded device having a Linux kernel and absolutely no userspace
> > whatsoever?
>
> To be honest I'
On Thu, Aug 23, 2018 at 3:55 AM Amit Kucheria wrote:
>
> The idle-states binding documentation[1] mentions that the
> 'entry-method' property is required on 64-bit platforms and must be
> set to "psci".
>
> commit a13f18f59d26 ("Documentation: arm: Fix typo in the idle-states
> bindings examples")
On Thu, Aug 23, 2018 at 12:12:35PM -0700, Josh Triplett wrote:
> On Thu, Aug 23, 2018 at 10:43:59AM -0700, Paul E. McKenney wrote:
> > Hello!
> >
> > Does anyone do kernel-only deployments, for example, setting up an
> > embedded device having a Linux kernel and absolutely no userspace
> > whatsoe
On Thu, Aug 23, 2018 at 12:16:04PM -0700, Josh Triplett wrote:
> On Thu, Aug 23, 2018 at 08:54:17PM +0200, Adam Borowski wrote:
> > On Thu, Aug 23, 2018 at 10:43:59AM -0700, Paul E. McKenney wrote:
> > > The mkinitramfs approach results in about 40MB of initrd, and dracut
> > > about 10MB. Most of
On Thu, Aug 23, 2018 at 08:54:17PM +0200, Adam Borowski wrote:
> On Thu, Aug 23, 2018 at 10:43:59AM -0700, Paul E. McKenney wrote:
> > The mkinitramfs approach results in about 40MB of initrd, and dracut
> > about 10MB. Most of this is completely useless for rcutorture, which
> > isn't interested
On Thu, Aug 23, 2018 at 02:42:45PM -0400, Nicolas Pitre wrote:
> On Thu, 23 Aug 2018, Paul E. McKenney wrote:
>
> > Hello!
> >
> > Does anyone do kernel-only deployments, for example, setting up an
> > embedded device having a Linux kernel and absolutely no userspace
> > whatsoever?
>
> Not that
Fedora got a bug report of a crash with iSCSI:
kernel BUG at include/linux/scatterlist.h:143!
...
RIP: 0010:iscsit_do_crypto_hash_buf+0x154/0x180 [iscsi_target_mod]
...
Call Trace:
? iscsi_target_tx_thread+0x200/0x200 [iscsi_target_mod]
iscsit_get_rx_pdu+0x4cd/0xa90 [iscsi_target_mod]
? nat
On Thu, Aug 23, 2018 at 01:20:40PM -0600, Shuah Khan wrote:
> On 08/23/2018 01:56 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.18.5 release.
> > There are 22 patches in this series, all will be posted as a response
> > to this one. If anyone has any issu
On 8/23/18 5:44 PM, Andi Kleen wrote:
> On Thu, Aug 23, 2018 at 03:44:18PM +0200, Vlastimil Babka wrote:
>> Two users have reported [1] that they have an "extremely unlikely" system
>> with more than MAX_PA/2 memory and L1TF mitigation is not effective. In fact
>> it's a CPU with 36bits phys limit
Commit a5fb9fb023a1435f2b42bccd7f547560f3a21dc3 upstream.
When testing the R-Car PCIe driver on the Condor board, if the PCIe PHY
driver was left disabled, the kernel crashed with this BUG:
kernel BUG at lib/ioremap.c:72!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
C
On Thu, Aug 23, 2018 at 09:51:06AM +0200, Greg Kroah-Hartman wrote:
> NOTE, this is going to be the LAST 4.17.y kernel release. Please move
> to the 4.18.y tree at this point in time if you have not already. After
> this release, 4.17.y will be end-of-life.
>
> This is the start of the stable re
On Thu, Aug 23, 2018 at 09:56:26AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.18.5 release.
> There are 22 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Thu, Aug 23, 2018 at 09:51:53AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.67 release.
> There are 217 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me kno
On Thu, Aug 23, 2018 at 09:51:56AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.124 release.
> There are 130 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me kno
On 08/23/2018 11:04 PM, Sergei Shtylyov wrote:
> Commit a5fb9fb023a1435f2b42bccd7f547560f3a21dc3 upstream.
>
> When testing the R-Car PCIe driver on the Condor board, if the PCIe PHY
> driver was left disabled, the kernel crashed with this BUG:
>
> kernel BUG at lib/ioremap.c:72!
> Internal
On Thu, Aug 23, 2018 at 09:52:36AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.152 release.
> There are 79 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
Hi,
I see the attached warning when booting 'sabrelite' images in qemu,
using imx_v6_v7_defconfig and imx6dl-sabrelite.dts.
Context suggests that the warning is seen since commit 1a4327fbf4554 ("spi:
fix IDR collision on systems with both fixed and dynamic SPI bus numbers").
Guenter
---
[7.
On Wed, 22 Aug 2018, Tetsuo Handa wrote:
> On 2018/08/03 15:16, Michal Hocko wrote:
> > On Fri 03-08-18 07:05:54, Tetsuo Handa wrote:
> >> On 2018/07/31 14:09, Michal Hocko wrote:
> >>> On Tue 31-07-18 06:01:48, Tetsuo Handa wrote:
> On 2018/07/31 4:10, Michal Hocko wrote:
> > Since shoul
tch warning unrelated to proposed change)
>
> Patch is against 4.18 (localversion-next is next-20180823)
>
> fs/cifs/sess.c | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/fs/cifs/sess.c b/fs/cifs/sess.c
> index 8b0502c..aa23c00 100644
> --- a/fs/cifs/
On Thu 23-08-18 12:38:33, Andi Kleen wrote:
> > There are people who care about L1TF mitigations. I am not going to
> > question their motivation. In any case a hint how to make the mitigation
> > active again sounds more useful than something that sounds as scary as
> > "you are vulnerable".
>
>
Commit a5fb9fb023a1435f2b42bccd7f547560f3a21dc3 upstream.
When testing the R-Car PCIe driver on the Condor board, if the PCIe PHY
driver was left disabled, the kernel crashed with this BUG:
kernel BUG at lib/ioremap.c:72!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
C
(Adding arm-soc folks)
On Thu, Aug 23, 2018 at 9:01 PM, Sudeep Holla wrote:
> Hi Amit,
>
> Thanks for fixing this.
>
> On Thu, Aug 23, 2018 at 02:23:29PM +0530, Amit Kucheria wrote:
>> The idle-states binding documentation[1] mentions that the
>> 'entry-method' property is required on 64-bit plat
Commit a5fb9fb023a1435f2b42bccd7f547560f3a21dc3 upstream.
When testing the R-Car PCIe driver on the Condor board, if the PCIe PHY
driver was left disabled, the kernel crashed with this BUG:
kernel BUG at lib/ioremap.c:72!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
C
On 08/23/2018 06:41 PM, Greg Kroah-Hartman wrote:
4.14-stable review patch. If anyone has any objections, please let me
know.
--
From: Sergei Shtylyov
commit a5fb9fb023a1435f2b42bccd7f547560f3a21dc3 upstream
Em Thu, Aug 23, 2018 at 12:16:43PM -0400, William Cohen escreveu:
> On 08/23/2018 10:31 AM, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Aug 23, 2018 at 01:21:45PM +0200, Martin Liška escreveu:
> >> May I please ping this.
> > I was waiting for someone to give some ack, perhaps Will Cohen can take
Hi Randy,
> Am 23.08.2018 um 20:13 schrieb Randy Dunlap :
>
> From: Randy Dunlap
>
> When $DEPMOD is not found, only print a warning instead of exiting
> with an error message and error status.
>
> Warning: 'make modules_install' requires /sbin/depmod. Please install it.
> This is probably in
> There are people who care about L1TF mitigations. I am not going to
> question their motivation. In any case a hint how to make the mitigation
> active again sounds more useful than something that sounds as scary as
> "you are vulnerable".
FWIW an early version of these patches automatically lim
On Thu, Aug 23, 2018 at 12:15 PM Linus Torvalds
wrote:
>
> So right now my "tlb-fixes" branch looks like this:
> [..]
>
> I'll do a few more test builds and boots, but I think I'm going to
> merge it in this cleaned-up and re-ordered form.
In the meantime, I decided to push out that branch in cas
On Thu 23-08-18 10:56:30, Mike Kravetz wrote:
> On 08/23/2018 10:01 AM, Mike Kravetz wrote:
> > On 08/23/2018 05:48 AM, Michal Hocko wrote:
> >> On Tue 21-08-18 18:10:42, Mike Kravetz wrote:
> >> [...]
> >>
> >> OK, after burning myself when trying to be clever here it seems like
> >> your proposed
One of the more common cases of allocation size calculations is finding
the size of a structure that has a zero-sized array at the end, along
with memory for some number of elements for that array. For example:
struct foo {
int stuff;
void *entry[];
};
instance = devm_kzalloc(dev,
(Oops, I had a typo in the linux-nfs mailing list)
On Thu, 2018-08-23 at 15:27 -0400, Anna Schumaker wrote:
> Hi Linus,
>
> The following changes since commit cd3f77d74ac31b4627cdfa70812338076a1ea475:
>
> Merge tag 'usb-4.18-rc7' of
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb (
Hi Vlastimil,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on next-20180822]
[cannot apply to v4.18]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github
Linus,
Please pull the userns-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
userns-linus
HEAD: 82c9a927bc5df6e06b72d206d24a9d10cced4eb5 getxattr: use correct xattr
length
This is a set of 4 fairly obvious bug fixes. A switch
Hi Linus,
The following changes since commit cd3f77d74ac31b4627cdfa70812338076a1ea475:
Merge tag 'usb-4.18-rc7' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb (2018-07-26 09:29:29
-0700)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.g
On Thu 23-08-18 16:28:12, Vlastimil Babka wrote:
> Two users have reported [1] that they have an "extremely unlikely" system
> with more than MAX_PA/2 memory and L1TF mitigation is not effective. Let's
> make the warning more helpful by suggesting the proper mem=X kernel boot
> param,
> a rough ca
On Thu 23-08-18 08:46:48, Andi Kleen wrote:
> On Thu, Aug 23, 2018 at 04:28:12PM +0200, Vlastimil Babka wrote:
> > Two users have reported [1] that they have an "extremely unlikely" system
> > with more than MAX_PA/2 memory and L1TF mitigation is not effective. Let's
> > make the warning more helpf
On Thu, Aug 23, 2018 at 7:44 PM Paul E. McKenney
wrote:
> Does anyone do kernel-only deployments, for example, setting up an
> embedded device having a Linux kernel and absolutely no userspace
> whatsoever?
To be honest I'm a total newb to kernel dev, so much so that I copied and
pasted the above
On Thu, Aug 23, 2018 at 10:43:59AM -0700, Paul E. McKenney wrote:
> Hello!
>
> Does anyone do kernel-only deployments, for example, setting up an
> embedded device having a Linux kernel and absolutely no userspace
> whatsoever?
I would very much *like* to do this. One day I'd like to have a
CONFI
On 08/23/2018 01:56 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.18.5 release.
> There are 22 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
Currently the ti-cpufreq driver blindly registers a 'ti-cpufreq' to force
the driver to probe on any platforms where the driver is built in.
However, this should only happen on platforms that actually can make use
of the driver. There is already functionality in place to match the
SoC compatible so
On 08/23/2018 01:52 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.152 release.
> There are 79 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
On 08/23/2018 01:51 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.124 release.
> There are 130 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 08/23/2018 01:51 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.67 release.
> There are 217 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 08/23/2018 01:51 AM, Greg Kroah-Hartman wrote:
> NOTE, this is going to be the LAST 4.17.y kernel release. Please move
> to the 4.18.y tree at this point in time if you have not already. After
> this release, 4.17.y will be end-of-life.
>
> This is the start of the stable review cycle for the
On Thu, Aug 23, 2018 at 08:54:17PM +0200, Adam Borowski wrote:
> On Thu, Aug 23, 2018 at 10:43:59AM -0700, Paul E. McKenney wrote:
> > The mkinitramfs approach results in about 40MB of initrd, and dracut
> > about 10MB. Most of this is completely useless for rcutorture, which
> > isn't interested
On Thu, Aug 23, 2018 at 1:47 AM Nicholas Piggin wrote:
>
> These are split from some patches I posted a while back, I was going
> to take a look and revive the series again after your fixes go in,
> but having another look, it may be that your "[PATCH 3/4] mm/tlb,
> x86/mm: Support invalidating TL
On Thu, Aug 23, 2018 at 08:54:17PM +0200, Adam Borowski wrote:
> .globl _start
> .data
> req:.8byte 9, 9
> .text
> _start:
> mov $35, %rax # syscall: nanosleep
> mov $req, %rdi
> xor %rsi, %rsi
> syscall
> jmp _start
Hi Vlastimil,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on next-20180822]
[cannot apply to v4.18]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github
On Thu, Aug 23, 2018 at 10:43:59AM -0700, Paul E. McKenney wrote:
> The mkinitramfs approach results in about 40MB of initrd, and dracut
> about 10MB. Most of this is completely useless for rcutorture, which
> isn't interested in mounting filesystems, opening devices, and almost
> all of the other
One of the more common cases of allocation size calculations is finding
the size of a structure that has a zero-sized array at the end, along
with memory for some number of elements for that array. For example:
struct foo {
int stuff;
void *entry[];
};
instance = kzalloc(sizeof(s
Hi Johan,
On Wed, Aug 22, 2018 at 12:57 PM Johan Hovold wrote:
>
> Use the new of_get_compatible_child() helper to lookup the slot child
> node instead of using of_find_compatible_node(), which searches the
> entire tree and thus can return an unrelated (i.e. non-child) node.
that new helper is m
On Thu, Aug 23, 2018 at 08:16:55PM +0200, Geert Uytterhoeven wrote:
> Hi Paul,
>
> On Thu, Aug 23, 2018 at 7:44 PM Paul E. McKenney
> wrote:
> > Does anyone do kernel-only deployments, for example, setting up an
> > embedded device having a Linux kernel and absolutely no userspace
> > whatsoever?
On Thu, 23 Aug 2018, Paul E. McKenney wrote:
> Hello!
>
> Does anyone do kernel-only deployments, for example, setting up an
> embedded device having a Linux kernel and absolutely no userspace
> whatsoever?
Not that I know of. For one thing, you'd lose the ability to license
your application c
Quoting Taniya Das (2018-08-08 03:15:26)
>
>
> On 8/8/2018 11:52 AM, Stephen Boyd wrote:
> >>
> >> Binding describes hardware controllable by the OS. That's the reality.
> >> Let's not add mandatory clock bindings for clocks that the OS can't do
> >> anything about.
> >>
> >
> > It seems that yo
Hi Gustavo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on security/next]
[also build test ERROR on v4.18 next-20180822]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/com
On 8/23/18 1:21 PM, John Johansen wrote:
> On 08/23/2018 06:42 AM, Gustavo A. R. Silva wrote:
>
> thank you for the patch, but a fix for this issue was pushed to apparmor-next
> yesterday
>
That's great. Good to know.
Thanks
--
Gustavo
There are three features used by various Logitech mice for
high-resolution scrolling: the fast scrolling bit in HID++ 1.0, and the
x2120 and x2121 features in HID++ 2.0 and above. This patch supports
all three, and uses the multiplier reported by the mouse for the HID++
2.0+ features.
The full lis
To avoid code duplication, this class counts high-resolution scroll
movements and emits the legacy low-resolution events when appropriate.
Drivers should create one instance for each scroll wheel that they
need to handle.
Signed-off-by: Harry Cutts
---
drivers/hid/hid-input.c | 44 +
On Thu, Aug 23, 2018 at 8:21 AM, Christoph Hellwig wrote:
>> xtensa: platform-specific handling of coherent memory
>
> How is this supposed to be used? For the nommu version there only
> are __weak stubs, but no actual implementation.
The idea is that nommu xtensa platforms that have two v
Hi Brendan,
On 8/22/2018 11:46 PM, Brendan Higgins wrote:
On Mon, Aug 20, 2018 at 1:16 PM Jae Hyun Yoo
wrote:
In most of cases, interrupt bits are set one by one but there are
also a lot of other cases that Aspeed I2C IP sends multiple
interrupt bits with combining master and slave events usi
From: Naoya Horiguchi
There is a kernel panic that is triggered when reading /proc/kpageflags
on the kernel booted with kernel parameter 'memmap=nn[KMG]!ss[KMG]':
BUG: unable to handle kernel paging request at fffe
PGD 9b20e067 P4D 9b20e067 PUD 9b210067 PMD 0
Oops: [#1] SM
Quoting Taniya Das (2018-08-22 03:28:31)
>
> >
> > H. Ok. That won't work then. recalc_rate() better not try to
> > populate the frequency table then or it will not work. So I suppose it
> > needs to fallback to reading the registers and assuming the parent_rate
> > coming in is the actual fr
From: Masayoshi Mizuma
commit 124049decbb1 ("x86/e820: put !E820_TYPE_RAM regions into
memblock.reserved") breaks movable_node kernel option because it
changed the memory gap range to reserved memblock. So, the node
is marked as Normal zone even if the SRAT has Hot plaggable affinity.
==
I notice that Linux 4.18 has the following changeset which changes the
user visible perf_event.h file
commit 6cbc304f2f360f25cc8607817239d6f4a2fd3dc5
Author: Peter Zijlstra
Date: Thu May 10 15:48:41 2018 +0200
perf/x86/intel: Fix unwind errors from PEBS entries (m
101 - 200 of 1231 matches
Mail list logo
