>From 9b9af540f2d55d80b4900ff94ca3d2c2980002bf Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Wed, 2 Mar 2016 13:10:41 -0500
The existing sequences of operations ensure that the offlining csses
are drained before cgroup_update_dfl_csses(), so even though
cgroup_update_dfl_csses() uses css_for_eac
On Wed, Mar 02, 2016 at 09:53:28AM -0800, H. Peter Anvin wrote:
> Please explain why we can't use rip-relative addressing in some form...
We *can* do almost what Brian suggested:
movqstack_start(%rip), %rsp
subq$__START_KERNEL_map, %rsp
But we still have to subtract __STA
On Tue, 2016-02-23 at 12:21 -0800, Joe Perches wrote:
> The existing logging macros are fairly large and converting the
> macros to functions make the object code smaller.
Artem and Adrian are the nominal maintainers for ubifs.
Artem last had a sign-off on a ubifs patch 6 months ago and
Adrian's
On Tue, Mar 01, 2016 at 04:59:39PM +0800, Chao Yu wrote:
> Hi Yang,
>
> > -Original Message-
> > From: Yang Shi [mailto:yang@linaro.org]
> > Sent: Saturday, February 27, 2016 8:25 AM
> > To: jaeg...@kernel.org; cm224@samsung.com; chao2...@samsung.com;
> > t...@linutronix.de;
> > r
On 02/03/2016 19:07, Rob Herring wrote:
> On Thu, Feb 25, 2016 at 11:37:10AM +0100, John Crispin wrote:
>> Signed-off-by: John Crispin
>> Cc: devicet...@vger.kernel.org
>> ---
>> This patch needs to be merged post-rc1 as it depends on the MFD series of
>> the PMIC which is already inside Lee's t
On 2 March 2016 at 19:13, Rob Herring wrote:
> On Thu, Feb 25, 2016 at 11:04:47PM +0100, Joachim Eastwood wrote:
>> Add binding documentation for NXP LPC1850 GPIO Pin Interrupt (PINT)
>> controller.
>>
>> Signed-off-by: Joachim Eastwood
>> ---
>> .../interrupt-controller/nxp,lpc1850-gpio-pint.tx
On March 2, 2016 10:15:56 AM PST, Borislav Petkov wrote:
>On Wed, Mar 02, 2016 at 09:53:28AM -0800, H. Peter Anvin wrote:
>> Please explain why we can't use rip-relative addressing in some
>form...
>
>We *can* do almost what Brian suggested:
>
>movqstack_start(%rip), %rsp
>subq
On Thu, Feb 25, 2016 at 04:36:36PM -0600, Franklin S Cooper Jr wrote:
> From: Vignesh R
>
> Add PWMSS device tree nodes for DRA7 SoC family and add documentation
> for dt bindings.
>
> Signed-off-by: Vignesh R
> ---
> Version 3 changes:
> None
>
> .../devicetree/bindings/pwm/pwm-tiehrpwm.txt
On 3/1/2016 2:43 PM, Bjorn Helgaas wrote:
> On Tue, Mar 01, 2016 at 01:49:34PM -0500, Sinan Kaya wrote:
>>> There's so much code there, that I think all the code obscures the
>>> fact that there's almost nothing really happening. In broad outline,
>>> I think we care about:
>>>
>>> - the legacy
This patch adds policy.c supporting context management.
1. For ioctls:
- fscrypt_process_policy
- fscrypt_get_policy
2. For context permission
- fscrypt_has_permitted_context
- fscrypt_inherit_context
Signed-off-by: Michael Halcrow
Signed-off-by: Theodore Ts'o
Signed-off-by: Ildar Muslukho
This patch adds keyinfo.c supporting key management.
- fscrypt_get_encryption_info
- fscrypt_free_encryption_info
Signed-off-by: Michael Halcrow
Signed-off-by: Ildar Muslukhov
Signed-off-by: Theodore Ts'o
Signed-off-by: Jaegeuk Kim
---
fs/crypto/keyinfo.c | 278 +++
This patch is to support the following ext4 crypto change.
commit 28b4c263961c47da84ed8b5be0b5116bad1133eb
Author: Theodore Ts'o
Date: Sun Feb 7 19:35:05 2016 -0500
ext4 crypto: revalidate dentry after adding or removing the key
Cc: Theodore Ts'o
Cc: Al Viro
Signed-off-by: Jaegeuk Kim
On 2/26/2016 12:15 PM, Eric Auger wrote:
>> -module_init(reset ## _module_init); \
>> > +#define module_vfio_reset_handler(compat, acpihid, reset) \
>> > +MODULE_ALIAS("vfio-reset:" compat);
>> > \
> Here you need to handle alia
Since ezchip network driver is written with big endian EZChip platform it
is necessary to add support for little endian architecture.
The first issue is that the order of the bits in a bit field is
implementation specific. So all the bit fields are removed.
Named constants are used to access neces
This patch tries to catch up with lookup and open policies in ext4.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/dir.c | 2 +-
fs/f2fs/file.c | 4
fs/f2fs/namei.c | 23 +++
3 files changed, 28 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c
index
This patch removes the most parts of internal crypto codes.
And then, it modifies and adds some ext4-specific crypt codes to use the generic
facility.
Signed-off-by: Jaegeuk Kim
---
fs/ext4/Kconfig | 12 +-
fs/ext4/Makefile| 2 -
fs/ext4/crypto.c| 525 -
This patch adds a facility to enable per-file encryption.
Arnd fixes a missing CONFIG_BLOCK check in the original patch.
"The newly added generic crypto abstraction for file systems operates
on 'struct bio' objects, which do not exist when CONFIG_BLOCK is
disabled:
fs/crypto/crypto.c: In function
On 03/02/16 10:15, Borislav Petkov wrote:
> On Wed, Mar 02, 2016 at 09:53:28AM -0800, H. Peter Anvin wrote:
>> Please explain why we can't use rip-relative addressing in some form...
>
> We *can* do almost what Brian suggested:
>
> movqstack_start(%rip), %rsp
> subq$__STAR
This patch adds definitions for per-file encryption used by ext4 and f2fs.
Signed-off-by: Jaegeuk Kim
---
include/linux/fs.h | 8 ++
include/linux/fscrypto.h | 239 +++
include/uapi/linux/fs.h | 18
3 files changed, 265 insertions(+)
cr
This patch removes the most parts of internal crypto codes.
And then, it modifies some f2fs-specific crypt codes to use the generic
facility.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/Kconfig | 10 +-
fs/f2fs/Makefile| 2 -
fs/f2fs/crypto.c| 473 --
On Fri, Feb 26, 2016 at 11:51:50AM +0100, Alexandre TORGUE wrote:
> Signed-off-by: Alexandre TORGUE
>
> diff --git a/Documentation/devicetree/bindings/net/stm32-dwmac.txt
> b/Documentation/devicetree/bindings/net/stm32-dwmac.txt
> new file mode 100644
> index 000..67fceda
> --- /dev/null
> +
Change log from v2:
- add missing Kconfig
- support module compilation
- change some data types to u8
Jaegeuk Kim (10):
fs crypto: add basic definitions for per-file encryption
fs crypto: add crypto.c for encrypt/decrypt functions
fs crypto: add policy.c to handle contexts
fs crypto: ad
This patch adds crypto.c supporting encrypting and decrypting functions.
1. IO preparation:
- fscrypt_get_ctx / fscrypt_release_ctx
2. before IOs:
- fscrypt_encrypt_page
- fscrypt_decrypt_page
- fscrypt_zeroout_range
3. after IOs:
- fscrypt_decrypt_bio_pages
- fscrypt_pullback_bio_pa
This patch adds fname.c supporting filename encryption.
1. general wrapper functions
- fscrypt_fname_disk_to_usr
- fscrypt_fname_usr_to_disk
- fscrypt_setup_filename
- fscrypt_free_filename
2. specific filename handling functions
- fscrypt_fname_alloc_buffer
- fscrypt_fname_free_buffer
Sig
On Wed, Mar 2, 2016 at 5:59 AM, Srinivas Kandagatla
wrote:
>
> On 01/03/16 16:59, Andrey Smirnov wrote:
>>
>> Add 'nvmem-composite' driver which allows to combine multiple chunks of
>> various NVMEM cells into a single continuous NVMEM device.
>
>
> My plan on this feature was add support inside t
On 2/26/2016 11:52 AM, Timur Tabi wrote:
> Sinan Kaya wrote:
>> Hi Marc Zyngier, Mark Rutland;
>>
>> I'm looking forward to hear your feedback on this series.
>
> Would it be possible to get this patchset into 4.6? We're already at v14,
> and there have been no review comments since this patch w
From: Amitoj Kaur Chawla
Date: Wed, 2 Mar 2016 19:52:42 +0530
> Specifically, pcim_release contains the following code:
How incredibly unintuitive that PCI helper functions magically become
managed just because a driver invoked pcim_enable_device().
Well, if that's what is it, that's what it is
From: Antonio Quartulli
Date: Wed, 2 Mar 2016 22:46:07 +0800
> On Wed, Mar 02, 2016 at 02:54:35PM +0100, Arnd Bergmann wrote:
>> The driver calls cfg80211_get_station, which may be part of a
>> module, so we must not enable BATMAN_ADV_BATMAN_V if
>> BATMAN_ADV=y and CFG80211=m:
>>
>> net/built-i
On Fri, Feb 26, 2016 at 01:32:53PM +0300, Kirill A. Shutemov wrote:
> Could you elaborate on problems with rmap? I have looked into this deeply
> yet.
>
> Do you see anything what would prevent following basic scheme:
>
> - Identify series of small pages as candidate for collapsing into
>a c
On Fri, Feb 26, 2016 at 03:21:33PM +0100, John Crispin wrote:
> Add three files. One describes the actual frame engine, the other two
> describe fast ethernet and gigabit switches bindings.
>
> Signed-off-by: John Crispin
> Signed-off-by: Felix Fietkau
> Signed-off-by: Michael Lee
Does this re
On Tue, Mar 01, 2016 at 06:38:12PM -0700, Shuah Khan wrote:
> On 03/01/2016 04:53 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.4 release.
> > There are 342 patches in this series, all will be posted as a response
> > to this one. If anyone has any issu
On 02/03/2016 19:46, Rob Herring wrote:
> On Fri, Feb 26, 2016 at 03:21:33PM +0100, John Crispin wrote:
>> Add three files. One describes the actual frame engine, the other two
>> describe fast ethernet and gigabit switches bindings.
>>
>> Signed-off-by: John Crispin
>> Signed-off-by: Felix Fiet
On Wed, 2 Mar 2016, Rob Herring wrote:
> On Fri, Feb 26, 2016 at 3:44 PM, Alan Tull
> wrote:
> > This patch add of overlay notifications.
> >
> > When DT overlays are being added, some drivers/subsystems
> > need to see device tree overlays before the changes go into
> > the live tree.
> >
> > T
On Tue, Mar 1, 2016 at 8:09 PM, Darrick J. Wong wrote:
> Create a new ioctl to expose the block layer's newfound ability to
> issue either a zeroing discard, a WRITE SAME with a zero page, or a
> regular write with the zero page. This BLKZEROOUT2 ioctl takes
> {start, length, flags} as parameters
On 03/02/2016 04:21 PM, Javier González wrote:
An Open-Channel SSD can work on two modes: (i) hybrid mode, where the
L2P table is maintained both by the host and by the device; and (ii)
full host-based, where the L2P table is uniquely maintained by the host.
The current rrpc target operates on hy
On Wed, 2016-03-02 at 19:46 +0100, Richard Weinberger wrote:
> Am 02.03.2016 7:19 nachm. schrieb Joe Perches :
> > On Tue, 2016-02-23 at 12:21 -0800, Joe Perches wrote:
> > > The existing logging macros are fairly large and converting the
> > > macros to functions make the object code smaller.
>
Enable Application Data Integrity (ADI) support in the sparc
kernel for applications to use ADI in userspace. ADI is a new
feature supported on sparc M7 and newer processors. ADI is supported
for data fetches only and not instruction fetches. This patch adds
prctl commands to enable and disable AD
From: Chunhao Lin
Date: Thu, 3 Mar 2016 00:59:15 +0800
> For RTL8168G/RTL8168H/RTL8411B/RTL8107E, enable this flag to eliminate
> message "AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0002
> address=0x3000 flags=0x0050] in dmesg.
>
> Signed-off-by: Chunhao Lin
Applie
On Sat, Feb 27, 2016 at 12:37:57PM +0100, luca abeni wrote:
> Subject: sched/core: fix __sched_setscheduler() to properly invoke
> prio_changed_dl()
>
> Currently, prio_changed_dl() is not called when __sched_setscheduler()
> changes the parameters of a SCHED_DEADLINE task. This happens because
>
On Mar 2, 2016 6:29 AM, "Borislav Petkov" wrote:
>
> On Wed, Mar 02, 2016 at 02:01:15PM +, One Thousand Gnomes wrote:
> > int main(void) is wrong as there are passed arguments
>
> Not in this particular case - test doesn't take args.
IIRC the C standard says otherwise. main is special.
Argua
The icn driver currently produces an unconditional #warning whenever
we build it, introduced by Karsten Keil back in 2003:
#warning TODO test headroom or use skb->nb to flag ACK
Karsten's original commit (from BitKeeper) contains this description:
- here are lot of bugs left, so ISDN is not
The icn, act2000 and pcbit drivers are all for very old hardware,
and it is highly unlikely that anyone is actually still using them
on modern kernels, if at all.
All three drivers apparently are for hardware that predates PCI
being the common connector, as they are ISA-only and active
PCI ISDN ca
On Tuesday 01 March 2016 08:49:10 Krzysztof Hałasa wrote:
> Signed-off-by: Krzysztof Hałasa
>
Applied to next/fixes-non-critical, with this changelog
added:
commit 59e430525b1f966edf2573256d78bf63c7561433
Author: Krzysztof Hałasa
Date: Tue Mar 1 08:49:10 2016 +0100
CNS3xxx: remove unuse
From: Santosh Shilimkar
Date: Tue, 1 Mar 2016 15:20:41 -0800
> v3:
> Re-generated the same series by omitting "-D" option from git format-patch
> command. Since first patch has file removals, git apply/am can't deal
> with it when formated with '-D' option.
Yeah this works much better, series
On 3/2/2016 11:13 AM, David Miller wrote:
From: Santosh Shilimkar
Date: Tue, 1 Mar 2016 15:20:41 -0800
v3:
Re-generated the same series by omitting "-D" option from git format-patch
command. Since first patch has file removals, git apply/am can't deal
with it when formated with '-D' option.
Hi Joe,
Locally I will remove the patch and use the '--ignore' option.
Is there anything I need to do for upstream? (Sorry, I am new to submitting
patches upstream)
-Dwane
-Original Message-
From: Joe Perches [mailto:j...@perches.com]
Sent: Tuesday, March 1, 2016 3:22 PM
To: Pottra
On Wed, 2016-03-02 at 19:15 +, Pottratz, Dwane wrote:
> Hi Joe,
Hello again Dwane.
> Locally I will remove the patch and use the '--ignore' option.
That's good, thanks.
> Is there anything I need to do for upstream?
No, I think it's fine as-is.
Thanks for the patch, it was fine, but it
Hi Tejun,
On Wed, Mar 2, 2016 at 11:10 PM, Tejun Heo wrote:
> Hello, Parav.
>
> It doesn't look like my reviews are getting through. For now,
>
I have addressed all the review comments that you provided in v5 patch.
I admit that few comments have not followed CodingStyle and I owe to
fix it, whi
On Wed, Mar 02, 2016 at 11:03:44AM -0800, Andy Lutomirski wrote:
> IIRC the C standard says otherwise. main is special.
My C99 draft pdf says either "int main(void)" or "int main(int argc,
char *argv[])".
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
Document the color extension in Documentation/leds/leds-class.txt
Signed-off-by: Heiner Kallweit
---
v2:
- introduced to patch series
v3:
- document extension in more detail
v4:
- Better explain why flag LED_SET_HUE_SAT is needed
v5:
- no changes
v6:
- add docu for this feature to Documentation/A
> -Original Message-
> From: Greg KH [mailto:g...@kroah.com]
> Sent: Wednesday, March 02, 2016 11:44 AM
> To: Thomas Gleixner
> Cc: Stephen Rothwell ; Ingo Molnar
> ; H. Peter Anvin ; Peter Zijlstra
> ; linux-n...@vger.kernel.org; linux-
> ker...@vger.kernel.org; J. German Rivera ;
> Qais
Since f_midi_transmit is called by both ALSA and USB frameworks, it can
potentially cause a race condition between both calls. This is bad because the
way f_midi_transmit is implemented can't handle concurrent calls. This is due
to the fact that the usb request fifo looks for the next element and o
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 77 +++-
1 file changed, 40 insertions(+), 37 deletions(-)
diff --git a/drivers/usb/gadget/function/f_midi.c
b/drivers/usb/gadget/function/f_midi.c
index 8475e3dc82d4..9a9e6112e224 100644
Patches are pretty much self-described.
Patch 1 is revised from comments.
Patch 2 is a bug fix.
Felipe F. Tonello (5):
usb: gadget: f_midi: refactor state machine
usb: gadget: f_midi: added spinlock on transmit function
usb: gadget: gmidi: remove bus powered requirement on bmAttributes
us
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/gadget/function/f_midi.c
b/drivers/usb/gadget/function/f_midi.c
index 9a9e6112e224..5c7f5c780fda 100644
--- a/drivers/usb/gadget/function/f_midi.c
+++ b/dr
This gadget uses a bmAttributes and MaxPower that requires the USB bus to be
powered from the host, which is not correct because this configuration is device
specific, not a USB-MIDI requirement.
This patch adds two modules parameters, bmAttributes and MaxPower, that allows
the user to set those f
On Tue, Mar 01, 2016 at 02:59:06PM -0800, Doug Anderson wrote:
> Guenter,
>
> On Sun, Feb 28, 2016 at 1:12 PM, Guenter Roeck wrote:
> > Convert driver to use watchdog infrastructure. This includes
> > infrastructure support to handle watchdog keepalive if the watchdog
> > is running while the wat
On Wed, Mar 02, 2016 at 01:43:42AM +0100, Luis R. Rodriguez wrote:
> On Wed, Feb 24, 2016 at 09:32:59AM +0100, Ingo Molnar wrote:
> There's only one problem with this strategy I can think so far which differs
> from my original approach, which is partly why I actually started looking at
> this stuf
This refactor results in a cleaner state machine code and as a result fixed a
bug when packaging a USB-MIDI packet right after a non-conformant MIDI byte
stream.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 204 ++-
1 file changed,
On 02/29/2016 05:20 PM, Tony Lindgren wrote:
> * Franklin S Cooper Jr. [160229 15:12]:
>>
>> On 02/29/2016 04:55 PM, Tony Lindgren wrote:
>>> * Franklin S Cooper Jr. [160229 14:31]:
On 02/29/2016 04:04 PM, Tony Lindgren wrote:
> Hmm but why are you also removing the pm_runtime calls? T
On Wed, Mar 02, 2016 at 09:56:51AM +0100, Dmitry Vyukov wrote:
> On Fri, Jan 15, 2016 at 8:11 PM, Dmitry Vyukov wrote:
> > On Fri, Jan 15, 2016 at 7:46 PM, Marcelo Ricardo Leitner
> > wrote:
> >> On Wed, Dec 30, 2015 at 09:42:27PM +0100, Dmitry Vyukov wrote:
> >>> Hello,
> >>>
> >>> The following
Hi Emil,
2016-03-02 Emil Velikov :
> On 1 March 2016 at 13:13, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Play safe and add flags member to all structs. So we don't need to
> > break API or create new IOCTL in the future if new features that requires
> > flags arises.
> >
> > v2:
On Wed, Mar 02, 2016 at 10:39:05AM -0800, H. Peter Anvin wrote:
> Well, we definitely should use %rip-relative addressing if we can.
Right you are.
> However, even so I believe this breaks if the kernel is loaded anywhere
> but its default load address. I think we need to do something like:
>
>
Hi Steve,
On Wed, 2016-03-02 at 12:39 -0500, Steven Rostedt wrote:
> On Fri, 26 Feb 2016 10:01:13 -0600
> Tom Zanussi wrote:
>
>
> > +static void hist_trigger_elt_copy(struct tracing_map_elt *to,
> > + struct tracing_map_elt *from)
> > +{
> > + char *comm_from = fr
From: Gustavo Padovan
We don't use the 'fence' name to refer to sync_file anymore. So rename it
to SYNC_IOC_FILE_INFO.
Signed-off-by: Gustavo Padovan
Reviewed-by: Maarten Lankhorst
---
drivers/staging/android/sync.c | 2 +-
drivers/staging/android/uapi/sync.h | 2 +-
2 files changed, 2 i
From: Gustavo Padovan
Change order of the field to avoid alignment issues with 64 bits
platforms.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/uapi/sync.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/android/uapi/sync.h
b/drivers/stagin
From: Gustavo Padovan
Change SYNC_IOC_FILE_INFO behaviour to avoid future API breaks and
optimize buffer
Now num_fences can be filled by the caller to inform how many fences it
wants to retrieve from the kernel. If the num_fences passed is greater
than zero info->sync_fence_info should point to
From: Gustavo Padovan
Play safe and add flags member to all structs. So we don't need to
break API or create new IOCTL in the future if new features that requires
flags arises.
v2: check if flags are valid (zero, in this case)
v3: return -EINVAL if flags are not zero'ed
v4: add padding for 64-
From: Gustavo Padovan
struct sync_merge_data already have documentation on top of the
struct definition. No need to duplicate it.
Signed-off-by: Gustavo Padovan
Reviewed-by: Maarten Lankhorst
---
drivers/staging/android/uapi/sync.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
From: Gustavo Padovan
Inform userspace how many fences are in the sync_fence_info field.
Signed-off-by: Gustavo Padovan
Reviewed-by: Maarten Lankhorst
---
drivers/staging/android/sync.c | 2 ++
drivers/staging/android/uapi/sync.h | 2 ++
2 files changed, 4 insertions(+)
diff --git a/dri
On Wednesday 02 March 2016 16:46:47 Joao Pinto wrote:
> On 2/19/2016 3:03 PM, Arnd Bergmann wrote:
> > On Thursday 18 February 2016 17:20:27 Joao Pinto wrote:
> >> diff --git a/Documentation/devicetree/bindings/ufs/ufs-dwc.txt
> >> b/Documentation/devicetree/bindings/ufs/ufs-dwc.txt
> > Please fo
On Tue, 02 Feb 2016, Davidlohr Bueso wrote:
I've just hit this issue myself and remembered this thread :)
Paul, folks, does the below patch look reasonable to you? If so
I can properly resend. thanks.
On Mon, 01 Feb 2016, Paul E. McKenney wrote:
On Mon, Feb 01, 2016 at 11:28:07AM +0800, Kefe
On Wed, Mar 2, 2016 at 11:09 PM, Tejun Heo wrote:
> Hello,
>
>> +struct rdma_cgroup {
>> + struct cgroup_subsys_state css;
>> +
>> + spinlock_t rpool_list_lock; /* protects resource pool list */
>> + struct list_head rpool_head;/* head to keep track of all resource
>> +
On Wed, 2 Mar 2016, Peter Zijlstra wrote:
> On Tue, Mar 01, 2016 at 11:55:01AM -0800, tip-bot for Thomas Gleixner wrote:
> > Commit-ID: 757c989b9994f51b42d6be1bd33c7c12d16a3ac7
> > Gitweb:
> > http://git.kernel.org/tip/757c989b9994f51b42d6be1bd33c7c12d16a3ac7
> > Author: Thomas Gleixner
From: Lars Persson
Date: Mon, 29 Feb 2016 16:22:29 +0100
> This series has bug fixes for the dwc_eth_qos ethernet driver.
>
> Mainly two stability fixes for problems found by Rabin Vincent:
> - Successive starts and stops of the interface would trigger a DMA reset
> timeout.
> - A race conditio
From: Eric Engestrom
Date: Mon, 29 Feb 2016 16:40:23 +
> Left over from c24588afc536a35c924d014f13b669b20ccf8553
> ("atl1c: using fixed TXQ configuration for l2cb and l1c")
>
> Signed-off-by: Eric Engestrom
Applied.
From: Eric Engestrom
Date: Mon, 29 Feb 2016 16:36:38 +
> 3b766cd832328fcb87db3507e7b98cf42f21689d ("net/core: Add reading VF
> statistics through the PF netdevice") added that variable but it's never
> been used.
>
> Signed-off-by: Eric Engestrom
Applied.
From: Eric Engestrom
Date: Mon, 29 Feb 2016 16:34:25 +
> This format hasn't been used since 04ed3e741d0f133e02bed7fa5c98edba128f90e7
> ("net: change netdev->features to u32")
>
> Signed-off-by: Eric Engestrom
A patch that does this is already in the networking tree, please always
check the
From: Eric Engestrom
Date: Mon, 29 Feb 2016 16:38:06 +
> 8cc785f6f429c2a3fb81745dc142cbd72a462c4a ("net: ipv4: make the ping
> /proc code AF-independent") removed the code using it, but renamed this
> variable instead of removing it.
>
> Signed-off-by: Eric Engestrom
Applied.
On Wednesday 02 March 2016 21:38:04 Lada Trimasova wrote:
> Since ezchip network driver is written with big endian EZChip platform it
> is necessary to add support for little endian architecture.
>
> The first issue is that the order of the bits in a bit field is
> implementation specific. So all
In commit f01f17d3705b ("mm, vmstat: make quiet_vmstat lighter")
the quiet_vmstat() function became asynchronous, in the sense that
the vmstat work was still scheduled to run on the core when the
function returned. For task isolation, we need a synchronous
version of the function that guarantees t
Here is the latest version of the task-isolation patch set, adopting
various suggestions made about the v9 patch series, including some
feedback from testing on the new EZchip NPS ARC platform (although the
new arch/arc support is not included in this patch series). All of the
suggestions were rel
With task_isolation mode, the task is in principle guaranteed not to
be interrupted by the kernel, but only if it behaves. In particular,
if it enters the kernel via system call, page fault, or any of a
number of other synchronous traps, it may be unexpectedly exposed
to long latencies. Add a sim
In prepare_exit_to_usermode(), call task_isolation_ready()
when we are checking the thread-info flags, and after we've handled
the other work, call task_isolation_enter() unconditionally.
In syscall_trace_enter_phase1(), we add the necessary support for
strict-mode detection of syscalls.
We add s
Currently ret_fast_syscall, work_pending, and ret_to_user form an ad-hoc
state machine that can be difficult to reason about due to duplicated
code and a large number of branch targets.
This patch factors the common logic out into the existing
do_notify_resume function, converting the code to C in
In do_notify_resume(), call task_isolation_ready() when we are
checking the thread-info flags; and after we've handled the other
work, call task_isolation_enter() unconditionally. To ensure we
always call task_isolation_enter() when returning to userspace,
modify _TIF_WORK_MASK to be _TIF_NOHZ, wh
When the schedule tick is disabled in tick_nohz_stop_sched_tick(),
we call hrtimer_cancel(), which eventually calls down into
__remove_hrtimer() and thus into hrtimer_force_reprogram().
That function's call to tick_program_event() detects that
we are trying to set the expiration to KTIME_MAX and ca
This per-cpu check was being done in the loop in lru_add_drain_all(),
but having it be callable for a particular cpu is helpful for the
task-isolation patches.
Signed-off-by: Chris Metcalf
---
include/linux/swap.h | 1 +
mm/swap.c| 15 ++-
2 files changed, 11 insertions(
The new "task_isolation_debug" flag simplifies debugging
of TASK_ISOLATION kernels when processes are running in
PR_TASK_ISOLATION_ENABLE mode. Such processes should get no
interrupts from the kernel, and if they do, when this boot flag is
specified a kernel stack dump on the console is generated.
On Tue, Mar 01, 2016 at 11:58:59AM -0800, tip-bot for Thomas Gleixner wrote:
> Commit-ID: 27d50c7eeb0f03c3d3ca72aac4d2dd487ca1f3f0
> Gitweb: http://git.kernel.org/tip/27d50c7eeb0f03c3d3ca72aac4d2dd487ca1f3f0
> Author: Thomas Gleixner
> AuthorDate: Fri, 26 Feb 2016 18:43:44 +
> Committ
This option, similar to NO_HZ_FULL_ALL, simplifies configuring
a system to boot by default with all cores except the boot core
running in task isolation mode.
---
init/Kconfig | 10 ++
kernel/isolation.c | 6 ++
2 files changed, 16 insertions(+)
diff --git a/init/Kconfig b/init
The existing nohz_full mode is designed as a "soft" isolation mode
that makes tradeoffs to minimize userspace interruptions while
still attempting to avoid overheads in the kernel entry/exit path,
to provide 100% kernel semantics, etc.
However, some applications require a "hard" commitment from th
3.4.110-rt140-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
With interrupts off it makes no sense to do the long path since we can't
leave the CPU anyway. Also we might end up in a recursion with lockdep.
Signed-of
3.4.110-rt140-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Clark Williams
RT has dropped support of rcu_bh, comment out in rcutorture.
Signed-off-by: Clark Williams
Signed-off-by: Sebastian Andrzej Siewior
Signed-off-by: Thomas Gleixner
Dear RT Folks,
This is the RT stable review cycle of patch 3.4.110-rt140-rc1.
Please scream at me if I messed something up. Please test the patches too.
The -rc release will be uploaded to kernel.org and will be deleted when
the final release is out. This is just a review release (or release ca
3.4.110-rt140-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
preempt_disable() invokes preempt_count_add() which saves the caller in
current->preempt_disable_ip. It uses CALLER_ADDR1 which does not look for its
calle
3.4.110-rt140-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Yang Shi
When running -rt kernel with both PREEMPT_OFF_HIST and LOCKDEP enabled,
the below error is reported:
[ INFO: suspicious RCU usage. ]
4.4.1-rt6 #1 Not tainted
include/tr
Based on the proposed RGB LED core extension the thingm driver was
changed to make use of this extension. It allows to simplify
the code a lot. For now primary purpose of this patch is to facilitate
testing of the RGB LED core extension.
I didn't find a way to split the patch into smaller parts as
On Wed, 2 Mar 2016 20:02:58 +0100
Peter Zijlstra wrote:
> On Sat, Feb 27, 2016 at 12:37:57PM +0100, luca abeni wrote:
> > Subject: sched/core: fix __sched_setscheduler() to properly invoke
> > prio_changed_dl()
> >
> > Currently, prio_changed_dl() is not called when __sched_setscheduler()
> > c
On Tuesday 01 March 2016 18:37:20 Krzysztof Kozlowski wrote:
>
> Second pull request with DT changes for v4.6.
> This is on top of previous DT changes
Pulled into next/dt, thanks!
Arnd
801 - 900 of 1085 matches
Mail list logo
