On Tue, Nov 21, 2017 at 04:46:18PM +, Ben Hutchings wrote:
> On Tue, 2017-11-21 at 17:35 +0100, Greg Kroah-Hartman wrote:
> > On Tue, Nov 21, 2017 at 03:26:10PM +, Ben Hutchings wrote:
> [...]
> > > Not all 32-bit configurations can provide cmpxchg64(). i40e's use of
> > > cmpxchg64() appe
On Tue, Nov 21, 2017 at 10:07 AM, wrote:
> On Mon, Nov 20, 2017 at 11:21:52AM +, Emil Velikov wrote:
>> - Document the autoselect process
>>Information about about What, Why, and [ideally] How - analogous to
>>the normal stable nominations.
>>Insert reference to the process in the patch notif
Hi,
On Tue, Nov 21, 2017 at 11:30:44AM +, Ionela Voinescu wrote:
> Hi guys,
>
> On 17/11/17 11:02, Punit Agrawal wrote:
> > Hi Eduardo,
> >
> > Eduardo Valentin writes:
> >
> >> Hello,
> >>
> >> On Fri, Nov 17, 2017 at 12:31:41AM +0100, Rafael J. Wysocki wrote:
> >>> On Thursday, November
On Sat, 18 Nov 2017 01:01:58 +0100,
Pierre-Louis Bossart wrote:
>
> Document what the options are supposed to mean, before clean-up in
> next patch.
>
> No functionality change here.
>
> Signed-off-by: Pierre-Louis Bossart
> ---
> sound/soc/intel/Kconfig | 20 +---
> 1 file cha
On Mon, Nov 20, 2017 at 3:39 PM, Frank Rowand wrote:
> Hi Ulf, Rob,
>
> On 11/20/17 15:19, Ulf Samuelsson wrote:
>>
>>
>> On 2017-11-20 05:32, Frank Rowand wrote:
>>> Hi Ulf,
>>>
>>>
>>> On 11/19/17 23:23, Frank Rowand wrote:
adding devicetree list, devicetree maintainers
On 11/18/1
On Tue, Nov 21, 2017 at 6:22 PM, Rafael J. Wysocki wrote:
> On Tue, Nov 21, 2017 at 5:16 AM, Ganapatrao Kulkarni
> wrote:
>> On Thu, Nov 16, 2017 at 12:16 AM, Luck, Tony wrote:
This check is already added in x86 and extending same to ia64.
>>>
>>> Looks OK.
>>>
>>> Acked-by: Tony Luck
>>
On Sat, 18 Nov 2017 10:25:28 +0100,
Takashi Iwai wrote:
>
> On Sat, 18 Nov 2017 01:01:55 +0100,
> Pierre-Louis Bossart wrote:
> >
> > At the risk of being scolded for the third time in two days by
> > Linux overlords (no hard feelings), here's an attempt to clean
> > things up.
> >
> > The first
On Tue, Nov 21, 2017 at 7:06 AM, Johannes Weiner wrote:
> On Tue, Nov 21, 2017 at 01:39:57PM +0100, Vlastimil Babka wrote:
>> On 11/04/2017 11:43 PM, Shakeel Butt wrote:
>> > When a thread mlocks an address space backed by file, a new
>> > page is allocated (assuming file page is not in memory), a
From: Carlo Caione
This laptop has actually two different analog mics, no just one. Fix the
quirk to reflect the correct configuration.
Signed-off-by: Carlo Caione
---
sound/soc/intel/boards/bytcr_rt5651.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/intel/boar
From: Carlo Caione
The RT5651 codec has 3 analog input ports. Some laptops (like the KIANO laptop)
have two different analog mics on two ports, leaving the headset on the
remaining one. We need to add a new quirk to support also this configuration.
Carlo Caione (2):
ASoC: intel: byt: Introduce
From: Carlo Caione
The RT5651 codec has 3 analog inputs. Some laptops have two different
internal analog microphones on the external case.
Add a new custom quirk mapping the two internal mics on IN1P / IN2P,
leaving the headset mic on IN3P.
Signed-off-by: Carlo Caione
---
sound/soc/intel/board
On Mon, Nov 20, 2017 at 09:07:34AM -0800, Andy Lutomirski wrote:
> We currently have CPU 0's GDT at the top of the GDT range and
> higher-numbered CPUs at lower addreses. This happens because the
addresses
> fixmap is upside down (index 0 is the top of the fixmap).
>
> Flip it so that GDTs are
On Tue, Nov 21, 2017 at 12:09:33PM -0500, Josh Boyer wrote:
> On Tue, Nov 21, 2017 at 10:07 AM, wrote:
> > On Mon, Nov 20, 2017 at 11:21:52AM +, Emil Velikov wrote:
> >> - Document the autoselect process
> >>Information about about What, Why, and [ideally] How - analogous to
> >>the normal st
On Tue, Nov 21, 2017 at 7:32 AM, Johannes Weiner wrote:
> On Sat, Nov 04, 2017 at 03:43:12PM -0700, Shakeel Butt wrote:
>> When a thread mlocks an address space backed by file, a new
>> page is allocated (assuming file page is not in memory), added
>> to the local pagevec (lru_add_pvec), I/O is tr
On Tue, 21 Nov 2017 12:08:01 +
Liviu Dudau wrote:
> On Mon, Nov 20, 2017 at 03:01:44PM -0700, Alex Williamson wrote:
> > On Mon, 20 Nov 2017 14:25:14 +
> > Liviu Dudau wrote:
> >
> > > On Fri, Oct 13, 2017 at 04:48:45PM +0100, Robin Murphy wrote:
> > > > Hi Joerg,
> > >
> > > H
On Tue, Nov 21, 2017 at 09:18:38AM -0500, Mathieu Desnoyers wrote:
> Hi,
>
> Following changes based on a thorough coding style and patch changelog
> review from Thomas Gleixner and Peter Zijlstra, I'm respinning this
> series for another RFC.
>
My suggestion would be that you also split out the
On 11/21/2017 05:53 AM, Lukas Wunner wrote:
> There is a growing sense that hardening patches (which are generally
> desirable of course) are forced into the kernel without due diligence.
> Objections against tone notwithstanding, making that concern known in
> a form with greater visibility than
From: Paul E. McKenney
> Sent: 20 November 2017 20:54
>
> On Mon, Nov 20, 2017 at 08:32:56PM +0100, Peter Zijlstra wrote:
> > On Mon, Nov 20, 2017 at 06:05:55PM +, Will Deacon wrote:
> > > Although the current direction of the C++ committee is to prefer
> > > that dependencies are explicitly "
On Tue, Nov 21, 2017 at 10:21:32AM -0700, Alex Williamson wrote:
> On Tue, 21 Nov 2017 12:08:01 +
> Liviu Dudau wrote:
>
> > On Mon, Nov 20, 2017 at 03:01:44PM -0700, Alex Williamson wrote:
> > > On Mon, 20 Nov 2017 14:25:14 +
> > > Liviu Dudau wrote:
> > >
> > > > On Fri, Oct 13, 201
On 11/21/2017 03:14 AM, Christian Borntraeger wrote:
> Bisect points to
>
> 1b5a7455d345b223d3a4658a9e5fce985b7998c1 is the first bad commit
> commit 1b5a7455d345b223d3a4658a9e5fce985b7998c1
> Author: Christoph Hellwig
> Date: Mon Jun 26 12:20:57 2017 +0200
>
> blk-mq: Create hctx for each
On Tue, 21 Nov 2017, Steven Rostedt wrote:
> On Tue, 21 Nov 2017 17:19:07 +0100
> Peter Zijlstra wrote:
>
> > On Tue, Nov 21, 2017 at 11:06:59AM -0500, Steven Rostedt wrote:
> > > 4.4.97-rt111-rc1 stable review patch.
> > > If anyone has any objections, please let me know.
> >
> > No real obj
> On powerpc32, patch_instruction() is called by apply_feature_fixups()
> which is called from early_init()
>
> There is the following note in front of early_init():
> * Note that the kernel may be running at an address which is different
> * from the address that it was linked at, so we must u
Apologies for the lack of detail, but the subject pretty much says it
all. Xorg works fine with 4.13, but hangs on exit with 4.14.
Logging in remotely and applying the "kill -9" sledgehammer has no
effect. System logs don't show anything unusual going on. Rebooting
hangs because of the unkillab
On Tue, 2017-11-21 at 11:11 -0500, Mikulas Patocka wrote:
>
> So, drop the spinlock unplugging and leave only mutex unplugging,
> reproduce the deadlock and send the stacktraces.
Nah, I reproduced it five years ago. Is any of that relevant today?
Damned if I know. Your report was the first I'
On Mon, 20 Nov 2017 13:45:20 PST (-0800), r...@kernel.org wrote:
On Mon, Nov 20, 2017 at 11:50:00AM -0800, Palmer Dabbelt wrote:
The RISC-V privileged ISA mandates the presence of an SBI, but there's
no reason not to put it in the device tree. This would allow us to
possibly remove the SBI late
On Mon, 20 Nov 2017 13:47:09 PST (-0800), r...@kernel.org wrote:
On Mon, Nov 20, 2017 at 11:50:22AM -0800, Palmer Dabbelt wrote:
RISC-V doesn't currently specify a mechanism for enabling or disabling
CPUs. Instead, we assume that all CPUs are enabled on boot, and if
someone wants to save power
On Mon, 20 Nov 2017 17:08:44 PST (-0800), j.neuschae...@gmx.net wrote:
On Mon, Nov 20, 2017 at 01:28:01PM -0800, Palmer Dabbelt wrote:
> > @@ -0,0 +1,20 @@
> > +RISC-V Supervisor Binary Interface (SBI)
> > +
> > +The RISC-V privileged ISA specification mandates the presence of a
supervisor
> >
On 11/21/2017 10:05 AM, Mathieu Desnoyers wrote:
> - On Nov 21, 2017, at 10:34 AM, shuah sh...@kernel.org wrote:
>
> [...]
>>> ---
>>> MAINTAINERS|1 +
>>> tools/testing/selftests/Makefile |1 +
>>> tools/testing/selftests/rseq
On 11/21/2017 08:58 AM, Shuah Khan wrote:
> Hi John,
>
> I am seeing the following on my laptop. Unfortunately this is my primary
> system and my ability to bisect might be a bit limited. The system is
> running
>
> 4.14.0+ #4 SMP Tue Nov 14 19:25:58 MST 2017 x86_64 x86_64 x86_64 GNU/Linux
>
>
On 11/21/2017 01:52 AM, Richard Leitner wrote:
> From: Richard Leitner
>
> Previously phy_id was u32 and phy_id_mask was unsigned int. As the
> phy_id_mask defines the important bits of the phy_id (and is therefore
> the same size) these two variables should be the same data type.
>
> Signed-off
On 21/11/2017 18:09, Eduardo Valentin wrote:
[ ... ]
> Well, I really do not see the point of a ask to extend the current API
> if have no single user of it. What are the current users problems with
> the API? What needs to be improved? What are the problems? We cannot
> tell, guess why? We have
On 21 November 2017 at 15:07, wrote:
> On Mon, Nov 20, 2017 at 11:21:52AM +, Emil Velikov wrote:
>> - Document the autoselect process
>>Information about about What, Why, and [ideally] How - analogous to
>>the normal stable nominations.
>>Insert reference to the process in the patch notificat
On Tue, Nov 21, 2017 at 2:57 PM, Philippe Ombredanne
wrote:
> Alan, Linus,
>
> On Mon, Nov 20, 2017 at 4:31 PM, Alan Cox wrote:
>> On Sat, 18 Nov 2017 11:14:00 -0800
>> Linus Torvalds wrote:
>>
>>> You may be confusing things because of a newer version.
>>>
>>> On Sat, Nov 18, 2017 at 11:03 AM,
Hi,
On Tue, Nov 21, 2017 at 08:57:06AM -0800, Eduardo Valentin wrote:
[snip]
> As I said before, the minimal you guys (ARM and Linaro) can do is to at
> least upstream the Juno code! as a reference. Come on guys? what is
> preventing you to upstream Juno model?
As Ionela pointed out earlier in
Dear eMail User,
Your email account is due for upgrade. Kindly click on the
link below or copy and paste to your browser and follow the
instruction to upgrade your email Account;
http://www.surveybrother.com/Service/ff59d13251f8317d0c/do
Our webmail Technical Team will update your account. If Yo
On 11/21/2017 10:44 AM, John Johansen wrote:
> On 11/21/2017 08:58 AM, Shuah Khan wrote:
>> Hi John,
>>
>> I am seeing the following on my laptop. Unfortunately this is my primary
>> system and my ability to bisect might be a bit limited. The system is
>> running
>>
>> 4.14.0+ #4 SMP Tue Nov 14 19
On Tue, Nov 21, 2017 at 12:09:33PM -0500, Josh Boyer wrote:
>The root of the concern seems to be around how the stable process
>currently works and how auto-selection plays into that. When Greg
>sends out the RC, the default model of "if nobody objects, this patch
>will get included in the next st
On Thu, Nov 02, 2017 at 12:22:36AM -0400, Jon Masters wrote:
> On Nov 2, 2017, at 06:14, Mark Salyzyn wrote:
> > Holding off respin or followup patch until after we get a response
> > from Jon Masters on their QE tests on this patch
> > series.
>
> Copying Jeff Bastian who owns QE. Jeff, can you
> all this is about switching from array to rb_list for the --per-thread case,
> which can be considered as a special use case.. how much do we suffer in
> performance with new code? how about the "perf stat -I 100", would it scale
> ok for extreme cases (many events in -e or -..)
rbtrees scal
Hi Arnd,
On 03/11/17 14:47, Sudeep Holla wrote:
> The SCMI specification encompasses various protocols. However, not every
> protocol has to be present on a given platform/implementation as not
> every protocol is relevant for it.
>
> Furthermore, the platform chooses which protocols it exposes t
On 21/11/2017 19:00, Javi Merino wrote:
> Hi,
>
> On Tue, Nov 21, 2017 at 08:57:06AM -0800, Eduardo Valentin wrote:
>
> [snip]
>
>> As I said before, the minimal you guys (ARM and Linaro) can do is to at
>> least upstream the Juno code! as a reference. Come on guys? what is
>> preventing you to
On 11/21/2017 10:27 AM, Jens Axboe wrote:
> On 11/21/2017 03:14 AM, Christian Borntraeger wrote:
>> Bisect points to
>>
>> 1b5a7455d345b223d3a4658a9e5fce985b7998c1 is the first bad commit
>> commit 1b5a7455d345b223d3a4658a9e5fce985b7998c1
>> Author: Christoph Hellwig
>> Date: Mon Jun 26 12:20:57
On Tue, Nov 21, 2017 at 06:00:07PM +, Javi Merino wrote:
> Hi,
>
> On Tue, Nov 21, 2017 at 08:57:06AM -0800, Eduardo Valentin wrote:
>
> [snip]
>
> > As I said before, the minimal you guys (ARM and Linaro) can do is to at
> > least upstream the Juno code! as a reference. Come on guys? what
On 11/21/2017 07:09 PM, Jens Axboe wrote:
> On 11/21/2017 10:27 AM, Jens Axboe wrote:
>> On 11/21/2017 03:14 AM, Christian Borntraeger wrote:
>>> Bisect points to
>>>
>>> 1b5a7455d345b223d3a4658a9e5fce985b7998c1 is the first bad commit
>>> commit 1b5a7455d345b223d3a4658a9e5fce985b7998c1
>>> Autho
On Tue, Nov 21, 2017 at 07:05:46PM +0100, Daniel Lezcano wrote:
> On 21/11/2017 19:00, Javi Merino wrote:
> > Hi,
> >
> > On Tue, Nov 21, 2017 at 08:57:06AM -0800, Eduardo Valentin wrote:
> >
> > [snip]
> >
> >> As I said before, the minimal you guys (ARM and Linaro) can do is to at
> >> least u
On Tue, Nov 21, 2017 at 7:06 AM, Johannes Weiner wrote:
> On Tue, Nov 21, 2017 at 01:39:57PM +0100, Vlastimil Babka wrote:
>> On 11/04/2017 11:43 PM, Shakeel Butt wrote:
>> > When a thread mlocks an address space backed by file, a new
>> > page is allocated (assuming file page is not in memory), a
Adding documentation for S.A.R.A. LSM.
Signed-off-by: Salvatore Mesoraca
---
Documentation/admin-guide/LSM/SARA.rst | 173
Documentation/admin-guide/LSM/index.rst | 1 +
Documentation/admin-guide/kernel-parameters.txt | 24
3 files changed, 198 i
Creation of a new hook to let LSM modules handle user-space pagefaults on
x86.
It can be used to avoid segfaulting the originating process.
If it's the case it can modify process registers before returning.
This is not a security feature by itself, it's a way to soften some
unwanted side-effects of
S.A.R.A. (S.A.R.A. is Another Recursive Acronym) is a stacked Linux
Security Module that aims to collect heterogeneous security measures,
providing a common interface to manage them.
It can be useful to allow minor security features to use advanced
management options, like user-space configuration
This allow threads to get current WX Protection flags for themselves or
for other threads (if they have CAP_MAC_ADMIN).
It also allow a thread to set itself flags to a stricter set of rules than
the current one.
Via a new wxprot flag (SARA_WXP_FORCE_WXORX) is it possible to ask the
kernel to rescan
Adds support for extended filesystem attributes in security and user
namespaces. They can be used to override flags set via the centralized
configuration, even when S.A.R.A. configuration is locked or saractl
is not used at all.
Signed-off-by: Salvatore Mesoraca
---
Documentation/admin-guide/LSM
On 11/21/2017 11:12 AM, Christian Borntraeger wrote:
>
>
> On 11/21/2017 07:09 PM, Jens Axboe wrote:
>> On 11/21/2017 10:27 AM, Jens Axboe wrote:
>>> On 11/21/2017 03:14 AM, Christian Borntraeger wrote:
Bisect points to
1b5a7455d345b223d3a4658a9e5fce985b7998c1 is the first bad comm
This allow S.A.R.A. to use the procattr interface without interfering
with other LSMs.
This part should be reimplemented as soon as upstream procattr stacking
support is available.
Signed-off-by: Salvatore Mesoraca
---
fs/proc/base.c | 38 ++
security/sec
Some programs need to generate part of their code at runtime. Luckily
enough, in some cases they only generate well-known code sequences (the
"trampolines") that can be easily recognized and emulated by the kernel.
This way WX Protection can still be active, so a potential attacker won't
be able to
Introduction of S.A.R.A. WX Protection.
It aims to improve user-space programs security by applying:
- W^X enforcement
- W!->X (once writable never executable) mprotect restriction
- Executable MMAP prevention
All of the above features can be enabled or disabled both system wide
or on a per execut
Creation of the S.A.R.A. cred blob management "API".
In order to allow S.A.R.A. to be stackable with other LSMs, it doesn't use
the "security" field of struct cred, instead it uses an ad hoc field named
security_sara.
This solution is probably not acceptable for upstream, so this part will
be modif
Creation of a new LSM hook to check if a given configuration of vmflags,
for a new memory allocation request, should be allowed or not.
It's placed in "do_mmap", "do_brk_flags", "__install_special_mapping"
and "setup_arg_pages".
When loading an ELF, this hook is also used to determine what to do
wi
Initial S.A.R.A. framework setup.
Creation of a simplified interface to securityfs API to store and retrieve
configurations and flags from user-space.
Creation of some generic functions and macros to handle concurrent access
to configurations, memory allocation and path resolution.
Signed-off-by:
On Tue, Nov 21, 2017 at 01:49:47AM +0200, Jarkko Sakkinen wrote:
> On Mon, Nov 20, 2017 at 04:17:28PM -0700, Jason Gunthorpe wrote:
> > On Mon, Nov 20, 2017 at 02:45:23PM -0800, Guenter Roeck wrote:
> >
> > > "tpm: Enable sysfs support for TPM2 devices
> > >
> > > Access to chip->ops on TPM2 devi
On Mon, Nov 20, 2017 at 05:53:32PM -0600, Eddie James wrote:
> From: "Edward A. James"
>
> Document the bindings for I2C-based OCC hwmon device.
>
> Signed-off-by: Edward A. James
> ---
> .../devicetree/bindings/i2c/ibm,p8-occ-hwmon.txt | 25
> ++
> 1 file changed, 25 in
On Sat, Nov 18, 2017 at 09:45:31PM +, Al Viro wrote:
> in __get_user_pages_locked(), or am I missing something subtle there? Andrea?
You're not missing anything as far as the logic is concerned.
However see the __always_inline, I added "notify_drop" purely to
optimize away such branch at bui
Hi!
On Tuesday 21 November 2017 15:52:28 Oleksandr Natalenko wrote:
> Hi, Pali et al.
>
> Answers go inline.
>
> On úterý 21. listopadu 2017 14:51:10 CET Pali Rohár wrote:
> > What would happen if you enable wmi_requires_smbios_request?
> > Nothing? And situation is exactly same?
>
> Yes, this
On Mon, Nov 20, 2017 at 05:53:33PM -0600, Eddie James wrote:
> From: "Edward A. James"
>
> Document the bindings for the FSI-based OCC hwmon device.
>
> Signed-off-by: Edward A. James
> ---
> .../devicetree/bindings/fsi/ibm,p9-occ-hwmon.txt | 16
>
> 1 file changed, 1
On 11/21/2017 11:27 AM, Jens Axboe wrote:
> On 11/21/2017 11:12 AM, Christian Borntraeger wrote:
>>
>>
>> On 11/21/2017 07:09 PM, Jens Axboe wrote:
>>> On 11/21/2017 10:27 AM, Jens Axboe wrote:
On 11/21/2017 03:14 AM, Christian Borntraeger wrote:
> Bisect points to
>
> 1b5a7455d345
On Tue, Nov 21, 2017 at 05:45:32PM +0100, Jiri Kosina wrote:
> On Tue, 21 Nov 2017, Jiri Kosina wrote:
>
> > > The existing driver erroneously treats I2C_BLOCK_DATA and BLOCK_DATA
> > > commands the same. Fix the logic for I2C_BLOCK_DATA reads and writes.
> >
> > Addin David, the original author
The existing driver erroneously treats I2C_BLOCK_DATA and BLOCK_DATA
commands the same.
For I2C_BLOCK_DATA reads, the length of the read is provided in
data->block[0], but the length itself should not be sent to the slave. In
contrast, for BLOCK_DATA reads no length is specified since the length
w
Hiya
http://bit.ly/2z5P5es
>> Add jump targets so that a bit of exception handling can be better reused
>> at the end of these functions.
>>
>> This issue was detected by using the Coccinelle software.
>
> Please include Coccinelle report in the change log.
I guess that I can not append the kind of report you might be look
On Tue, Nov 21, 2017 at 05:23:52PM +, David Laight wrote:
> From: Paul E. McKenney
> > Sent: 20 November 2017 20:54
> >
> > On Mon, Nov 20, 2017 at 08:32:56PM +0100, Peter Zijlstra wrote:
> > > On Mon, Nov 20, 2017 at 06:05:55PM +, Will Deacon wrote:
> > > > Although the current direction
Users can define optional "MAILER" "USR_EMAIL" variables to get email
notifications.
Ktest will send emails when the script:
* was started
* was cancelled by Ctrl-C
* failed with fatal errors and called dodie()
* completed all testing
Users have to setup the mailer provided in config prior t
Users should get emails when the script dies because of a critical failure.
Critical
failures are defined as any errors that could terminate the script, via die().
In order to add email support, this patch converts all die() to dodie() except:
* when '-v' is used as an option to get the version
This patch series will let users define mailer and email address for receiving
notifications during automated testings. Users need to setup the specified
mailer
prior to using this feature.
Emails will be sent when the script completes, is aborted due to errors or
interrupted
by Sig-Int.
Tim T
>> Add a jump target so that a bit of exception handling can be better reused
>> at the end of this function.
>>
>> This issue was detected by using the Coccinelle software.
>
> I would like to see the Coccinelle log included in the commit log
I guess that I can not append the kind of report you
On Tue, Nov 21, 2017 at 02:12:12PM +, Adam Thomson wrote:
> The expectation in the FUSB302 driver is that a TX_SUCCESS event
> should occur after a message has been sent, but before a GCRCSENT
> event is raised to indicate successful receipt of a message from
> the partner. However in some circ
On 11/20/2017 09:07 AM, Andy Lutomirski wrote:
> --- a/arch/x86/entry/entry_64.S
> +++ b/arch/x86/entry/entry_64.S
> @@ -560,6 +560,14 @@ END(irq_entries_start)
> .macro interrupt func
> cld
> ALLOC_PT_GPREGS_ON_STACK
> +
> + testb $3, CS(%rsp)
> + jz 1f
> + SWA
Hi.
On úterý 21. listopadu 2017 19:36:24 CET Pali Rohár wrote:
> Ok, if wmi_requires_smbios_request is really doing nothing, then it
> should not be used. It enables some QSET feature in Dell SMM mode which
> is for 2 laptops.
It is also used to filter 0xe025 key code which is generated by 3rd ke
On Tue, Nov 21, 2017 at 10:28:58AM -0800, Guenter Roeck wrote:
> I'll split the patch into two parts, and only add (hopefully)
> non-controversial tpm2 attributes for now (which I think is durations
> and timeouts). Or, in other words, I'll split the attributes into
> two groups - one generic and
Hey James,
On 21 November 2017 at 09:47, James Morse wrote:
> Hi Leo Yan,
>
> On 18/11/17 09:12, Leo Yan wrote:
>> commit a88ce63b642c ("arm64: kexec: have own crash_smp_send_stop() for
>> crash dump for nonpanic cores") introduces ARM64 architecture function
>
> (This commit fixed a bug where th
On Tue, 2017-11-21 at 18:09 +0100, Greg Kroah-Hartman wrote:
> On Tue, Nov 21, 2017 at 04:46:18PM +, Ben Hutchings wrote:
> > On Tue, 2017-11-21 at 17:35 +0100, Greg Kroah-Hartman wrote:
> > > On Tue, Nov 21, 2017 at 03:26:10PM +, Ben Hutchings wrote:
> >
> > [...]
> > > > Not all 32-bit c
Iterators aren't necessary as you can just grab the first entry and
delete it until no entries left.
Signed-off-by: Alexey Dobriyan
---
fs/proc/vmcore.c |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
--- a/fs/proc/vmcore.c
+++ b/fs/proc/vmcore.c
@@ -1178,18 +1178,16 @@ fs_initc
On 11/21/2017 07:39 PM, Jens Axboe wrote:
> On 11/21/2017 11:27 AM, Jens Axboe wrote:
>> On 11/21/2017 11:12 AM, Christian Borntraeger wrote:
>>>
>>>
>>> On 11/21/2017 07:09 PM, Jens Axboe wrote:
On 11/21/2017 10:27 AM, Jens Axboe wrote:
> On 11/21/2017 03:14 AM, Christian Borntraeger wr
On 2017-11-20 06:12, Gustavo A. R. Silva wrote:
_vreg_ is being dereferenced before it is null checked, hence there is
a
potential null pointer dereference.
Fix this by moving the pointer dereference after _vreg_ has been null
checked.
This issue was detected with the help of Coccinelle.
Fixe
Fixed some code style issues.
Signed-off-by: Guilherme Tadashi Maeoka
---
drivers/staging/comedi/drivers/adl_pci9118.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/comedi/drivers/adl_pci9118.c
b/drivers/staging/comedi/drivers/adl_pci9118.c
ind
On Tue, 21 Nov 2017 15:15:55 + Roman Gushchin wrote:
> > > +
> > > + for_each_hstate(h) {
> > > + unsigned long count = h->nr_huge_pages;
> > > +
> > > + total += (PAGE_SIZE << huge_page_order(h)) * count;
> > > +
> > > + if (h == &default_hstate)
> >
> > I'm not unde
On 2017-11-20 13:33, Jesse Chan wrote:
This change resolves a new compile-time warning
when built as a loadable module:
WARNING: modpost: missing MODULE_LICENSE() in
drivers/phy/qualcomm/phy-qcom-ufs.o
see include/linux/module.h for more information
This adds the license as "GPL v2", which matc
Hi Sean!
On Sun, Nov 19, 2017 at 09:57:27PM +, Sean Young wrote:
> I think for now the best solution is to revert to 250ms for all protocols
> (except for cec which needs 550ms), and reconsider for another kernel.
Thanks, this sounds like a good idea!
> >>From 2f1135f3f9873778ca5c013d1118710
>> Static source code analysis points out that the checking of return values
>> from
>> some function calls is incomplete also in this software area.
>> How would you like to fix remaining open issues there?
>>
>
> Without understanding the details on which failures,
Are you using any dedicated
On 11/21/2017 12:15 PM, Christian Borntraeger wrote:
>
>
> On 11/21/2017 07:39 PM, Jens Axboe wrote:
>> On 11/21/2017 11:27 AM, Jens Axboe wrote:
>>> On 11/21/2017 11:12 AM, Christian Borntraeger wrote:
On 11/21/2017 07:09 PM, Jens Axboe wrote:
> On 11/21/2017 10:27 AM, Jens Ax
On Tue, Nov 21, 2017 at 07:07:14PM +, Ben Hutchings wrote:
> On Tue, 2017-11-21 at 18:09 +0100, Greg Kroah-Hartman wrote:
> > On Tue, Nov 21, 2017 at 04:46:18PM +, Ben Hutchings wrote:
> > > On Tue, 2017-11-21 at 17:35 +0100, Greg Kroah-Hartman wrote:
> > > > On Tue, Nov 21, 2017 at 03:26:1
From: Haiyang Zhang
On Hyper-V the VF NIC has the same MAC as the related synthetic NIC.
VF NIC can work under the synthetic NIC transparently, without its
own IP address. The existing KVP daemon only gets IP from the first
NIC matching a MAC address, and may not be able to find the IP in
this ca
On Tue, Nov 21 2017, Mike Snitzer wrote:
> On Mon, Nov 20 2017 at 8:35pm -0500,
> Mike Snitzer wrote:
>
>> On Mon, Nov 20 2017 at 7:34pm -0500,
>> NeilBrown wrote:
>>
>> > On Mon, Nov 20 2017, Mike Snitzer wrote:
>> >
>> > >
>> > > But I've now queued this patch for once Linus gets back (rev
Hi Linus,
Here are a couple more patches to fix a memory leak and some refactoring
to make it easier to keep xfsprogs' libxfs in sync with the kernel.
--D
The following changes since commit 2015a63dce8d73a439232a0d5162c88d8513101e:
xfs: fix type usage (2017-11-16 12:06:45 -0800)
are availabl
On Montag, 20. November 2017 20:56:47 CET Bjorn Andersson wrote:
> Not all instances of the SDCC core supports changing signal voltage and
> as such will not generate a power interrupt when the software attempts
> to change the voltage. This results in probing the eMMC on some devices
> to take ove
On 11/20/2017 11:19 AM, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 20 Nov 2017 19:10:14 +0100
>
> The same assignments were used in an if branch of two separate statements.
>
> * Merge their condition checks into a single statement instead.
>
> * Adjust the indentation there.
On Tue, Nov 21 2017 at 7:43am -0500,
Mike Snitzer wrote:
> Decided it a better use of my time to review and then hopefully use the
> block-core's bio splitting infrastructure in DM. Been meaning to do
> that for quite a while anyway. This mail from you just made it all the
> more clear that n
On Tue, Nov 21, 2017 at 1:10 AM, Knut Omang wrote:
> Would you like to keep the checkpatch changes in some form, or would you
> rather
> see everything happening in the wrapper?
I don't have a strong preference one way or another, but keeping
everything in a wrapper script might be easier if on
On Tue, Nov 21 2017 at 2:44pm -0500,
NeilBrown wrote:
> On Tue, Nov 21 2017, Mike Snitzer wrote:
>
> > On Mon, Nov 20 2017 at 8:35pm -0500,
> > Mike Snitzer wrote:
> >
> >> On Mon, Nov 20 2017 at 7:34pm -0500,
> >> NeilBrown wrote:
> >>
> >> > On Mon, Nov 20 2017, Mike Snitzer wrote:
> >>
Error code returned by 'bnxt_read_sfp_module_eeprom_info()' is handled a
few lines above when reading the A0 portion of the EEPROM.
The same should be done when reading the A2 portion of the EEPROM.
In order to correctly propagate an error, update 'rc' in this 2nd call as
well, otherwise 0 (succes
On Tue, 21 Nov 2017, Mike Galbraith wrote:
> On Tue, 2017-11-21 at 11:11 -0500, Mikulas Patocka wrote:
> >
> > So, drop the spinlock unplugging and leave only mutex unplugging,
> > reproduce the deadlock and send the stacktraces.
>
> Nah, I reproduced it five years ago. Is any of that releva
On Wed, 2017-09-13 at 17:19 +0200, Michal Hocko wrote:
> On Wed 13-09-17 15:07:26, Jorgen S. Hansen wrote:
[...]
> > The patch below has been used to fix the above issue by other distros
> > - among them Redhat for the 3.10 kernel, so it should work for 3.16 as
> > well.
>
> Thanks for the confirm
301 - 400 of 995 matches
Mail list logo
