3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 110080cea0d0e4dfdb0b536e7f8a5633ead6a781 upstream.
There are a couple potential integer overflows here.
round_up(m->size + (m->addr & ~PAGE_MASK), PAGE_SIZE);
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 8fb44d60d4142cd2a440620cd291d346e23c131e upstream.
If llc_mac_hdr_init() returns an error, we must drop the skb
since no llc_build_and_send_ui_pkt() caller will take care
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ravi Bangoria
commit 3202e35ec1c8fc19cea24253ff83edf702a60a02 upstream.
Consider a scenario where user creates two events:
1st event:
attr.sample_type |= PERF_SAMPLE_BRANCH_STACK;
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Roberto Bergantinos Corpas
commit 31fad7d41e73731f05b8053d17078638cf850fa6 upstream.
In cifs_read_allocate_pages, in case of ENOMEM, we go through
whole rdata->pages array but we have failed
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 903869bd10e6719b9df6718e785be7ec725df59f upstream.
ip_sf_list_clear_all() needs to be defined even if !CONFIG_IP_MULTICAST
Fixes: 3580d04aa674 ("ipv4/igmp: fix another
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Steffen Maier
commit ef4021fe5fd77ced0323cede27979d80a56211ca upstream.
When the user tries to remove a zfcp port via sysfs, we only rejected it if
there are zfcp unit children under the
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Harald Freudenberger
commit 1c2c7029c008922d4d48902cc386250502e73d51 upstream.
This patch fixes a complain about possible sleep during
spinlock aquired
"BUG: sleeping function called from
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit a4270d6795b0580287453ea55974d948393e66ef upstream.
If a network driver provides to napi_gro_frags() an
skb with a page fragment of exactly 14 bytes, the call
to
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kai-Heng Feng
commit 1a6dd3fea131276a4fc44ae77b0f471b0b473577 upstream.
There is one more Realtek card reader requires ums-realtek to work
correctly.
Add the device ID to support it.
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: "S.j. Wang"
commit ad6eecbfc01c987e0253371f274c3872042e4350 upstream.
Add regcache_mark_dirty before regcache_sync for power
of codec may be lost at suspend, then all the register
need to be
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: YueHaibing
commit 5caaf29af5ca82d5da8bc1d0ad07d9e664ccf1d8 upstream.
If spi_register_master fails in spi_bitbang_start
because device_add failure, We should return the
error code other than
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Shuah Khan
commit 3ea3091f1bd8586125848c62be295910e9802af0 upstream.
Fix the following sparse context imbalance regression introduced in
a patch that fixed sleeping function called from
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Steffen Maier
commit d27e5e07f9c49bf2a6a4ef254ce531c1b4fb5a38 upstream.
With this early return due to zfcp_unit child(ren), we don't use the
zfcp_port reference from the earlier
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Yingjoe Chen
commit a0692f0eef91354b62c2b4c94954536536be5425 upstream.
If I2C_M_RECV_LEN check failed, msgs[i].buf allocated by memdup_user
will not be freed. Pump index up so it will be
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: "George G. Davis"
commit 099506cbbc79c0bd52b19cb6b930f256dabc3950 upstream.
As noted in commit 84b40e3b57ee ("serial: 8250: omap: Disable DMA for
console UART"), UART console lines use
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Chris Packham
commit c5f81656a18b271976a86724dadd8344e54de74e upstream.
This is adds the vendor and device id for the AT-VT-Kit3 which is a
pl2303-based device.
Signed-off-by: Chris Packham
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
commit f6e2aa91a46d2bc79fce9b93a988dbe7655c90c0 upstream.
Recently syzbot in conjunction with KMSAN reported that
ptrace_peek_siginfo can copy an uninitialized siginfo to
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Zhenliang Wei
commit 98af37d624ed8c83f1953b1b6b2f6866011fc064 upstream.
In the fixes commit, removing SIGKILL from each thread signal mask and
executing "goto fatal" directly will skip the
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Marco Zatta
commit bd21f0222adab64974b7d1b4b8c7ce6b23e9ea4d upstream.
This patch fixes the chipmunk-like voice that manifets randomly when
using the integrated mic of the Logitech Webcam HD
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Robert Hancock
commit 4a60570dce658e3f8885bbcf852430b99f65aca5 upstream.
Some chips have attributes which exist on more than one page but the
attribute is not presently marked as paged. This
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Shuah Khan
commit 0c9e8b3cad654bfc499c10b652fbf8f0b890af8f upstream.
stub_probe() and stub_disconnect() call functions which could call
sleeping function in invalid context whil holding
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Paolo Abeni
commit 720f1de4021f09898b8c8443f3b3e995991b6e3a upstream.
Currently, the process issuing a "start" command on the pktgen procfs
interface, acquires the pktgen thread lock and
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Willem de Bruijn
commit fd704bd5ee749d560e86c4f1fd2ef486d8abf7cf upstream.
CAN supports software tx timestamps as of the below commit. Purge
any queued timestamp packets on socket destroy.
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ronnie Sahlberg
commit 487317c99477d00f22370625d53be3239febabbe upstream.
We can not depend on the tcon->open_file_lock here since in multiuser mode
we may have the same file/inode open via
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 65a3c497c0e965a552008db8bc2653f62bc925a1 upstream.
Before taking a refcount, make sure the object is not already
scheduled for deletion.
Same fix is needed in
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dave Martin
commit df205b5c63281e4f32caac22adda18fd68795e80 upstream.
Since commit d26c25a9d19b ("arm64: KVM: Tighten guest core register
access from userspace"), KVM_{GET,SET}_ONE_REG
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Joakim Zhang
commit 247e5356a709eb49a0d95ff2a7f07dac05c8252c upstream.
Current we can meet timeout issue when setting a small bitrate like
1 as follows on i.MX6UL EVK board (ipg clock =
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit f6581f5b55141a95657ef5742cf6a6bfa20a109f upstream.
Restore the read memory barrier in __ptrace_may_access() that was deleted
a couple years ago. Also add comments on this
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Zhu Yanjun
commit 85cb928787eab6a2f4ca9d2a798b6f3bed53ced1 upstream.
When the following tests last for several hours, the problem will occur.
Server:
rds-stress -r 1.1.1.16 -D 1M
Client:
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 240b4cc8fd5db138b675297d4226ec46594d9b3b upstream.
Once we unlock adapter->hw_lock in pvscsi_queue_lck() nothing prevents just
queued scsi_cmnd from completing and freeing the
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Petr Oros
commit 2e5db6eb3c23e5dc8171eb8f6af7a97ef9fcf3a9 upstream.
Certain cards in conjunction with certain switches need a little more
time for link setup that results in ethtool link test
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Oliver Neukum
commit e0feb73428b69322dd5caae90b0207de369b5575 upstream.
If a disconnected device is closed, rio_close() must free
the buffers.
Signed-off-by: Oliver Neukum
Signed-off-by:
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Colin Ian King
commit c3ea60c231446663afd6ea1054da6b7f830855ca upstream.
There are two occurrances of a call to snd_seq_oss_fill_addr where
the dest_client and dest_port arguments are in the
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: YueHaibing
commit 30d8177e8ac776d89d387fad547af6a0f599210e upstream.
We build vlan on top of bonding interface, which vlan offload
is off, bond mode is 802.3ad (LACP) and xmit_hash_policy is
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: YueHaibing
commit d595b03de2cb0bdf9bcdf35ff27840cc3a37158f upstream.
As commit 30d8177e8ac7 ("bonding: Always enable vlan tx offload")
said, we should always enable bonding's vlan tx offload,
This is the start of the stable review cycle for the 3.16.75 release.
There are 87 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Fri Oct 04 19:06:50 UTC 2019.
Anything
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Xin Long
commit 25bff6d5478b2a02368097015b7d8eb727c87e16 upstream.
Now in sctp_endpoint_init(), it holds the sk then creates auth
shkey. But when the creation fails, it doesn't release the
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Coly Li
commit 31b90956b124240aa8c63250243ae1a53585c5e2 upstream.
Recently people report bcache code compiled with gcc9 is broken, one of
the buggy behavior I observe is that two adjacent 4KB
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Stanley Chu
commit 24e2e7a19f7e4b83d0d5189040d997bce3596473 upstream.
UFS runtime suspend can be triggered after pm_runtime_enable() is invoked
in ufshcd_pltfrm_init(). However if the first
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit 8404d7a674c49278607d19726e0acc0cae299357 upstream.
A packed AppArmor policy contains null-terminated tag strings that are read
by unpack_nameX(). However, unpack_nameX() uses
On Tue 2019-10-01 12:37:01, Matthias Kaehlcke wrote:
> On Tue, Oct 01, 2019 at 02:08:46PM -0400, Steven Rostedt wrote:
> > On Tue, 1 Oct 2019 10:42:35 -0700
> > Matthias Kaehlcke wrote:
> >
> > > On Tue, Oct 01, 2019 at 01:03:43PM -0400, Steven Rostedt wrote:
> > > > On Tue, 1 Oct 2019 09:35:42
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Naohiro Aota
commit c4e0540d0ad49c8ceab06cceed1de27c4fe29f6e upstream.
Currently, btrfs does not consult seed devices to start readahead. As a
result, if readahead zone is added to the seed
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Colin Ian King
commit ea136a112d89bade596314a1ae49f748902f4727 upstream.
The left shift of unsigned int cpu_khz will overflow for large values of
cpu_khz, so cast it to a long long before
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dmitry Korotin
commit 0b24cae4d535045f4c9e177aa228d4e97bad212c upstream.
Add a missing EHB (Execution Hazard Barrier) in mtc0 -> mfc0 sequence.
Without this execution hazard barrier it's
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eiichi Tsukata
commit 46cc0b44428d0f0e81f11ea98217fc0edfbeab07 upstream.
Current snapshot implementation swaps two ring_buffers even though their
sizes are different from each other, that can
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Julian Wiedmann
commit fdbf6326912d578a31ac4ca0933c919eadf1d54c upstream.
af_iucv sockets over z/VM IUCV require that their skbs are allocated
in DMA memory. This restriction doesn't apply to
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andrea Arcangeli
commit 59ea6d06cfa9247b586a695c21f94afa7183af74 upstream.
When fixing the race conditions between the coredump and the mmap_sem
holders outside the context of the process, we
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 4f488fbca2a86cc7714a128952eead92cac279ab upstream.
In wiphy_new_nm(), if an error occurs after dev_set_name() and
device_initialize() have already been called, it's
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: 7879fc4bdc7506d37bd67b6fc29442c53c06dfda
Gitweb:
https://git.kernel.org/tip/7879fc4bdc7506d37bd67b6fc29442c53c06dfda
Author:Borislav Petkov
AuthorDate:Sun, 25 Aug 2019 22:50:18 +02:00
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit 31f6264e225fb92cf6f4b63031424f20797c297d upstream.
We've received a bugreport that using LPM with ST1000LM024 drives leads
to system lockups. So it seems that these
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jakub Kicinski
commit 177b8007463c4f36c9a2c7ce7aa9875a4cad9bd5 upstream.
When GSO frame has to be corrupted netem uses skb_gso_segment()
to produce the list of frames, and re-enqueues the
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit f3e92cb8e2eb8c27d109e6fd73d3a69a8c09e288 upstream.
Nine years ago, I added RCU handling to neighbours, not pneighbours.
(pneigh are not commonly used)
Unfortunately I
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Steve French
commit 8d526d62db907e786fd88948c75d1833d82bd80e upstream.
Some servers such as Windows 10 will return STATUS_INSUFFICIENT_RESOURCES
as the number of simultaneous SMB3 requests
On 10/2/19 8:06 PM, Linus Torvalds wrote:
On Wed, Oct 2, 2019 at 6:48 AM Thomas Hellström (VMware)
wrote:
From: Thomas Hellstrom
Add two utilities to a) write-protect and b) clean all ptes pointing into
a range of an address space.
This one I still don't exactly love.
I'm not entirely sure
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ivan Vecera
commit 718f4a2537089ea41903bf357071306163bc7c04 upstream.
Number of Rx queues used for flow hashing returned by the driver is
incorrect and this bug prevents user to use the last
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Wengang Wang
commit be99ca2716972a712cde46092c54dee5e6192bf8 upstream.
ocfs2_dentry_attach_lock() can be executed in parallel threads against the
same dentry. Make that race safe. The race
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Filipe Manana
commit ce7791ffee1e1ee9f97193b817c7dd1fa6746aad upstream.
The list of devices is protected by the device_list_mutex and the device
replace code, in its finishing phase correctly
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Julian Wiedmann
commit 06996c1d4088a0d5f3e7789d7f96b4653cc947cc upstream.
Even when running as VM guest (ie pr_iucv != NULL), af_iucv can still
open HiperTransport-based connections. For
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 085ebfe937d7a7a5df1729f35a12d6d655fea68c upstream.
perf_sample_regs_user() uses 'current->mm' to test for the presence of
userspace, but this is insufficient, consider
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 21d4120ec6f5b5992b01b96ac484701163917b63 upstream.
Michal Suchanek reported [1] that running the pcrypt_aead01 test from
LTP [2] in a loop and holding Ctrl-C causes a NULL
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: John David Anglin
commit 63923d2c3800919774f5c651d503d1dd2adaddd5 upstream.
We only support I/O to kernel space. Using %sr1 to load the coherence
index may be racy unless interrupts are
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Yabin Cui
commit 1b038c6e05ff70a1e66e3e571c2e6106bdb75f53 upstream.
In perf_output_put_handle(), an IRQ/NMI can happen in below location and
write records to the same ring buffer:
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit c8ea9fce2baf7b643384f36f29e4194fa40d33a6 upstream.
Sometimes mpi_powm will leak karactx because a memory allocation
failure causes a bail-out that skips the freeing of
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven
commit 1bf72720281770162c87990697eae1ba2f1d917a upstream.
Currently, if the user specifies an unsupported mitigation strategy on the
kernel command line, it will be ignored
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 3f9fbe9bd86c534eba2faf5d840fd44c6049f50e upstream.
Similar to how decrementing rb->next too early can cause data_head to
(temporarily) be observed to go backward, so too
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: WANG Cong
commit c38b7d327aafd1e3ad7ff53eefac990673b65667 upstream.
Andrey reported a use-after-free in add_grec():
for (psf = *psf_list; psf; psf = psf_next) {
...
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Randy Dunlap
commit e9646f0f5bb62b7d43f0968f39d536cfe7123b53 upstream.
The gpio-adp5588 driver uses interfaces that are provided by
GPIOLIB_IRQCHIP, so select that symbol in its Kconfig
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Sahitya Tummala
commit f6122ed2a4f9c9c1c073ddf6308d1b2ac10e0781 upstream.
In the vfs_statx() context, during path lookup, the dentry gets
added to sd->s_dentry via configfs_attach_attr(). In
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Alejandro Jimenez
commit c1f7fec1eb6a2c86d01bc22afce772c743451d88 upstream.
The bits set in x86_spec_ctrl_mask are used to calculate the guest's value
of SPEC_CTRL that is written to the MSR
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ravi Bangoria
commit 913a90bc5a3a06b1f04c337320e9aeee2328dd77 upstream.
perf_event_open() limits the sample_period to 63 bits. See:
0819b2e30ccb ("perf: Limit
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Alexandra Winter
commit 335726195e460cb6b3f795b695bfd31f0ea70ef0 upstream.
Enabling sysfs attribute bridge_hostnotify triggers a series of udev events
for the MAC addresses of all currently
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: YueHaibing
commit c5a3aed1cd3152429348ee1fe5cdcca65fe901ce upstream.
This patch add error path for can_init() to avoid possible crash if some
error occurs.
Fixes: 0d66548a10cb ("[CAN]: Add
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 3e66b7cc50ef921121babc91487e1fb98af1ba6e upstream.
Building with Clang reports the redundant use of MODULE_DEVICE_TABLE():
drivers/net/ethernet/dec/tulip/de4x5.c:2110:1:
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit ca21f851cc9643af049226d57fabc3c883ea648e upstream.
The Acorn i2c driver (for RiscPC) triggers the "i2c adapter has no name"
warning in the I2C core driver, resulting in
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Roman Bolshakov
commit 5676234f20fef02f6ca9bd66c63a8860fce62645 upstream.
WRITE SAME corrupts data on the block device behind iblock if the command
is emulated. The emulation code issues (M -
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit a03ff54460817c76105f81f3aa8ef655759ccc9a upstream.
The syzkaller USB fuzzer found a slab-out-of-bounds write bug in the
USB core, caused by a failure to check the actual
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Catalina Mocanu
commit 288903f6b91e759b0a813219acd376426cbb8f14 upstream.
This fixes the following checkpatch.pl warning:
WARNING: else is not generally useful after a break or return.
While
3.16.75-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jisheng Zhang
commit 49ce881c0d4c4a7a35358d9dccd5f26d0e56fc61 upstream.
Commit 984203ceff27 ("net: stmmac: mdio: remove reset gpio free")
removed the reset gpio free, when the driver is
Hi Paul and other.
> Hi Alexandre,
> This should probably be something like ingenic,xburst2. JZ4780 is the
> SoC. It also should be a documented binding, but I think it would be
> worth holding off on the whole thing until we actually get SMP support
> merged - just in case we come up with a
On Thu, Sep 26, 2019 at 7:17 PM Yang Weijiang wrote:
>
> CR4.CET(bit 23) is master enable bit for CET feature.
> Previously, KVM did not support setting any bits in XSS
> so it's hardcoded to check and inject a #GP if Guest
> attempted to write a non-zero value to XSS, now it supports
> CET
On Wed, 02 Oct 2019 20:47:03 +0530, Saiyam Doshi said:
> fs_sync() is wrapper to bdev_sync(). When fs_sync is called with
> non-zero argument, bdev_sync gets called.
>
> Most instances of fs_sync is called with false and very few with
> true. Refactor this and makes direct call to bdev_sync()
On Tue, Mar 19, 2019 at 8:33 AM Sebastian Reichel wrote:
>
> Hi Hans,
>
> On Thu, Mar 14, 2019 at 09:20:10AM +0100, Hans Verkuil wrote:
> > On 12/21/18 2:17 AM, Sebastian Reichel wrote:
> > > This moves all remaining users of the legacy TI_ST driver to hcill
> > > (patches
> > > 1-3). Then
We've seen several incorrect patches for fs_sync() calls in the exfat driver.
Add code to the TODO that explains this isn't just a delete code and refactor,
but that actual analysis of when the filesystem should be flushed to disk
needs to be done.
Signed-off-by: Valdis Kletnieks
---
diff --git
+++ Matthias Maennich [27/09/19 14:41 +0100]:
On Fri, Sep 27, 2019 at 06:35:56PM +0900, Masahiro Yamada wrote:
I was hit by some problems caused by the module namespace feature
that was merged recently. At least, the breakage of
external module builds is a fatal one. I just took a look at the
Hi Will,
On Wed, Oct 02, 2019 at 02:19:29PM +0100, Will Deacon wrote:
> On Wed, Oct 02, 2019 at 04:09:13PM +0300, Laurent Pinchart wrote:
> > Thank you for the patch.
>
> And thank you for the quick response.
>
> > On Wed, Oct 02, 2019 at 12:27:53PM +0100, Will Deacon wrote:
> > > I don't have
On Thu, Sep 26, 2019 at 7:17 PM Yang Weijiang wrote:
>
> "Load Guest CET state" bit controls whether Guest CET states
> will be loaded at Guest entry. Before doing that, KVM needs
> to check if CPU CET feature is enabled on host and available
> to Guest.
>
> Note: SHSTK and IBT features share one
On 02.10.19 00:53, Eric W. Biederman wrote:
Kees Cook writes:
As there appear to be no users of the sysctl system call, remove the
code>...
I copied everyone who had put this into a defconfig and I will wait a
little more to see if anyone screams. I think it is a safe guess that
several
On 02-Okt 11:45, Alexei Starovoitov wrote:
> On Wed, Oct 02, 2019 at 07:46:32PM +0200, KP Singh wrote:
> > From: KP Singh
> >
> > Rename asm_goto_workaround.h to asm_workaround.h and add a
> > workaround for the newly added "asm_inline" in:
> >
> > commit eb111869301e ("compiler-types.h: add
On Wed, Oct 02, 2019 at 02:55:50PM +0200, Geert Uytterhoeven wrote:
> On Wed, Oct 2, 2019 at 6:33 AM Nick Desaulniers
> wrote:
> > On Tue, Oct 1, 2019 at 11:14 AM Russell King - ARM Linux admin
> > wrote:
> > > On Tue, Oct 01, 2019 at 11:00:11AM -0700, Nick Desaulniers wrote:
> > > > On Tue,
Em Wed, 2 Oct 2019 19:23:02 +0200
JP escreveu:
> Hi all.
>
> On 10/2/19 5:21 PM, Gonsolo wrote:
> > Hi!
> >
> >> Antti has some great suggestions in that thread:
> >> https://lkml.org/lkml/2017/5/24/245
> >>
> >> Also note https://lkml.org/lkml/2017/5/26/357 if you have access to a
>
On Wed, Oct 02, 2019 at 02:25:52PM +0200, Giovanni Gherdovich wrote:
> > What about KABYLAKE_X and ICELAKE_X ?
>
> KABYLAKE_X: does it exist? I couldn't find it in
> arch/x86/include/asm/intel-family.h (the tip tree), I only see KABYLAKE_L and
> KABYLAKE.
My bad, I must've been staring
On Wed, Oct 02, 2019 at 02:27:54PM +0200, Giovanni Gherdovich wrote:
> On Tue, 2019-09-24 at 18:00 +0200, Peter Zijlstra wrote:
> > On Tue, Sep 24, 2019 at 04:03:32PM +0200, Peter Zijlstra wrote:
> >
> > > > I'll check what's the cost of static_cpu_has() and if it's
> > > > non-negligible I'll
>
On Wed, Oct 02, 2019 at 07:46:32PM +0200, KP Singh wrote:
> From: KP Singh
>
> Rename asm_goto_workaround.h to asm_workaround.h and add a
> workaround for the newly added "asm_inline" in:
>
> commit eb111869301e ("compiler-types.h: add asm_inline definition")
>
> Add missing include for
Hello
On 10/2/19 1:36 PM, Pavel Machek wrote:
On Wed 2019-10-02 11:34:00, Dan Murphy wrote:
The LED_COLOR_MAX_ID is incorrect. THe MAX_ID should
be the last COLOR_ID in the list. If an array was allocate
with MAX_ID the allocation would be correct but the meaning
is wrong.
So for array
02.10.2019 02:35, Chanwoo Choi пишет:
> Hi,
>
> On 19. 8. 12. 오전 6:23, Dmitry Osipenko wrote:
>> There are cases where unnecessary ACTMON interrupts could be avoided,
>> like when one memory client device requests higher clock rate than the
>> other or when clock rate is manually limited using
Tracking the performance state can be useful for
debugging/understanding power domain behavior.
Signed-off-by: Matthias Kaehlcke
---
Changes in v2:
- split original patch in two, one for genpd_set_performance_state
one for genpd_power_on/off
- updated commit message (original subject was "PM
The events can be useful for power analysis/optimization, e.g.
to track the state of power domains during suspend/resume on
battery powered devices.
Signed-off-by: Matthias Kaehlcke
---
Changes in v2:
- split original patch in two, one for genpd_power_on/off and
one for
On Wed 2019-10-02 11:34:00, Dan Murphy wrote:
> The LED_COLOR_MAX_ID is incorrect. THe MAX_ID should
> be the last COLOR_ID in the list. If an array was allocate
> with MAX_ID the allocation would be correct but the meaning
> is wrong.
>
> So for array allocation the code should use
On Wed, Oct 02, 2019 at 02:26:44PM +0200, Giovanni Gherdovich wrote:
> On Tue, 2019-09-24 at 18:04 +0200, Peter Zijlstra wrote:
> > On Mon, Sep 09, 2019 at 04:42:15AM +0200, Giovanni Gherdovich wrote:
> >
> > > +static void intel_set_cpu_max_freq(void)
> > > +{
> > > + /*
> > > + * TODO: add
On Wed, Oct 02, 2019 at 02:29:25PM +0200, Giovanni Gherdovich wrote:
> +void x86_arch_scale_freq_tick_enable(void)
> +{
> + tick_disable = false;
> +}
> +
> +static void reset_scale_freq(void *arg)
> +{
> + this_cpu_write(arch_cpu_freq, SCHED_CAPACITY_SCALE);
> +}
> +
> +void
301 - 400 of 926 matches
Mail list logo
