On 5/28/2019 10:05 AM, Peter Zijlstra wrote:
On Tue, May 28, 2019 at 09:33:40AM -0400, Liang, Kan wrote:
Uncore PMU doesn't support sampling. It will return -EINVAL.
There is no regs support for counting. The request will be ignored.
I think current check for uncore is good enough.
breakpo
Use the available IRQ helper functions, most of the functions have
additional helpful side affects like configuring the trigger type of the
IRQ.
Signed-off-by: Charles Keepax
---
Changes since v2:
- Don't consider zero to be a valid IRQ number
Thanks,
Charles
drivers/i2c/i2c-core-acpi.c | 24
Only set init_irq during i2c_device_new and only handle client->irq on
the probe/remove paths.
Suggested-by: Benjamin Tissoires
Signed-off-by: Charles Keepax
---
No changes since v2.
Thanks,
Charles
drivers/i2c/i2c-core-base.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff
Bring the ACPI path in sync with the device tree path and handle all the
IRQ fetching at probe time. This leaves the only IRQ handling at device
registration time being that which is passed directly through the board
info as either a resource or an actual IRQ number.
Signed-off-by: Charles Keepax
Remove the static from i2c_dev_irq_from _resources so that other parts
of the core code can use this helper function.
Signed-off-by: Charles Keepax
---
No changes since v2.
Thanks,
Charles
drivers/i2c/i2c-core-base.c | 4 ++--
drivers/i2c/i2c-core.h | 2 ++
2 files changed, 4 insertions(
It makes sense to contain all the ACPI IRQ handling in a single helper
function.
Signed-off-by: Charles Keepax
---
No changes since v2.
Thanks,
Charles
drivers/i2c/i2c-core-acpi.c | 3 +++
drivers/i2c/i2c-core-base.c | 3 ---
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/driv
In preparation for future refactoring factor out the fetch of the IRQ
into its own helper function.
Signed-off-by: Charles Keepax
---
Changes since v2:
- Don't consider zero to be a valid IRQ number
Thanks,
Charles
drivers/i2c/i2c-core-acpi.c | 33 +
1 file ch
Alan Stern writes:
> On Tue, 28 May 2019, Kalle Valo wrote:
>
>> The correct prefix is "p54:", but I can fix that during commit.
>
> Oh, okay, thanks.
>
>> > Index: usb-devel/drivers/net/wireless/intersil/p54/p54usb.c
>> > ===
>> > -
On 5/22/19 1:08 PM, Prarit Bhargava wrote:
>
>
> On 5/13/19 10:37 AM, Barret Rhoden wrote:
>> Hi -
>>
>
> Hey Barret, my apologies for not getting back to you earlier. I got caught up
> in something that took me away from this issue.
>
>> On 5/13/19 7:23 AM, Prarit Bhargava wrote:
>> [snip]
Fix gcc build error while CONFIG_REGMAP_MMIO is not set
drivers/staging/fieldbus/anybuss/arcx-anybus.o: In function `controller_probe':
arcx-anybus.c: undefined reference to `__devm_regmap_init_mmio_clk'
Select REGMAP_MMIO to fix it.
Reported-by: Hulk Robot
Fixes: 2411a336c8ce ("staging: fieldb
On Tue, May 28, 2019 at 10:31 AM YueHaibing wrote:
>
> Fix gcc build error while CONFIG_REGMAP_MMIO is not set
>
checkpatch.pl errors remain:
$ ./scripts/checkpatch.pl < ~/Downloads/YueHaibing.eml
ERROR: DOS line endings
#92: FILE: drivers/staging/fieldbus/anybuss/Kconfig:17:
+^Iselect REGMAP_MM
Sorry, this is broken, Pls igore this.
On 2019/5/28 22:29, YueHaibing wrote:
> Fix gcc build error while CONFIG_REGMAP_MMIO is not set
>
> drivers/staging/fieldbus/anybuss/arcx-anybus.o: In function
> `controller_probe':
> arcx-anybus.c: undefined reference to `__devm_regmap_init_mmio_clk'
>
>
Hi, Yang,
On 28.05.2019 15:44, Yang Shi wrote:
> Currently THP deferred split shrinker is not memcg aware, this may cause
> premature OOM with some configuration. For example the below test would
> run into premature OOM easily:
>
> $ cgcreate -g memory:thp
> $ echo 4G > /sys/fs/cgroup/memory/thp
On Wed, May 22, 2019 at 05:03:23PM -0700, Matt Helsley wrote:
> This series cleans up recordmcount and then makes it into
> an objtool subcommand.
>
> The series starts with 8 cleanup patches which make recordmcount
> easier to review and integrate with objtool. The final 5 patches
> show the begi
On Tue, 28 May 2019 15:46:59 +0200
Tomas Bortoli wrote:
> In case of errors, predicate_parse() goes to the out_free label
> to free memory and to return an error code.
>
> However, predicate_parse() does not free the predicates of the
> temporary prog_stack array, thence leaking them.
>
>
> Si
On Mon, May 20, 2019 at 02:28:35PM +0300, Leon Romanovsky wrote:
> > On Mon, May 20, 2019 at 01:19:02PM +0200, Michal Kubecek wrote:
> > > Commit 25c13324d03d ("IB/mlx5: Add steering SW ICM device memory
type")
> > > breaks i386 build by introducing three 64-bit divisions. As the
Hi,
On Tue, May 28, 2019 at 6:12 AM Ulf Hansson wrote:
>
> On Mon, 20 May 2019 at 20:41, Doug Anderson wrote:
> >
> > Hi,
> >
> > On Mon, Apr 29, 2019 at 1:41 PM Douglas Anderson
> > wrote:
> > >
> > > Processing SDIO interrupts while dw_mmc is suspended (or partly
> > > suspended) seems like
+++ Prarit Bhargava [28/05/19 10:30 -0400]:
On 5/22/19 1:08 PM, Prarit Bhargava wrote:
On 5/13/19 10:37 AM, Barret Rhoden wrote:
Hi -
Hey Barret, my apologies for not getting back to you earlier. I got caught up
in something that took me away from this issue.
On 5/13/19 7:23 AM, Prari
Based on your explanation, file->private_data can not be NULL before
call vbg_core_close_session method all the time, since
file->private_data is always set.
Am I right?
On Tue, May 28, 2019 at 9:19 PM Hans de Goede wrote:
>
> Hi,
>
> On 28-05-19 14:47, Young Xiao wrote:
> > vbg_misc_device_close
On Tue, 28 May 2019 09:43:28 -0500
Josh Poimboeuf wrote:
> Thanks for the patches. This looks like a good step in the right
> direction.
Good to hear.
>
> What's the performance difference between the old recordmcount and the
> new version which relies on elf_open()? It would be useful to co
Good day,
On Tue, May 28, 2019 at 01:19:24PM +0800, Leo Yan wrote:
> Hi Suzuki,
>
> On Wed, May 22, 2019 at 11:34:33AM +0100, Suzuki K Poulose wrote:
> > This series adds the support for CoreSight devices on ACPI based
> > platforms. The device connections are encoded as _DSD graph property[0],
>
Hi,
On 28-05-19 16:49, Yang Xiao wrote:
Based on your explanation, file->private_data can not be NULL before
call vbg_core_close_session method all the time, since
file->private_data is always set.
Am I right?
Yes.
Regards,
Hans
On Tue, May 28, 2019 at 9:19 PM Hans de Goede wrote:
Hi
On Wed, May 22, 2019 at 05:03:33PM -0700, Matt Helsley wrote:
> Rather than a standalone executable merge recordmcount as a sub
> command of objtool. This is a small step towards cleaning up
> recordmcount and eventually saving ELF code with objtool.
>
> For the initial step all that's required is
On Mon, May 27, 2019 at 03:37:20PM +0100, Catalin Marinas wrote:
> On Mon, May 06, 2019 at 06:30:51PM +0200, Andrey Konovalov wrote:
> > This patch is a part of a series that extends arm64 kernel ABI to allow to
> > pass tagged user pointers (with the top byte set to something else other
> > than 0
On Tue, May 28, 2019 at 1:42 AM Michal Hocko wrote:
>
> On Tue 28-05-19 11:04:46, Konstantin Khlebnikov wrote:
> > On 28.05.2019 10:38, Michal Hocko wrote:
> [...]
> > > Could you define the exact semantic? Ideally something for the manual
> > > page please?
> > >
> >
> > Like kswapd which works w
In order to subsequently add more tests for the arm64 architecture
we compile the tests target for arm64 systematically.
Signed-off-by: Raphael Gault
---
tools/perf/arch/arm64/Build | 2 +-
tools/perf/arch/arm64/tests/Build | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --g
The perf user-space tool relies on the PMU to monitor events. It offers an
abstraction layer over the hardware counters since the underlying
implementation is cpu-dependent. We want to allow userspace tools to have
access to the registers storing the hardware counters' values directly.
This targets
Add a documentation file to describe the access to the pmu hardware
counters from userspace
Signed-off-by: Raphael Gault
---
.../arm64/pmu_counter_user_access.txt | 42 +++
1 file changed, 42 insertions(+)
create mode 100644 Documentation/arm64/pmu_counter_user_access.tx
This test relies on the fact that the PMU registers are accessible
from userspace. It then uses the perf_event_mmap_page to retrieve
the counter index and access the underlying register.
This test uses sched_setaffinity(2) in order to run on all CPU and thus
check the behaviour of the PMU of all c
In order to be able to access the counter directly for userspace,
we need to provide the index of the counter using the userpage.
We thus need to override the event_idx function to retrieve and
convert the perf_event index to armv8 hardware index.
Since the arm_pmu driver can be used by any implem
In order to prevent the userspace processes which are trying to access
the registers from the pmu registers on a big.LITTLE environment we
introduce a hook to handle undefined instructions.
The goal here is to prevent the process to be interrupted by a signal
when the error is caused by the task b
On Tue 2019-05-28 23:21:17, Tetsuo Handa wrote:
> On 2019/05/28 22:42, Petr Mladek wrote:
> >> Ahh.. OK, now I sort of remember why I gave up on this idea (see [1]
> >> at the bottom, when it comes to uv_nmi_dump_state()) - printk_NMI and
> >> printk-safe redirections.
> >>
> >>NMI
> >>
Keep track of event opened with direct access to the hardware counters
and modify permissions while they are open.
The strategy used here is the same which x86 uses: everytime an event
is mapped, the permissions are set if required. The atomic field added
in the mm_context helps keep track of the
Add an extra test to check userspace access to pmu hardware counters.
This test doesn't rely on the seqlock as a synchronisation mechanism but
instead uses the restartable sequences to make sure that the thread is
not interrupted when reading the index of the counter and the associated
pmu register
On Sat, May 25, 2019 at 02:51:18PM -0700, Andrew Morton wrote:
> On Fri, 24 May 2019 13:50:45 -0400 Daniel Jordan
> wrote:
>
> > locked_vm accounting is done roughly the same way in five places, so
> > unify them in a helper. Standardize the debug prints, which vary
> > slightly, but include th
The patch
ASoC: cx2072x: fix spelling mistake "configued" -> "configured"
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the n
The patch
ASoC: cx2072x: remove redundant assignment to pulse_len
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 h
The patch
ASoC: cx2072x: fix integer overflow on unsigned int multiply
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
regulator: max77620: Support Maxim 77663
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
ASoC: max98357a: Show KConfig entry
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Li
The patch
spi: sh-msiof: Reduce delays in sh_msiof_modify_ctr_wait()
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 h
The patch
spi: spi-meson-spifc: update with SPDX Licence identifier
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 ho
> >> I have been wondering about xmit_more
> >> myself. I don’t think it changes anything for software timestamps,
> >> but it may with hardware timestamps.
> >
> > It arguably makes the software timestamp too early if taken on the
> > first segment, as the NIC is only informed of all the new descr
Fix two non-critical typos in the documentation of the dl_entity_overflow
function:
- "rather then" --> "rather than";
- "in such way that" --> "in such a way that".
Signed-off-by: Alessio Balsini
---
kernel/sched/deadline.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a
Add a system call to allow filesystem information to be queried. A request
value can be given to indicate the desired attribute. Support is provided
for enumerating multi-value attributes.
===
NEW SYSTEM CALL
===
The new system call looks like:
int ret = fsinfo(
Implement a misc device that implements a general notification queue as a
ring buffer that can be mmap()'d from userspace.
The way this is done is:
(1) An application opens the device and indicates the size of the ring
buffer that it wants to reserve in pages (this can only be set once):
Hi Al,
Here are a set of patches that adds a syscall, fsinfo(), that allows
attributes of a filesystem/superblock to be queried. Attribute values are
of four basic types:
(1) Version dependent-length structure (size defined by type).
(2) Variable-length string (up to PAGE_SIZE).
(3) Array
On Tue 28 May 2019 at 01:32, Paul Walmsley wrote:
> An update for those testing RISC-V patches: here's a new branch of
> riscv-pk/bbl that doesn't try to read or modify the DT data at all, which
> should be useful until U-Boot settles down. This new riscv-pk version
> should be easier to use
Hi Al,
Here are a set of patches that adds a syscall, fsinfo(), that allows
attributes of a filesystem/superblock to be queried. Attribute values are
of four basic types:
(1) Version dependent-length structure (size defined by type).
(2) Variable-length string (up to PAGE_SIZE).
(3) Array
Add a key/keyring change notification facility whereby notifications about
changes in key and keyring content and attributes can be received.
Firstly, an event queue needs to be created:
fd = open("/dev/event_queue", O_RDWR);
ioctl(fd, IOC_WATCH_QUEUE_SET_SIZE, page_size << n);
t
Allow fsinfo() to be used to query the filesystem attached to an fs_context
once a superblock has been created or if it comes from fspick().
This is done with something like:
fd = fsopen("ext4", 0);
...
fsconfig(fd, fsconfig_cmd_create, ...);
fsinfo(fd, NULL, ...);
Implement LSM parameter value retrieval with fsinfo() - akin to parsing
/proc/mounts. This allows all the LSM parameters to be retrieved in one go
with:
struct fsinfo_params params = {
.request= FSINFO_ATTR_LSM_PARAMETER,
};
The format is a blob containing
Add a notification count on mount objects so that the user can easily check
to see if a mount has changed its attributes or its children.
Future patches will:
(1) Provide this value through fsinfo() attributes.
(2) Hook into the notify_mount() function to provide a notification
interface
Introduce a non-repeating system-unique superblock ID that can be used to
tag superblock notification messages. The ID is time-based to make it
harder to use it as a covert communications channel.
Make it so that this ID can be fetched by the fsinfo() system call.
Signed-off-by: David Howells
-
Provide fsinfo() attributes that can be used to query a filesystem
parameter description. To do this, fsinfo() can be called on an
fs_context that doesn't yet have a superblock created and attached.
It can be obtained by doing, for example:
fd = fsopen("ext4", 0);
struct fsinfo_
Allow mount information, including information about the topology tree to
be queried with the fsinfo() system call. Usage of AT_FSINFO_MOUNTID_PATH
allows overlapping mounts to be queried.
To this end, four fsinfo() attributes are provided:
(1) FSINFO_ATTR_MOUNT_INFO.
This is a structure
Allow the fsinfo() syscall to look up a mount object by ID rather than by
pathname. This is necessary as there can be multiple mounts stacked up at
the same pathname and there's no way to look through them otherwise.
This is done by passing AT_FSINFO_MOUNTID_PATH to fsinfo() in the
parameters and
Implement parameter value retrieval with fsinfo() - akin to parsing
/proc/mounts.
This allows all the parameters to be retrieved in one go with:
struct fsinfo_params params = {
.request= FSINFO_ATTR_PARAMETER,
};
Each parameter comes as a pair of blobs wit
Add support for fsinfo() to kernfs and cgroup.
Signed-off-by: David Howells
---
fs/kernfs/mount.c | 20
include/linux/kernfs.h|4
kernel/cgroup/cgroup-v1.c | 44
kernel/cgroup/cgroup.c| 19 +
Add support to Smack for retrieval of the superblock parameters.
Signed-off-by: David Howells
---
security/smack/smack_lsm.c | 43 +++
1 file changed, 43 insertions(+)
diff --git a/security/smack/smack_lsm.c b/security/smack/smack_lsm.c
index 0de725f88
Add support to SELinux for retrieval of the superblock parameters by
fsinfo(FSINFO_ATTR_LSM_PARAMETERS).
Signed-off-by: David Howells
---
security/selinux/hooks.c| 41 +
security/selinux/include/security.h |2 +
security/selinux/ss/services.c |
Implement a program to demonstrate mount listing using the new fsinfo()
syscall, for example:
# ./test-mntinfo
ROOT 5dc ext4 8:12
\_ sys 138 sysfs 0:13
| \_ kernel/security 16
Add fsinfo support to the AFS filesystem.
Signed-off-by: David Howells
---
fs/afs/internal.h |1
fs/afs/super.c | 155 ++-
fs/fsinfo.c |3 +
include/uapi/linux/fsinfo.h | 12 +++
samples/vfs/test-fsinfo.c
Allow fsinfo() to retrieve information about a superblock, including the
values configured by the parameters passed at superblock creation.
Signed-off-by: David Howells
---
fs/nfs/fs_context.c | 163 +++
fs/nfs/internal.h |6 ++
fs/nfs/nfs4
On Tue, May 28, 2019 at 06:49:13AM -0400, Benjamin Coddington wrote:
> Maintainers, what's the best thing to do here: fold these into
> another patch version and post it (add attribution)? Add it as
> another patch at the end of the series?
Either would be fine. Yeah, if it was folded in then we
From: Ian Kent
The new fsinfo() system call adds a new super block operation
->fsinfo() which is used by file systems to provide file
system specific information for fsinfo() requests.
The fsinfo() request FSINFO_ATTR_PARAMETERS provides the same
function as sb operation ->show_options() so it n
On Thu, May 16, 2019 at 12:14:04PM +0300, Stanimir Varbanov wrote:
> Hi Bjorn,
>
> On 5/2/19 3:19 AM, Bjorn Andersson wrote:
> > Before introducing the QCS404 platform, which uses the same PCIe
> > controller as IPQ4019, migrate this to use the bulk clock API, in order
> > to make the error paths
From: Ian Kent
The new fsinfo() system call adds a new super block operation
->fsinfo() which is used by file systems to provide file
system specific information for fsinfo() requests.
The fsinfo() request FSINFO_ATTR_PARAMETERS provides the same
function as sb operation ->show_options() so it n
From: Ian Kent
The new fsinfo() system call adds a new super block operation
->fsinfo() which is used by file systems to provide file
system specific information for fsinfo() requests.
The fsinfo() request FSINFO_ATTR_PARAMETERS provides the same
function as sb operation ->show_options() so it n
From: Ian Kent
The new fsinfo() system call adds a new super block operation
->fsinfo() which is used by file systems to provide file
system specific information for fsinfo() requests.
The fsinfo() request FSINFO_ATTR_PARAMETERS provides the same
function as sb operation ->show_options() so it n
From: Ian Kent
The new fsinfo() system call adds a new super block operation
->fsinfo() which is used by file systems to provide file
system specific information for fsinfo() requests.
The fsinfo() request FSINFO_ATTR_PARAMETERS provides the same
function as sb operation ->show_options() so it n
From: Ian Kent
The new fsinfo() system call adds a new super block operation
->fsinfo() which is used by file systems to provide file
system specific information for fsinfo() requests.
The fsinfo() request FSINFO_ATTR_PARAMETERS provides the same
function as sb operation ->show_options() so it n
[Cc Pankaj Suryawanshi who has reported a similar problem
http://lkml.kernel.org/r/sg2pr02mb309806967ae91179cafec34be8...@sg2pr02mb3098.apcprd02.prod.outlook.com]
On Fri 24-05-19 16:11:14, Minchan Kim wrote:
> There was below bugreport from Wu Fangsuo.
>
> 7200 [ 680.491097] c4 7125 (syz-executo
From: Ian Kent
The new fsinfo() system call adds a new super block operation
->fsinfo() which is used by file systems to provide file
system specific information for fsinfo() requests.
The fsinfo() request FSINFO_ATTR_PARAMETERS provides the same
function as sb operation ->show_options() so it n
---
Documentation/filesystems/fsinfo.rst | 571 ++
1 file changed, 571 insertions(+)
create mode 100644 Documentation/filesystems/fsinfo.rst
diff --git a/Documentation/filesystems/fsinfo.rst
b/Documentation/filesystems/fsinfo.rst
new file mode 100644
index 00
From: Ian Kent
The new fsinfo() system call adds a new super block operation
->fsinfo() which is used by file systems to provide file
system specific information for fsinfo() requests.
The fsinfo() request FSINFO_ATTR_PARAMETERS provides the same
function as sb operation ->show_options() so it n
prempt_disable/enable tracepoints occurs only in the preemption
enabled <-> disable transition. As preempt_latency_stop() and
preempt_latency_start() already do this control, avoid code
duplication by using these functions in the softirq code as well.
RFC: Should we move preempt_latency_start/pree
The preempt_disable tracepoint only traces in the disable <-> enable case.
Which is correct, but think about this case:
--- %< --
THREAD IRQ
| |
preempt_disable_notra
Oops, I posted this on the wrong branch - will repost on the right branch.
David
The preempt_disable/enable tracepoint only traces in the disable <-> enable
case, which is correct. But think about this case:
%< --
THREAD IRQ
| |
preem
While playing with the model + working in a fix for the task
context & trace recursion, I ended up hitting two cases in which the
preempt_disable/enable tracepoint was supposed to happen, but didn't.
There is an explanation for each case in the log message.
This is an RFC exposing the problem, wi
On 5/28/19 4:44 PM, Steven Rostedt wrote:
> On Tue, 28 May 2019 15:46:59 +0200
> Tomas Bortoli wrote:
>
>> In case of errors, predicate_parse() goes to the out_free label
>> to free memory and to return an error code.
>>
>> However, predicate_parse() does not free the predicates of the
>> tempora
Em Tue, May 28, 2019 at 04:03:14PM +0100, Raphael Gault escreveu:
> In order to subsequently add more tests for the arm64 architecture
> we compile the tests target for arm64 systematically.
Humm, the subject doesn't match the description? I.e. it _was_
unconditionally built, now it is only built
Add support for fsinfo().
Signed-off-by: David Howells
---
fs/hugetlbfs/inode.c | 56 ++
1 file changed, 56 insertions(+)
diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
index 1dcc57189382..e6ecebd9ebc2 100644
--- a/fs/hugetlbfs/inode.
> On May 28, 2019, at 11:13 AM, J. Bruce Fields wrote:
>
> On Tue, May 28, 2019 at 06:49:13AM -0400, Benjamin Coddington wrote:
>> Maintainers, what's the best thing to do here: fold these into
>> another patch version and post it (add attribution)? Add it as
>> another patch at the end of th
On Mon, 27 May 2019, Jiri Kosina wrote:
> > Looks this has been discussed in the past.
> >
> > http://lists.infradead.org/pipermail/linux-nvme/2019-April/023234.html
> >
> > I created a fix for a case but not good enough.
> >
> > http://lists.infradead.org/pipermail/linux-nvme/2019-April/023277
On 2019/05/29 0:03, Petr Mladek wrote:
>> But is context dependent buffer large enough to hold SysRq-t output?
>> I think that only main logbuf can become large enough to hold SysRq-t output.
>
> SysRq messages are stored directly into the main log buffer.
>
> The limited per-CPU buffers are need
Christian Brauner writes:
> This adds the clone6 system call.
>
> As mentioned several times already (cf. [7], [8]) here's the promised
> patchset for clone6().
>
> We recently merged the CLONE_PIDFD patchset (cf. [1]). It took the last
> free flag from clone().
>
> Independent of the CLONE_PIDFD
On Tue, 28 May 2019 17:18:59 +0200
Tomas Bortoli wrote:
> >> + memset(prog_stack, 0, nr_preds * sizeof(*prog_stack));
> >> +
> >
> > Can you instead just switch the allocation of prog_stack to use
> > kcalloc()?
>
> kmalloc_array() is safe against arithmetic overflow of the arguments.
> Us
On Tue, May 28, 2019 at 04:01:03PM +0200, Peter Zijlstra wrote:
> On Tue, May 28, 2019 at 08:31:29PM +0800, Young Xiao wrote:
> > When a kthread calls call_usermodehelper() the steps are:
> > 1. allocate current->mm
> > 2. load_elf_binary()
> > 3. populate current->thread.regs
> >
> > While
On Mon, May 27, 2019 at 07:06:38PM -0700, Florian Fainelli wrote:
> Both sysfs-bus-mdio and sysfs-class-net-phydev contain the same
> duplication information. There is not currently any MDIO bus specific
> attribute, but there are PHY device (struct phy_device) specific
> attributes. Use the more p
A packed AppArmor policy contains null-terminated tag strings that are read
by unpack_nameX(). However, unpack_nameX() uses string functions on them
without ensuring that they are actually null-terminated, potentially
leading to out-of-bounds accesses.
Make sure that the tag string is null-termina
On 5/28/19 5:29 PM, Steven Rostedt wrote:
> On Tue, 28 May 2019 17:18:59 +0200
> Tomas Bortoli wrote:
>
+ memset(prog_stack, 0, nr_preds * sizeof(*prog_stack));
+
>>>
>>> Can you instead just switch the allocation of prog_stack to use
>>> kcalloc()?
>>
>> kmalloc_array() is safe ag
On 2019/5/28 22:35, Sven Van Asbroeck wrote:
> On Tue, May 28, 2019 at 10:31 AM YueHaibing wrote:
>>
>> Fix gcc build error while CONFIG_REGMAP_MMIO is not set
>>
>
> checkpatch.pl errors remain:
>
> $ ./scripts/checkpatch.pl < ~/Downloads/YueHaibing.eml
> ERROR: DOS line endings
> #92: FILE: dr
Dear Linux folks,
Occasionally, Linux outputs the message below on the workstation Dell
OptiPlex 5040 MT.
TCP: net00: Driver has suspect GRO implementation, TCP performance may be
compromised.
Linux 4.14.55 and Linux 5.2-rc2 show the message, and the WWW also
gives some hits [1][2].
```
$
On Mon, May 27, 2019 at 1:54 PM Gustavo A. R. Silva
wrote:
>
> Fix logically dead code in switch statement.
>
> Notice that *ret* is updated with -ENOMEM before the switch statement
> at 395:
>
> 395 switch (ret) {
> 396 case -ENODATA:
> 397 case -ED
In case of errors, predicate_parse() goes to the out_free label
to free memory and to return an error code.
However, predicate_parse() does not free the predicates of the
temporary prog_stack array, thence leaking them.
Signed-off-by: Tomas Bortoli
Reported-by: syzbot+6b8e0fb820e570c59...@syzkal
Hi Miquel,
> > >
> > > > Some of the SPI NAND devices has parameter page which is similar to
> ONFI
> > > > table.
> > > >
> > > > But, it may not be self sufficient to propagate all the required
> > > > parameters. Fixup function has been added in struct manufacturer to
> > > > accommodate this.
On Tue, 2019-05-28 at 11:43 +0100, Robin Murphy wrote:
> On 27/05/2019 17:08, Miles Chen wrote:
> > This change makes CONFIG_ZONE_DMA32 defuly y and allows users
> > to overwrite it.
> >
> > For the SoCs that do not need CONFIG_ZONE_DMA32, this is the
> > first step to manage all available memory
On Tue, 28 May 2019 17:43:38 +0200
Tomas Bortoli wrote:
> In case of errors, predicate_parse() goes to the out_free label
> to free memory and to return an error code.
>
> However, predicate_parse() does not free the predicates of the
> temporary prog_stack array, thence leaking them.
Thanks, I
401 - 500 of 936 matches
Mail list logo
