From: Andi Kleen
Implement a weak group fallback for perf record, similar to the existing perf
stat support.
This allows to use groups that might be longer than the available counters
without
failing.
Before:
$ perf record -e
'{cycles,cache-misses,cache-references,cpu_clk_unhalted.thread,cy
On Mon, 24 Sep 2018, Kees Cook wrote:
> In preparation for doing more interesting LSM init probing, this converts
> the existing initcall system into an explicit call into a function pointer
> from a section-collected struct lsm_info array.
>
> Cc: James Morris
> Cc: "Serge E. Hallyn"
> Cc: Ard
From: Andi Kleen
- Move the function from builtin-stat to evlist for reuse
- Rename to evlist to match purpose better
- Pass the evlist as first argument.
- No functional changes
Signed-off-by: Andi Kleen
---
tools/perf/builtin-stat.c | 29 ++---
tools/perf/util/evlist.
On Sep 29, 2018, at 2:40 AM, Pali Rohár wrote:
>
> Hi!
>
> Last year I did some research how Windows and Linux tools handle FAT
> labels (boot sector vs root directory) and proposed some unification.
> More in thread: https://www.spinics.net/lists/kernel/msg2640891.html
>
> My proposed change f
On Mon, Oct 01, 2018 at 06:17:00PM +0100, Will Deacon wrote:
> Hi Peter,
>
> Thanks for chewing up my afternoon ;)
I'll get you a beer in EDI ;-)
> On Wed, Sep 26, 2018 at 01:01:20PM +0200, Peter Zijlstra wrote:
> > /**
> > + * set_pending_fetch_acquire - fetch the whole lock value and set pen
On Mon, 1 Oct 2018, Darrick J. Wong wrote:
> If we /did/ replace CAP_SYS_ADMIN checking with a pile of LSM hooks,
Not sure we'd need a pile of hooks, what about just "read" and "write"
storage admin?
Or even two new capabilities along these lines, which we convert existing
CAP_SYS_ADMIN etc. t
On Mon 2018-10-01 15:23:24, Steven Rostedt wrote:
> On Thu, 27 Sep 2018 12:46:01 -0700
> Daniel Wang wrote:
>
> > Prior to this change, the combination of `softlockup_panic=1` and
> > `softlockup_all_cpu_stacktrace=1` may result in a deadlock when the reboot
> > path
> > is trying to grab the co
Hi all,
this series sorts out how we deal with the nowarn flags in the dma
mapping code. We still support __GFP_NOWARN for the legacy APIs that
don't support passing the dma specific flags, but we generally want
every implementation to actually check DMA_ATTR_NO_WARN instead.
On Mon, Oct 1, 2018 at 10:01 PM Andreas Dilger wrote:
> If the current dosfstools maintainer is non-responsive, you could always
> fork the project in GitHub, land the critical patches into your branch,
> and make a release on your own. If the maintainer surfaces again, then
> they can pull in y
On Monday 01 October 2018 14:00:28 Andreas Dilger wrote:
> If not, then you are the new maintainer.
Hi! I really do not want to have another project.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: PGP signature
On Mon, 1 Oct 2018, Mickaël Salaün wrote:
> Another way to apply a security policy could be to tied it to a file
> descriptor, similarly to Capsicum, which could enable to create
> programmable (real) capabilities. This way, it would be possible to
> "wrap" a file descriptor with a Landlock progra
On Mon, Oct 1, 2018 at 8:53 PM Leonard Crestez wrote:
> This patch seems to break network booting on imx6sx-sdb in linux-next
> because the enet phy regulator is not on. Reverting the patch fixes
> boot.
Thanks for reporting.
John Stultz reported the same problem I'm trying to debug it.
> Here
RK3399 has one cluster with 4 small cores, and another one with 2 big
cores, with cores in different clusters having different OPPs and thus
different policies. Let's enable this via "have_governor_per_policy"
platform data.
Signed-off-by: Dmitry Torokhov
---
Not tested, but we had a patch uncon
On 10/1/18 10:13 PM, Pavel Machek wrote:
>
> Dunno. Is the patch perhaps a bit too complex? This is not exactly
> trivial bugfix.
>
> pavel@duo:/data/l/clean-cg$ git show dbdda842fe96f | diffstat
> printk.c | 108
> ++-
>
> I see that
On Thu, Sep 27, 2018 at 2:49 PM, Zubin Mithra wrote:
> Syzkaller reported a OOB-read with the stacktrace below. This occurs
> inside __aa_lookupn_ns as `n` is not initialized. `n` is obtained from
> aa_splitn_fqname. In cases where `name` is invalid, aa_splitn_fqname
> returns without initializing
On Sun, Sep 30, 2018 at 06:49:50PM +0200, Ard Biesheuvel wrote:
> Commit e872267b8bcbb179 ("jump_table: move entries into ro_after_init
> region") moved the __jump_table input section into the __ro_after_init
> output section, but inadvertently put the macro in the wrong place in
> the s390 linker
On Monday 09 April 2018 12:35:54 Pali Rohár wrote:
> On Monday 09 April 2018 03:24:14 Christoph Hellwig wrote:
> > On Mon, Apr 09, 2018 at 12:10:09PM +0200, Pali Rohár wrote:
> > > Another example:
> > >
> > > fd = open("/a")
> > > link("/a", "/b")
> > > unlink("/a")
> > >
> > > Calling funlink f
In multi-master environment, this driver's master cannot know
exactly when peer master sends data to this driver's slave so a
case can be happened that this master tries to send data through
the master_xfer function but slave data from peer master is still
being processed by this driver.
To preven
This commit adds reading code of the 'timeout' DT property to set
bus timeout value in adapter configuration. This value still
can be configured through an I2C_TIMEOUT ioctl on cdev too.
Signed-off-by: Jae Hyun Yoo
---
drivers/i2c/busses/i2c-aspeed.c | 8 +++-
1 file changed, 7 insertions(+)
This commit adds 'timeout' property as an optional property which
can be used for setting 'timeout' value of 'struct i2c_adapter'.
With this patch, the bus timeout value can be set through this
DT property from the probing time of the module. Still the bus
timeout value can be set by an I2C_TIMEOUT
In multi-master environment, this driver's master cannot know
exactly when peer master sends data to this driver's slave so a
case can be happened that this master tries to send data through
the master_xfer function but slave data from peer master is still
being processed by this driver.
To preven
On Mon, Oct 01, 2018 at 10:18:10PM +0800, Feng Tang wrote:
> As I rechecked, the baud rate for pciserial is optional, so there may
> be no ",baudrate" following the "force". So this 2 strncmp is to
> cover conditions for with and without baudrate.
And what guarantees you have a space after the "fo
On Mon, 1 Oct 2018 22:13:10 +0200
Pavel Machek wrote:
> > > [1]
> > > https://lore.kernel.org/lkml/20180409081535.dq7p5bfnpvd3x...@pathway.suse.cz/T/#u
> > >
> > > Serial console logs leading up to the deadlock. As can be seen the stack
> > > trace
> > > was incomplete because the printing pat
Hi Linus,
On Mon, Oct 1, 2018 at 5:17 PM Linus Walleij wrote:
> > reg_enet_3v3: regulator-enet-3v3 {
> > compatible = "regulator-fixed";
> > pinctrl-names = "default";
> > pinctrl-0 = <&pinctrl_enet_3v3>;
> > regulator-name = "enet_3v3";
> > regulator-min-
On Mon, Oct 1, 2018 at 12:23 PM Steven Rostedt wrote:
>
> > Serial console logs leading up to the deadlock. As can be seen the stack
> > trace
> > was incomplete because the printing path hit a timeout.
>
> I'm fine with having this backported.
Thanks. I can send the cherrypicks your way. Do you
On Mon, Oct 1, 2018 at 1:23 PM Vlastimil Babka wrote:
>
> On 10/1/18 10:13 PM, Pavel Machek wrote:
> >
> > Dunno. Is the patch perhaps a bit too complex? This is not exactly
> > trivial bugfix.
> >
> > pavel@duo:/data/l/clean-cg$ git show dbdda842fe96f | diffstat
> > printk.c | 108
> >
On Mon, Oct 01, 2018 at 01:37:30PM -0700, Daniel Wang wrote:
>On Mon, Oct 1, 2018 at 12:23 PM Steven Rostedt wrote:
>>
>> > Serial console logs leading up to the deadlock. As can be seen the stack
>> > trace
>> > was incomplete because the printing path hit a timeout.
>>
>> I'm fine with having t
commit efdfeb079cc3
("regulator: fixed: Convert to use GPIO descriptor only")
switched to use gpiod_get() to look up the regulator from the
gpiolib core whether that is device tree or boardfile.
This meant that we activate the code in
a603a2b8d86e ("gpio: of: Add special quirk to parse regulator f
Hi Peter,
thanks for the review.
On 01/10/2018 13:49, Peter Rosin wrote:
> On 2018-09-26 10:35, Luca Ceresoli wrote:
>> From: Luca Ceresoli
>>
>> struct i2c_client has a direct pointer to the adapter, no need to dig
>> it out of the struct device tree.
>
> Right, looks sane, but can you please
On 10/01/2018 11:49 AM, John Stultz wrote:
On Mon, Oct 1, 2018 at 10:58 AM, Mark Salyzyn wrote:
Last sent 23 Nov 2016.
The following 23 patches are rebased and resent, and represent a
rewrite of the arm and arm64 vDSO into C, adding support for arch32
(32-bit user space hosted 64-bit kernels)
On Mon, Oct 1, 2018 at 10:36 PM Fabio Estevam wrote:
> On Mon, Oct 1, 2018 at 5:17 PM Linus Walleij wrote:
>
> > > reg_enet_3v3: regulator-enet-3v3 {
> > > compatible = "regulator-fixed";
> > > pinctrl-names = "default";
> > > pinctrl-0 = <&pinctrl_enet_3v3>;
> > >
On Mon, Oct 01, 2018 at 11:15:32AM +0200, Eric W. Biederman wrote:
>
> In the context of process migration there is a simpler subproblem that I
> think it is worth exploring if we can do something about.
>
> For a cluster of machines all running with synchronized
> clocks. CLOCK_REALTIME matches.
Hello,
On 01.10.2018 19:11, Thomas Gleixner wrote:
> Peter and I discussed that and we came up with the idea that the file
> descriptor is not even required, i.e. you could make it backward
> compatible.
>
> perf_event_open() knows which PMU is associated with the event the caller
> tries to
On 10/01/2018 11:15 AM, Thomas Gleixner wrote:
On Mon, 1 Oct 2018, Mark Salyzyn wrote:
+static notrace int do_boottime(const struct vdso_data *vd, struct timespec *ts)
+{
+ u32 seq, mult, shift;
+ u64 nsec, cycle_last;
+ vdso_wtm_clock_nsec_t wtm_nsec;
+
+ /* open codi
On 09/26/2018 07:34 AM, Jordan Crouse wrote:
On Tue, Sep 25, 2018 at 01:02:15PM -0500, Rob Herring wrote:
On Fri, Aug 31, 2018 at 05:01:45PM +0300, Georgi Djakov wrote:
This binding is intended to represent the relations between the interconnect
controllers (providers) and consumer device no
On Mon, Oct 01, 2018 at 02:51:48PM +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Mon, 01 Oct 2018 12:56:37 +0200, Jan Kundrát wrote:
>
> > Thomas, Russell, Lorenzo,
> > did you have time to convert this into a patch which can hit 4.19? I don't
> > see anything related in 4.19-rc6, but perhaps I
Hi Trilok,
On 09/11/2018 01:17 PM, Trilok Soni wrote:
> Bjorn,
>
>> #define MSG "hello world!"
>> -#define MSG_LIMIT 100
>> +
>> +static int count = 100;
>> +module_param(count, int, 0644);
>
> I thought Greg KH doesn't want any new code to have module_param call,
> right? Are we O
Hi Bjorn,
On 09/14/2018 07:37 PM, Suman Anna wrote:
> Hi Bjorn,
>
> The following series includes couple of fixes and improvements
> associated with the sysfs interfaces. Patches are based on top
> of 4.19-rc1. The first 3 patches are independent of each other.
>
> Following is the patch summary
On Mon, Oct 1, 2018 at 3:36 PM Ricardo Ribalda Delgado
wrote:
> On Mon, Oct 1, 2018 at 1:54 PM Linus Walleij wrote:
> > On Fri, Sep 28, 2018 at 9:30 PM Ricardo Ribalda Delgado
> > wrote:
> >
> > > How do we proceed from here? Can you fix your driver somehow to
> > > init the valid mask before en
On 25/09/2018 23:16, Alexandre Belloni wrote:
> On 24/09/2018 03:59:55+0200, Daniel Lezcano wrote:
>> On 13/09/2018 13:30, Alexandre Belloni wrote:
>>> Add a driver for the Atmel Timer Counter Blocks. This driver provides a
>>> clocksource and two clockevent devices.
>>>
>>> One of the clockevent d
On Mon, Oct 01, 2018 at 01:56:32PM -0700, Saravana Kannan wrote:
>
>
> On 09/26/2018 07:34 AM, Jordan Crouse wrote:
> >On Tue, Sep 25, 2018 at 01:02:15PM -0500, Rob Herring wrote:
> >>On Fri, Aug 31, 2018 at 05:01:45PM +0300, Georgi Djakov wrote:
> >>>This binding is intended to represent the rel
On Mon, Oct 1, 2018 at 1:44 PM, Mark Salyzyn wrote:
> On 10/01/2018 11:49 AM, John Stultz wrote:
>> It seems the patchset is already somewhat broken up into separate
>> sets, so I might recommend picking just one area and focus on
>> upstreaming that first. Maybe the in-arch cleanups for arm and t
This is V7 of the "KASLR feature to randomize each loadable module" patchset.
The purpose is to increase the randomization and also to make the modules
randomized in relation to each other instead of just the base, so that if one
module leaks the location of the others can't be inferred.
This new
This adds a test module in lib/, and a script in kselftest that does
benchmarking on the allocation of memory in the module space. Performance here
would have some small impact on kernel module insertions, BPF JIT insertions
and kprobes. In the case of KASLR features for the module space, this modu
Create __vmalloc_node_try_addr function that tries to allocate at a specific
address and supports caller specified behavior for whether any lazy purging
happens if there is a collision.
This new function draws from the __vmalloc_node_range implementation. Attempts
to merge the two into a single al
Add debugfs file "modfraginfo" for providing info on module space fragmentation.
This can be used for determining if loadable module randomization is causing any
problems for extreme module loading situations, like huge numbers of modules or
extremely large modules.
Sample output when KASLR is ena
This adds dedicated "Whiskers" driver that hooks both into HID and EC to
produce proper SW_TABLET_SWITCH event from base presence bit from EC and
base state (folded/unfolded) coming from USB/HID.
Signed-off-by: Nicolas Boichat
Signed-off-by: Dmitry Torokhov
---
drivers/hid/Kconfig
This adds a "base attached" switch definition to the MKBP protocol that
is used by Whiskers driver to properly determine device state (clamshell
vs tablet mode).
Signed-off-by: Dmitry Torokhov
---
Lee, I was wondering if it woudl be OK for cros_ec_commands.h to be
merged through HID tree.
inc
This changes the behavior of the KASLR logic for allocating memory for the text
sections of loadable modules. It randomizes the location of each module text
section with about 17 bits of entropy in typical use. This is enabled on X86_64
only. For 32 bit, the behavior is unchanged.
It refactors exi
In preparation to remove the node name pointer from struct device_node,
convert printf users to use the %pOFn format specifier.
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Jaroslav Kysela
Cc: Takashi Iwai
Cc: Olivier Moysan
Cc: Arnaud Pouliquen
Cc: Maxime Coquelin
Cc: Alexandre Torgue
Cc: alsa-de
In preparation to remove the node name pointer from struct device_node,
convert printf users to use the %pOFn format specifier.
Cc: Greg Kroah-Hartman
Signed-off-by: Rob Herring
---
drivers/uio/uio_dmem_genirq.c | 3 ++-
drivers/uio/uio_pdrv_genirq.c | 3 ++-
2 files changed, 4 insertions(+), 2
On 10/1/2018 2:14 PM, Dan Williams wrote:
Use kvzalloc() to bypass the arbitrary PAGE_SIZE limit of label transfer
operations. Given the expense of calling into firmware, maximize the
amount of label data we transfer per call to be up to the total label
space if allowed by the firmware, or 256
In preparation to remove the node name pointer from struct device_node,
convert printf users to use the %pOFn format specifier.
Cc: Dmitry Torokhov
Cc: Michal Simek
Cc: linux-in...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Rob Herring
---
drivers/input/serio/xilin
In preparation to remove the node name pointer from struct device_node,
convert printf users to use the %pOFn format specifier.
Cc: Sebastian Reichel
Cc: linux...@vger.kernel.org
Signed-off-by: Rob Herring
---
drivers/power/reset/axxia-reset.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
On 2018-09-27 06:56, Jarkko Sakkinen wrote:
On Wed, Sep 26, 2018 at 02:45:17PM -0700, Dave Hansen wrote:
On 09/26/2018 02:15 PM, Andy Lutomirski wrote:
Could we perhaps have a little vDSO entry (or syscall, I suppose) that
runs an enclave an returns an error code, and rig up the #PF handler
to
This code needs to select function #0, which is the first int in the
array of functions, not the number 0 which may or may not be the
function for "GPIO mode" per the enum mapping. We were getting lucky on
SDM845, where this was tested, because the function 0 matched the enum
value for "GPIO mode".
On 10/01/2018 02:26 PM, Jordan Crouse wrote:
On Mon, Oct 01, 2018 at 01:56:32PM -0700, Saravana Kannan wrote:
On 09/26/2018 07:34 AM, Jordan Crouse wrote:
On Tue, Sep 25, 2018 at 01:02:15PM -0500, Rob Herring wrote:
On Fri, Aug 31, 2018 at 05:01:45PM +0300, Georgi Djakov wrote:
This bindi
Call the 64bit versions of rtc_time_to_tm now that the range is enforced by
the core.
Also remove the open coded rtc_tm_to_time64.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-vr41xx.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/rtc/rtc-vr41xx.c b
On Mon, Oct 1, 2018 at 1:43 PM, Linus Walleij wrote:
> commit efdfeb079cc3
> ("regulator: fixed: Convert to use GPIO descriptor only")
> switched to use gpiod_get() to look up the regulator from the
> gpiolib core whether that is device tree or boardfile.
>
> This meant that we activate the code i
Hi.
2018年9月27日(木) 2:57 Nadav Amit :
>
> at 1:58 AM, Rasmus Villemoes wrote:
>
> > On 2018-09-18 23:28, Nadav Amit wrote:
> >
> >> diff --git a/arch/x86/Makefile b/arch/x86/Makefile
> >> index 8f6e7eb8ae9f..944fa3bc9376 100644
> >> --- a/arch/x86/Makefile
> >> +++ b/arch/x86/Makefile
> >> @@ -21
On 10/01/2018 02:42 PM, Jethro Beekman wrote:
>
> 1) Even though the vDSO function exists, userspace may still call
> `ENCLU[EENTER]` manually, so the fault handling as described in the
> current patch should also be maintained.
Why?
Instead of lying to the core when the alarm is invalid, let it handle that
by returning the error.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-mv.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/rtc/rtc-mv.c b/drivers/rtc/rtc-mv.c
index 4b198b3778d3.
Quoting ryang (2018-09-21 15:00:37)
> Calling clk_set_rate or clk_round_rate will lock up the kernel when the
> rate is zero. This avoids the infinite loop and uses a slightly more
> optimized p divider calculation.
>
> Signed-off-by: ryang
Do you have a more proper name? Or you want the author
Quoting Gregory CLEMENT (2018-09-12 06:40:17)
> Convert the remaining files to SPDX license description.
>
> Signed-off-by: Gregory CLEMENT
> ---
Applied to clk-next
Quoting Gregory CLEMENT (2018-09-12 08:35:49)
> While applying the commit a8309cedcdce ("clk: apn806: Add eMMC clock to
> system controller driver"), of_clk_add_provider was added wheres it was
> already present in the probe function.
>
> This extraneous call is harmless but not useful so remove i
Quoting Edgar Bernardi Righi (2018-09-04 08:39:48)
> Basic clock support for S500 SoC was implemented using the Actions
> Semi Owl clock driver.
> This patch also adds custom delay support to Actions Semi OWL pll clock
> driver.
> The default delay (50us) is not enough for Actions Semi Owl S500 So
2018年10月2日(火) 4:58 Nick Desaulniers :
>
> On Mon, Oct 1, 2018 at 12:02 PM Masahiro Yamada
> wrote:
> >
> > Hi Nick,
> >
> > 2018年10月2日(火) 2:18 Nick Desaulniers :
> > >
> > > On Mon, Oct 1, 2018 at 2:45 AM Masahiro Yamada
> > > wrote:
> > > >
> > > > We have raised the compiler requirement from ti
Hi Christoph,
After merging the dma-mapping tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
drivers/base/platform.c:1182:12: warning: 'dma_default_get_required_mask'
defined but not used [-Wunused-function]
static u64 dma_default_get_required_mask(struct device *
On Mon, Oct 1, 2018 at 3:24 PM Masahiro Yamada
wrote:
>
> 2018年10月2日(火) 4:58 Nick Desaulniers :
> >
> > On Mon, Oct 1, 2018 at 12:02 PM Masahiro Yamada
> > wrote:
> > >
> > > Hi Nick,
> > >
> > > 2018年10月2日(火) 2:18 Nick Desaulniers :
> > > >
> > > > On Mon, Oct 1, 2018 at 2:45 AM Masahiro Yamada
On 10/1/18 11:32 AM, Florian Fainelli wrote:
> Hi Jens,
>
> This is a resend of the previous series posted here:
>
> https://lkml.org/lkml/2018/9/20/1060
>
> With a few minor changes:
>
> - rebased against your for-4.20/libata branch
> - added Rob's Reviewed-by to patch
> - fixed the use of the
Nobody(*) uses them. Dropping this will allow us to make the total
number of memory controllers configurable (as we won't have to
worry about duplicated device names under this directory).
(*) https://marc.info/?l=linux-edac&m=153809709903987&w=2
Signed-off-by: Tony Luck
---
Boris: Apply this,
On Tue, Oct 02, 2018 at 06:08:16AM +1000, James Morris wrote:
> On Mon, 1 Oct 2018, Darrick J. Wong wrote:
>
> > If we /did/ replace CAP_SYS_ADMIN checking with a pile of LSM hooks,
>
> Not sure we'd need a pile of hooks, what about just "read" and "write"
> storage admin?
>
> Or even two new c
On Sun, Sep 30, 2018 at 1:51 PM Nathan Chancellor
wrote:
>
> Clang warns that the __weak attribute is going to be ignored on
> g_attr_inode_data because it's not in the correct location (needs to be
> after the type).
>
> In file included from fs/exofs/dir.c:35:
> In file included from fs/exofs/ex
On Mon, Oct 01, 2018 at 11:25:29AM -0400, Theodore Y. Ts'o wrote:
> On Mon, Oct 01, 2018 at 04:04:42PM +0100, Alan Cox wrote:
> > > Systems restricted by LSMs to the point where CAP_SYS_ADMIN is not
> > > trusted have exactly the same issues. i.e. there's nobody trusted by
> > > the kernel to admin
Hi arm-soc maintainers,
Please merge the updated fix for the following issue.
Regards,
Leo
The following changes since commit 96fc74333f84cfdf8d434c6c07254e215e2aad00:
soc: fsl: qe: Fix copy/paste bug in ucc_get_tdm_sync_shift() (2018-09-25
13:57:26 -0700)
are available in the Git repositor
On Thu, Sep 27, 2018 at 11:41:49PM +0200, Thomas Gleixner wrote:
> On Thu, 27 Sep 2018, Thomas Gleixner wrote:
> > Add time skew via NTP/PTP into the picture and you might have to adjust
> > timers as well, because you need to guarantee that they are not expiring
> > early.
> >
> > I haven't looke
> On Sep 27, 2018, at 9:53 PM, Song Liu wrote:
>
> Hi Ravi,
>
>> On Sep 27, 2018, at 9:33 PM, Ravi Bangoria
>> wrote:
>>
>> Hi Song,
>>
>> On 09/25/2018 03:55 AM, Song Liu wrote:
>>> This patch tries to enable PMU sharing. To make perf event scheduling
>>> fast, we use special data struct
On Mon, Oct 01, 2018 at 04:43:49PM -0500, Rob Herring wrote:
> In preparation to remove the node name pointer from struct device_node,
> convert printf users to use the %pOFn format specifier.
>
> Cc: Dmitry Torokhov
> Cc: Michal Simek
> Cc: linux-in...@vger.kernel.org
> Cc: linux-arm-ker...@lis
On Mon, Oct 01, 2018 at 11:22:46AM +1000, Stephen Rothwell wrote:
>Hi Sasha,
>
>On Mon, 1 Oct 2018 00:38:27 + Sasha Levin
>wrote:
>>
>> From: Stephen Rothwell
>>
>> [ Upstream commit bcfb84a996f6fa90b5e6e2954b2accb7a4711097 ]
>>
>> A powerpc build of cifs with gcc v8.2.0 produces this warnin
On 09/26/2018 07:48 AM, Sudeep Holla wrote:
On Wed, Sep 26, 2018 at 05:42:15PM +0300, Georgi Djakov wrote:
Hi Rob,
Thanks for the comments!
On 09/25/2018 09:02 PM, Rob Herring wrote:
On Fri, Aug 31, 2018 at 05:01:45PM +0300, Georgi Djakov wrote:
This binding is intended to represent the rela
On Mon, Oct 01, 2018 at 07:29:03AM -0700, Sean Christopherson wrote:
> On Wed, 2018-09-26 at 14:15 -0700, Andy Lutomirski wrote:
> > runs an enclave an returns an error code, and rig up the #PF handler
> > to check if the error happened in the vDSO entry and fix it up rather
> > than sending a sign
Hi Bjorn,
After merging the pci tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warning:
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c: In function
'ixgbe_io_slot_reset':
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:11102:6: warning: unused variable
'err' [-Wunused-vari
On Mon, Oct 01, 2018 at 09:42:48PM +, Jethro Beekman wrote:
> 1) Even though the vDSO function exists, userspace may still call
> `ENCLU[EENTER]` manually, so the fault handling as described in the current
> patch should also be maintained.
You mean the way it was is in v13 and not the way it
Looks good. Just some minor bits.
On Sat, Sep 29, 2018 at 01:30:15AM +0300, Tomas Winkler wrote:
> 1. TPM2_CC_LAST has moved from 182 to 193
> 2. Convert tpm2_ordinal_duration from an array into a switch statement,
>as there are not so many commands that require special duration
>relative
On Sat, Sep 29, 2018 at 01:30:15AM +0300, Tomas Winkler wrote:
> 1. TPM2_CC_LAST has moved from 182 to 193
> 2. Convert tpm2_ordinal_duration from an array into a switch statement,
>as there are not so many commands that require special duration
>relative to a number of commands, the switch
On Sat, Sep 29, 2018 at 01:30:20AM +0300, Tomas Winkler wrote:
> Move tpm1_pcr_extend to tpm1-cmd.c and remove
> unused pcrextend_header structure and
> EXTEND_PCR_RESULT_SIZE and EXTEND_PCR_RESULT_BODY_SIZE
> defines.
>
> Fixes warning:
> drivers/char/tpm/tpm-interface.c:609:38: warning: ‘pcrexte
On Sat, Sep 29, 2018 at 01:30:22AM +0300, Tomas Winkler wrote:
> Factor out get random implementation from tpm-interface.c
> into tpm1_get_random function in tpm1-cmd.c.
> No functional changes.
>
> Signed-off-by: Tomas Winkler
> Reviewed-by: Jarkko Sakkine
Reviewed-by: Jarkko Sakkinen
Tested-
On Sat, Sep 29, 2018 at 01:30:14AM +0300, Tomas Winkler wrote:
> This patch series provides initial separation of tpm 1.x and tpm 2.x
> commands, in foresight that the tpm 1.x chips will eventually phase out
> and can be compiled out for modern systems.
> A new file is added tpm1-cmd.c that contai
On Sat, Sep 29, 2018 at 01:30:25AM +0300, Tomas Winkler wrote:
> TPM manual startup is used only from within TPM 1.x or TPM 2.x
> code, hence remove tpm_startup() function from tpm-interface.c
> and add two static functions implementations tpm1_startup()
> and tpm2_startup() into to tpm1-cmd.c and
On Sat, Sep 29, 2018 at 01:30:24AM +0300, Tomas Winkler wrote:
> Factor out TPM 1.x suspend flow from tpm-interface.c into a new function
> tpm1_pm_suspend() in tpm1-cmd.c
>
> Signed-off-by: Tomas Winkler
Reviewed-by: Jarkko Sakkinen
Tested-by: Jarkko Sakkinen
/Jarkko
On Sat, Sep 29, 2018 at 01:30:26AM +0300, Tomas Winkler wrote:
> Add tpm2_pcr_extend() function to tpm2-cmd.c with signature required
> by tpm-interface.c. It wraps the original open code
> implementation. The original original tpm2_pcr_extend() function
> is renamed to __tpm2_pcr_extend() and made
On Sat, Sep 29, 2018 at 01:30:27AM +0300, Tomas Winkler wrote:
> Add wrapper tpm_auto_startup() to tpm-interface.c
> instead of open coded decision between TPM 1.x and TPM 2.x
> in tpm-chip.c
>
> Signed-off-by: Tomas Winkler
> Tested-by: Jarkko Sakkinen
Reviewed-by: Jarkko Sakkinen
/Jarkko
v4:
- add Reviewed-bys.
- cosmetic tweaks.
- New patches to fully centralize LSM "enable" decisions:
LSM: Finalize centralized LSM enabling logic
apparmor: Remove boot parameter
selinux: Remove boot parameter
v3:
- add CONFIG_LSM_ENABLE and refactor resulting logic
v2:
- add "lsm.orde
LoadPin's "enable" setting is really about enforcement, not whether
or not the LSM is using LSM hooks. Instead, split this out so that LSM
enabling can be logically distinct from whether enforcement is happening
(for example, the pinning happens when the LSM is enabled, but the pin
is only checked
In preparation for doing more interesting LSM init probing, this converts
the existing initcall system into an explicit call into a function pointer
from a section-collected struct lsm_info array.
Signed-off-by: Kees Cook
Reviewed-by: Casey Schaufler
Reviewed-by: James Morris
Reviewed-by: John
On Sat, Sep 29, 2018 at 01:30:35AM +0300, Tomas Winkler wrote:
> The TPM specs defines PCR index as a positive number, and there is
> no reason to use a signed number. It is also a possible security
> issue as currently no functions check for a negative index,
> which may become a large number when
By default, no messages are printed when mounting a CIFS filesystem.
This information is valuable when troubleshooting and/or forensic
analyzing a system and finding out if was a CIFS endpoint mount
attempted.
Other filesystems such as XFS, EXT* does issue a printk() when mounting
their filesystems
Hi,
This mini patch series fixes issues introduced recently for non-ACPI
platforms using `rtc-cmos'. Please see individual change descriptions for
details.
These have been run-time verified with the DECstation (arch/mips/dec).
Please apply.
Maciej
Fix a commit 311ee9c151ad ("rtc: cmos: allow using ACPI for RTC alarm
instead of HPET") `rtc-cmos' regression causing a link error:
drivers/rtc/rtc-cmos.o: In function `cmos_platform_probe':
rtc-cmos.c:(.init.text+0x33c): undefined reference to `hpet_rtc_interrupt'
rtc-cmos.c:(.init.text+0x3f4):
Fix a problem with commit 311ee9c151ad ("rtc: cmos: allow using ACPI for
RTC alarm instead of HPET") defining `use_acpi_alarm' module parameter
even for non-ACPI platforms, which ignore it. Wrap the definition into
#ifdef CONFIG_ACPI and use a static inline wrapper function, hardcoded
to retur
401 - 500 of 580 matches
Mail list logo
