Hi Steven,
Does the patch look good? Can this be picked up in the next rc?
Vaibhav
On Fri, Sep 7, 2018 at 3:31 PM Vaibhav Nagarnaik wrote:
>
> When reducing ring buffer size, pages are removed by scheduling a work
> item on each CPU for the corresponding CPU ring buffer. After the pages
> are
On Thu, Aug 30, 2018 at 04:11:59PM -0600, Jon Derrick wrote:
> Hi Bjorn,
>
> Sorry for the delay on this one and pushing it after RC1.
> Feel free to queue it up for 4.20 if it looks fine.
>
> I've added comments to the git log and source explaining why
> calculate_iosize was left unchanged.
Al Viro wrote:
> > Add two new iterator types to iov_iter:
> >
> > (1) ITER_MAPPING
> >
> > This walks through a set of pages attached to an address_space that
> > are pinned or locked, starting at a given page and offset and walking
> > for the specified amount of space. A
On Mon, 17 Sep 2018 13:53:05 -0700
Vaibhav Nagarnaik wrote:
> Hi Steven,
>
> Does the patch look good? Can this be picked up in the next rc?
>
Yes it's fine. I can pick it up. Does it need to be marked for stable?
Thanks!
-- Steve
On Mon, 2018-09-17 at 15:53 -0500, Bjorn Helgaas wrote:
> On Thu, Aug 30, 2018 at 04:11:59PM -0600, Jon Derrick wrote:
> > Hi Bjorn,
> >
> > Sorry for the delay on this one and pushing it after RC1.
> > Feel free to queue it up for 4.20 if it looks fine.
> >
> > I've added comments to the git
On Mon, Sep 17, 2018 at 2:01 PM Steven Rostedt wrote:
>
> On Mon, 17 Sep 2018 13:53:05 -0700
> Vaibhav Nagarnaik wrote:
>
> > Hi Steven,
> >
> > Does the patch look good? Can this be picked up in the next rc?
> >
>
> Yes it's fine. I can pick it up. Does it need to be marked for stable?
Thanks.
On 09/07/2018 05:25 AM, Peter Zijlstra wrote:
On Thu, Aug 30, 2018 at 01:24:58PM -0700, subhra mazumdar wrote:
+void pipe_busy_wait(struct pipe_inode_info *pipe)
+{
+ unsigned long wait_flag = pipe->pipe_wait_flag;
+ unsigned long start_time = pipe_busy_loop_current_time();
+
+
On Mon, Sep 17, 2018 at 08:38:16PM +, Walker, Benjamin wrote:
> On Mon, 2018-08-20 at 14:32 -0700, Howell, Seth wrote:
> > Hi Jason,
> >
> > I apologize for the few days of radio silence on this one. I was able to
> > apply
> > your patch on my local configuration and can confirm that it
Hi Linus,
> The one change that stands out and merits mention is the code of
> conduct addition...
The Code of Conflict was perfectly fine. Whomever convinced you to add
the Code of Conduct was convincing you to give control over to a social
justice initiative that has no interest in the
On Mon, Sep 17, 2018 at 6:55 PM Oleg Nesterov wrote:
>
> On 09/17, Rafael J. Wysocki wrote:
> >
> > On Fri, Sep 14, 2018 at 6:21 PM Oleg Nesterov wrote:
> > >
> > > > > Since you are adding the notifier anyway, what about designing it to
> > > > > make
> > > > > the thread wait on _PREPARE
On Mon, Sep 17, 2018 at 01:40:07PM -0700, Stephen Boyd wrote:
> Let's change the function signature to return the pointer to memory or
> an error pointer on failure, and take an argument that lets us return
> the size of the aux data read. This way we can remove the
> cmd_db_read_aux_data_len()
On Mon, Sep 17, 2018 at 12:02:56PM +0200, Roberto Sassu wrote:
> This code has the same behavior of tpm2_get_pcr_allocation(). If some
> banks are not used, set the algorithm of the first unused to
> TPM_ALG_ERROR.
My point is that maybe it would sense to use zero for that in order
to make code a
On Mon, Sep 17, 2018 at 1:34 PM Stepan Golosunov wrote:
>
> On Sun, Sep 16, 2018 at 06:04:57PM -0700, Deepa Dinamani wrote:
> > static long do_compat_pselect(int n, compat_ulong_t __user *inp,
> > compat_ulong_t __user *outp, compat_ulong_t __user *exp,
> > - struct old_timespec32
On Wed, Sep 12, 2018 at 07:39:16PM -0500, David Lechner wrote:
> This series introduces a new SPI mode flag, SPI_CS_WORD, that indicates that
> the chip select line should be toggled after each word sent. This series
> includes examples of how this can be implemented for both an SPI controller
>
On Thu, Sep 13, 2018 at 09:26:48AM -0500, David Lechner wrote:
> On 09/13/2018 08:44 AM, Geert Uytterhoeven wrote:
> I suppose it might be best to modify the SPI core to say:
> if ((spi->mode & SPI_CS_WORD) && (!(ctlr->mode_bits & SPI_CS_WORD) ||
>
On Mon, Sep 17, 2018 at 09:54:37AM -0400, Boris Ostrovsky wrote:
> On 9/16/18 3:25 PM, Jarkko Sakkinen wrote:
> > On Thu, Sep 13, 2018 at 05:25:51PM -0400, Boris Ostrovsky wrote:
> >> From: "Dr. Greg Wettstein"
> >>
> >> Functionality of the xen-tpmfront driver was lost secondary to
> >> the
The patch
spi: add software implementation for SPI_CS_WORD
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
The patch
spi: pic32-sqi: remove unnecessary of_node_get()
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
The patch
regulator: pfuze100-regulator: fix spelling mistake "standy" -> "standby"
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually
Jacek
On 09/17/2018 02:22 PM, Jacek Anaszewski wrote:
> Dan,
>
> On 09/17/2018 05:24 PM, Dan Murphy wrote:
>> Jacek
>>
>> On 09/15/2018 03:00 PM, Jacek Anaszewski wrote:
>>> Hi Pavel.
>>>
>>> On 09/14/2018 11:42 PM, Pavel Machek wrote:
Hi!
>> You may want to learn more about device
On Mon, Sep 10, 2018 at 10:18:22AM -0700, Tadeusz Struk wrote:
> The TCG SAPI specification [1] defines a set of functions, which allow
> applications to use the TPM device in either blocking or non-blocking fashion.
> Each command defined by the specification has a corresponding
>
Trond Myklebust wrote:
> Another question that is relevant for most networked filesystems
> (including AFS, I believe), is how will you deal with encryption of the
> data you are transmitting? Encrypting and decrypting in-place directly
> in the page cache or in a userspace O_DIRECT mapped
sysrq_handle_crash() dereferences a NULL pointer on purpose to force
an exception, the local variable 'killer' is assigned to NULL and
dereferenced later. Clang detects the NULL pointer dereference at compile
time and emits a BRK instruction (on arm64) instead of the expected NULL
pointer
Hello,
syzbot found the following crash on:
HEAD commit:5815ca49bf07 Temporarily revert "Revert "kmsan: don't trac..
git tree: https://github.com/google/kmsan.git/master
console output: https://syzkaller.appspot.com/x/log.txt?x=14dafb6640
kernel config:
The patch
regulator: fixed: Convert to use GPIO descriptor only
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
spi: pxa2xx: Remove the shutdown callback
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
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 Linus
On Mon, 17 Sep 2018 14:02:59 -0700
Vaibhav Nagarnaik wrote:
> On Mon, Sep 17, 2018 at 2:01 PM Steven Rostedt wrote:
> >
> > On Mon, 17 Sep 2018 13:53:05 -0700
> > Vaibhav Nagarnaik wrote:
> >
> > > Hi Steven,
> > >
> > > Does the patch look good? Can this be picked up in the next rc?
> > >
Dan,
On 09/17/2018 05:24 PM, Dan Murphy wrote:
> Jacek
>
> On 09/15/2018 03:00 PM, Jacek Anaszewski wrote:
>> Hi Pavel.
>>
>> On 09/14/2018 11:42 PM, Pavel Machek wrote:
>>> Hi!
>>>
> You may want to learn more about device tree and/or talk to the device
> tree maintainers. This is an
On 09/17/2018 11:14 AM, Kees Cook wrote:
> On Mon, Sep 17, 2018 at 10:13 AM, Casey Schaufler
> wrote:
>> TOMOYO uses the cred blob pointer. When the blob is shared TOMOYO
>> has to be allocated a pointer size chunk to store the pointer in.
>> Smack has the same behavior on file blobs.
>
> Oh
On 9/17/2018 11:08 PM, Stephen Boyd wrote:
Quoting Sai Prakash Ranjan (2018-09-11 03:46:01)
On 9/9/2018 1:57 AM, Sai Prakash Ranjan wrote:
+void notrace pstore_event_call(struct trace_event_buffer *fbuffer)
+{
+ struct trace_iterator *iter;
+ struct trace_seq *s;
+ struct
On 9/15/18 2:21 AM, Matthew Wilcox wrote:
On Sat, Sep 15, 2018 at 04:34:57AM +0800, Yang Shi wrote:
Suggested-by: Michal Hocko
Suggested-by: Kirill A. Shutemov
Suggested-by: Matthew Wilcox
Reviewed-by: Matthew Wilcox
Looks good! Thanks for sticking with this patch series.
Thanks for
This patch adds the SC2731 PMIC switch charger support.
Signed-off-by: Baolin Wang
Reviewed-by: Krzysztof Kozlowski
---
Changes from v2:
- Add reviewed tag from Krzysztof.
- Change current unit to uA instead of mA.
Changes from v1:
- Remove some redundant head files.
- Add one mutex to
This patch adds the binding documentation for Spreadtrum SC2731 charger
device.
Signed-off-by: Baolin Wang
Reviewed-by: Krzysztof Kozlowski
---
Changes from v2:
- Add reviewed tag from Krzysztof.
Changes from v1:
- Add parent node.
- Add some battery standard properties.
---
Without this, an fsync call is sent to the server even if no data
changed. This resulted in a rather severe (50%) performance regression
under certain metadata-heavy workloads.
In the past, everything was direct IO. Nothing happend on a close call.
An explicit fsync call would send an fsync
This is necessary to ensure the uid/gid responsible for the write is
communicated with the server. Only one uid/gid may have outstanding
changes at a time. If another uid/gid writes while there are
outstanding changes, the changes must be written out before the new
data is put into the page.
Go through pages and look for a consecutive writable region. After
finding 128 consecutive writable pages or when finding a non-consecutive
region, do the write.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/inode.c | 135 +-
If no major issues are found in review or in our testing, we intend to
submit this during the next merge window.
The goal of all this is to significantly reduce the number of network
requests made to the OrangeFS
First the xattr cache is needed because otherwise we make a ton of
getxattr calls
/linux/commits/H-kon-Bugge/IB-mlx4-Enable-debug-print-of-SMPs/20180917-232956
config: i386-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed
Oleg Nesterov writes:
> absolutely off-topic question,
>
> On 09/16, Eric W. Biederman wrote:
>>
>> @@ -747,11 +746,9 @@ void do_coredump(const siginfo_t *siginfo)
>> }
>>
>> /* get us an unshared descriptor table; almost always a no-op */
>> -retval = unshare_files();
>> +
On 9/17/2018 11:14 AM, Kees Cook wrote:
>
>> Keep security=$lsm with the existing exclusive behavior.
>> Add lsm=$lsm1,...,$lsmN which requires a full list of modules
>>
>> If you want to be fancy (I don't!) you could add
>>
>> lsm.add=$lsm1,...,$lsmN which adds the modules to the stack
>>
On 09/17/2018 12:23 PM, Casey Schaufler wrote:
> On 9/17/2018 11:14 AM, Kees Cook wrote:
>>
>>> Keep security=$lsm with the existing exclusive behavior.
>>> Add lsm=$lsm1,...,$lsmN which requires a full list of modules
>>>
>>> If you want to be fancy (I don't!) you could add
>>>
>>>
Signed-off-by: Martin Brandenburg
---
fs/orangefs/super.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/fs/orangefs/super.c b/fs/orangefs/super.c
index 4c36481208f5..61bec955b285 100644
--- a/fs/orangefs/super.c
+++ b/fs/orangefs/super.c
@@ -406,15
OrangeFS accepts a mask indicating which attributes were changed. The
kernel must not set any bits except those that were actually changed.
The kernel must set the uid/gid of the request to the actual uid/gid
responsible for the change.
Code path for notify_change initiated setattrs is
Remove orangefs_inode_read. It was used by readpage. Calling
wait_for_direct_io directly serves the purpose just as well. There is
now no check of the bufmap size in the readpage path. There are already
other places the bufmap size is assumed to be greater than PAGE_SIZE.
Important to call
Signed-off-by: Martin Brandenburg
---
fs/orangefs/orangefs-kernel.h | 1 +
fs/orangefs/orangefs-utils.c | 2 +-
fs/orangefs/waitqueue.c | 18 ++
3 files changed, 12 insertions(+), 9 deletions(-)
diff --git a/fs/orangefs/orangefs-kernel.h b/fs/orangefs/orangefs-kernel.h
On Mon, Sep 17, 2018 at 12:25 PM, Andy Lutomirski wrote:
> On Fri, Sep 14, 2018 at 5:50 AM, Thomas Gleixner wrote:
>> The code flow for the vclocks is convoluted as it requires the vclocks
>> which can be invalidated separately from the vsyscall_gtod_data sequence to
>> store the fact in a
Now orangefs_inode_getattr fills from cache if an inode has dirty pages.
also if attr_valid and dirty pages and !flags, we spin on inode writeback
before returning if pages still dirty after: should it be other way
Signed-off-by: Martin Brandenburg
---
fs/orangefs/file.c | 77
Signed-off-by: Martin Brandenburg
---
fs/orangefs/inode.c | 10 +-
fs/orangefs/orangefs-cache.c | 24 ++--
fs/orangefs/orangefs-kernel.h | 6 --
fs/orangefs/orangefs-mod.c| 10 +-
4 files changed, 36 insertions(+), 14 deletions(-)
diff
Would happen if an inode is dirty but whatever happened is not something
that can be written out to OrangeFS.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/orangefs-utils.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/fs/orangefs/orangefs-utils.c b/fs/orangefs/orangefs-utils.c
On Mon, 2018-08-20 at 14:32 -0700, Howell, Seth wrote:
> Hi Jason,
>
> I apologize for the few days of radio silence on this one. I was able to apply
> your patch on my local configuration and can confirm that it fixes the issue
> of send with invalidate being improperly mapped between a
On 09/16/2018 06:35 AM, Sebastian Reichel wrote:
> Hi,
>
> On Sun, Jul 22, 2018 at 09:33:56PM +0800, Liu Xiang wrote:
>> According to the datasheet, bq27411 is similar to bq27421.
>>
>> Signed-off-by: Liu Xiang
>> ---
>
> Looks good to me. Do you plan to test/review this Andrew, or
> should I
On 17.09.2018 09:52, Nick Desaulniers wrote:
> On Sun, Sep 16, 2018 at 8:15 AM Nathan Chancellor
> wrote:
>>
>> On Sun, Sep 16, 2018 at 10:53:51AM +0100, Jonathan Cameron wrote:
>> > On Fri, 14 Sep 2018 22:25:11 -0700
>> > Nathan Chancellor wrote:
>> >
>> > > Clang warns when an enumerated type
On 9/15/18 3:10 AM, Matthew Wilcox wrote:
On Sat, Sep 15, 2018 at 04:34:56AM +0800, Yang Shi wrote:
Regression and performance data:
Did the below regression test with setting thresh to 4K manually in the code:
* Full LTP
* Trinity (munmap/all vm syscalls)
* Stress-ng:
This is a fairly big change, but ultimately it's not a lot of code.
Implement write_inode and then avoid the call to orangefs_inode_setattr
within orangefs_setattr.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/inode.c | 11 +++
fs/orangefs/super.c | 16
2 files
It's a copy of the loop which would run in read_pages from
mm/readahead.c.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/inode.c | 39 +--
1 file changed, 1 insertion(+), 38 deletions(-)
diff --git a/fs/orangefs/inode.c b/fs/orangefs/inode.c
index
When an inode is created, we fetch attributes from the server. There is
no need to turn around and invalidate them.
No need to initialize attributes after the getattr either. Either it'll
be exactly the same, or it'll be something else and wrong.
Signed-off-by: Martin Brandenburg
---
No need to store the received mask. It is either STATX_BASIC_STATS or
STATX_BASIC_STATS & ~STATX_SIZE. If STATX_SIZE is requested, the cache
is bypassed anyway, so the cached mask is unnecessary to decide whether
to do a real getattr.
This is a change. Previously a getattr would want size and
This uses the same timeout as the getattr cache. This substantially
increases performance when writing files with smaller buffer sizes.
When writing, the size is (often) changed, which causes a call to
notify_change which calls security_inode_need_killpriv which needs a
getxattr. Caching it
This should be a no-op now, but once inode writeback works, it'll be
necessary to have the correct attribute in the dirty inode.
Previously the attribute fetch timeout was marked invalid and the server
provided the updated attribute. When the inode is dirty, the server
cannot be consulted since
This should be a no-op now. When inode writeback works, this will
prevent a getattr from overwriting inode data while an inode is
transitioning to dirty.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/inode.c | 4 ++--
fs/orangefs/orangefs-utils.c | 33
The cmd_db_get_header() function is a static local function that doesn't
need to copy anything from one place to another. Instead, it can just
point into the region by returning pointers to what we're looking for.
If we do that, we should mark what we're returning as const so that code
can't
Let's change the function signature to return the pointer to memory or
an error pointer on failure, and take an argument that lets us return
the size of the aux data read. This way we can remove the
cmd_db_read_aux_data_len() API entirely and also get rid of the memcpy
operation from cmd_db to the
This commit fixes the wrong usage of pr_info introduced by the
commit e728e4f20100 ("ARM: s3c24xx: formatting cleanup in
mach-mini2440.c").
Since the idea is to print on a single line, pr_cont has to be used.
Signed-off-by: Cedric Roux
---
arch/arm/mach-s3c24xx/mach-mini2440.c | 6 +++---
1
Some changes to the cmd-db code to not do any more copying
of memory. Instead, we'll just hand out pointers to things
inside cmd-db.
Changes from v1:
* Fixed patch#2 for GPU wreckage
Cc: Mahesh Sivasubramanian
Cc: Lina Iyer
Cc: Bjorn Andersson
Cc: Evan Green
Cc: Jordan Crouse
Cc: Rob
Oleg Nesterov writes:
> On 09/16, Eric W. Biederman wrote:
>>
>> Oleg Nesterov writes:
>>
>> > As for binder.c, in this case we probably actually want to unshare ->files
>> > on exec so we can ignore it?
>>
>> Looking at the binder case it only captures ->files on mmap. Exec
>> ditches the
Hi Rob,
On 17 September 2018 at 11:26, Rob Herring wrote:
> On Wed, Sep 12, 2018 at 03:29:38PM +0800, Baolin Wang wrote:
>> This patch adds the binding documentation for Spreadtrum SC27XX series PMICs
>> fuel gauge unit device, which is used to calculate the battery capacity.
>>
>>
On Sun, Sep 16, 2018 at 10:40:22PM -0700, James Bottomley wrote:
> On Sun, 2018-09-16 at 22:19 +0300, Jarkko Sakkinen wrote:
> > On Thu, Sep 13, 2018 at 05:45:54PM +0100, David Howells wrote:
> > > Jarkko Sakkinen wrote:
> > >
> > > > David, what do you think?
> > >
> > > Which David?
> > >
>
"Rafael J. Wysocki" writes:
> On Sat, Sep 15, 2018 at 8:53 AM Francisco Jerez wrote:
>>
>> "Rafael J. Wysocki" writes:
>>
>> > On Tuesday, September 11, 2018 7:35:15 PM CEST Francisco Jerez wrote:
>> >>
>> >> "Rafael J. Wysocki" writes:
>> >>
>> >> > On Thursday, September 6, 2018 6:20:08 AM
On Mon, Sep 17, 2018 at 2:36 PM Steven Rostedt wrote:
>
> On Mon, 17 Sep 2018 14:02:59 -0700
> Vaibhav Nagarnaik wrote:
>
> > On Mon, Sep 17, 2018 at 2:01 PM Steven Rostedt wrote:
> > >
> > > On Mon, 17 Sep 2018 13:53:05 -0700
> > > Vaibhav Nagarnaik wrote:
> > >
> > > > Hi Steven,
> > > >
> >
On 9/17/2018 12:55 PM, John Johansen wrote:
> On 09/17/2018 12:23 PM, Casey Schaufler wrote:
>> On 9/17/2018 11:14 AM, Kees Cook wrote:
Keep security=$lsm with the existing exclusive behavior.
Add lsm=$lsm1,...,$lsmN which requires a full list of modules
If you want to be fancy
Regarding those who are ejected from the Linux Kernel Community after
this CoC:
Contributors can, at any time, rescind the license grant regarding their
property via written notice to those whom they are rescinding the grant
from (regarding their property (code)).
The GPL version 2 lacks a
On Mon, Sep 17, 2018 at 08:56:34PM +0200, Andreas Kemnade wrote:
> Hi Dmitry,
>
> On Mon, 17 Sep 2018 10:51:31 -0700
> Dmitry Torokhov wrote:
>
> > Hi Andreas,
> >
> > On Mon, Sep 17, 2018 at 07:22:54AM +0200, Andreas Kemnade wrote:
> > > When runtime is not enabled, pm_runtime_get_sync()
On Mon, 2018-09-17 at 15:08 -0600, Jason Gunthorpe wrote:
> On Mon, Sep 17, 2018 at 08:38:16PM +, Walker, Benjamin wrote:
> > We've recently run into this same issue on i40iw, which appears to make the
> > same
> > mistake of using the kernel version of the enum instead of the userspace
> >
On Thu, Sep 13, 2018 at 11:00 AM Mika Westerberg
wrote:
>
> On Mon, Sep 10, 2018 at 12:33:33PM +0300, Mika Westerberg wrote:
> > Hi Lukas,
> >
> > I'm including Greg here in case I've done something wrong as a maintainer.
> > Since I've only maintained Thunderbolt quite short time, it may be that
On Mon, Sep 17, 2018 at 05:25:27PM +0530, Pintu Kumar wrote:
> On Mon, Sep 17, 2018 at 11:46 AM Pintu Kumar wrote:
> > > > But still no effect.
> > > > And I checked LTP test cases. It almost doing the same thing.
> > > >
> > > > I observed that [ksmd] thread is not waking up at all.
> > > > I
In order to identify which thread triggered the event in the
multi-threaded program, add the FAN_EVENT_INFO_TID tag in fanotify_init
to select whether to report the event creator's thread id information.
Signed-off-by: nixiaoming
---
fs/notify/fanotify/fanotify.c | 5 -
On Mon, Sep 17, 2018 at 10:17:55AM +0200, Peter Zijlstra wrote:
> On Sat, Sep 15, 2018 at 10:55:13PM +0800, Guo Ren wrote:
> > > > +#define ATOMIC_OP_RETURN(op, c_op)
> > > > \
>
> > > > +#define ATOMIC_FETCH_OP(op, c_op)
On Sun, 9 Sep 2018, Dou Liyang wrote:
> From: Dou Liyang
>
> Linux has spread out the non managed interrupt across the possible
> target CPUs to avoid vector space exhaustion.
>
> But, the same situation may happen on the managed interrupts.
Second thougts on this.
Spreading the managed
alsa_conformance_test -C hw:0,4 -p 1024 --debug
would sometime show:
TIME_DIFF(s)HW_LEVEL READ RATE
0.95970 1024 102410670001.041992
0.042609555 1024 2048 24032.168372
0.021330364 1024 3072 48006.681930
On 09/16, Eric W. Biederman wrote:
>
> @@ -1291,6 +1292,12 @@ int flush_old_exec(struct linux_binprm * bprm)
> flush_thread();
> current->personality &= ~bprm->per_clear;
>
> + retval = unshare_files();
I was going to sugget basically the same changes, please feel free to add
my
On Mon, Sep 17, 2018 at 5:49 AM Heikki Krogerus
wrote:
> I hit a BUG while attempting to unload fusb302 driver module on my
> Intel CHT board (GPDWin). I bisected it to commit:
>
> 461c1a7d4733 ("gpiolib: override irq_enable/disable")
Sorry for not getting the fix out to next in time,
On 09/16, Eric W. Biederman wrote:
>
> Oleg's patch to remove get_files_struct from proc means we don't need
> two counts in files_struct.
So it seems you agree with this patch at least in general.
OK, if nobody else objects I'll split this patch and send the series
tomorrow.
> Eric W.
[I'm not sure who the best people to ask about this are, I hope the
recipient list resembles something reasonable...]
I have noticed that the dup_mmap() logic on fork() doesn't handle
pages with active direct I/O properly: dup_mmap() seems to assume that
making the PTE referencing a page readonly
On Mon, Sep 17, 2018 at 02:10:41PM +0200, Lubomir Rintel wrote:
> This allows use of SPI when power management is disables, such as on
> early boot;
>
> See also: commit 31eb74318054 ("PM / runtime: Fix handling of suppliers
> with disabled runtime PM")
> if (!was_busy &&
On Mon, 17 Sep 2018, Christoph Hellwig wrote:
> > Just for the record, this would be the first (architected) timer ever which
> > just works. I'm having a hard time to believe this, but I'd certainly
> > welcome it.
>
> And that would be the contact with reality.
I've dealt with the reality of
On Mon, Sep 17, 2018 at 03:42:32PM +0100, John Garry wrote:
> - dead e-mail addresses (Zhichang, Gabriele)
>
> On 13/09/2018 13:48, Andrew Murray wrote:
>
> Hi Andrew,
>
> > The !CONFIG_GENERIC_IOMAP version of ioport_map uses MMIO_UPPER_LIMIT to
> > prevent users from making I/O accesses
> -Original Message-
> From: Greg KH
> Sent: Monday, September 17, 2018 7:28 AM
> To: KY Srinivasan
> Cc: o...@aepfle.de; Stephen Hemminger ;
> jasow...@redhat.com; linux-kernel@vger.kernel.org; Michael Kelley
> (EOSG) ; a...@canonical.com;
> de...@linuxdriverproject.org; vkuznets
>
On 09/16, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> > IOW. Lets ignore do_close_on_exec(), lets ignore the fact that unshare_fd()
> > can fail and thus it makes sense to call it before point-of-no-return.
> >
> > Any other reason why we can't simply call unshare_files() at the end of
From: Christophe Kerello
This patch adds the documentation of the device tree bindings for the STM32
FMC2 NAND controller.
Signed-off-by: Christophe Kerello
---
.../devicetree/bindings/mtd/stm32-fmc2-nand.txt| 90 ++
1 file changed, 90 insertions(+)
create mode 100644
On Thu, Aug 30, 2018 at 08:02:05PM +0200, Krzysztof Kozlowski wrote:
> Samsung Exynos SoCs and boards related bindings evolved since the initial
> introduction, but initially the bindings were minimal and a bit incomplete
> (they never described all the hardware modules available in the SoCs).
>
/linux/commits/H-kon-Bugge/IB-mlx4-Enable-debug-print-of-SMPs/20180917-232956
config: i386-randconfig-x002-201837 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed
On 14/09/18 17:28, Jeffrey Hugo wrote:
> The type of a cache might not be specified by architectural mechanisms (ie
> system registers), but its type might be specified in the PPTT. In this
> case, we should populate the type of the cache, rather than leave it
> undefined.
>
> This fixes the
> Looks good to me. Thanks! :)
>
> Acked-by: Jae Hyun Yoo
Does that mean I need to revert "[PATCH i2c-next v6] i2c: aspeed: Handle
master/slave combined irq events properly" in i2c/for-next? And apply
this to i2c/for-current?
(and please quote only relevat parts of a message when replying)
Hi Peter,
On 9/17/2018 1:23 AM, Peter Zijlstra wrote:
> On Tue, Sep 11, 2018 at 10:14:33AM -0700, Reinette Chatre wrote:
>> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
>> index 53c500f0ca79..c04dc666425c 100644
>> --- a/include/linux/perf_event.h
>> +++
On 09/17, Rafael J. Wysocki wrote:
>
> On Fri, Sep 14, 2018 at 6:21 PM Oleg Nesterov wrote:
> >
> > > > Since you are adding the notifier anyway, what about designing it to
> > > > make
> > > > the thread wait on _PREPARE until the notifier kicks it again on exit
> > > > fron
On 9/16/2018 4:00 PM, Kees Cook wrote:
> On Sun, Sep 16, 2018 at 11:49 AM, Casey Schaufler
> wrote:
>> On 9/15/2018 5:30 PM, Kees Cook wrote:
>>> To prepare for having a third type of LSM ("shared blob"), this implements
>>> dynamic handling of LSM ordering. The visible change here is that the
On Tue, Aug 14, 2018 at 07:50:14PM +0300, Leonard Crestez wrote:
> On imx7d the pcie-phy power domain is turned off in suspend and this can
> make the system hang on resume when attempting any read from PCI.
>
> Fix this by adding PM_SLEEP support to the imx6 pci driver. This is
> currently only
Please don't do this.
The hard part of fixing this is not what you are doing, changing the
return type.
The hard part is fixing each and every function to actually return
values which are members of the netdev_tx_t enumeration.
Please fix each and every function properly.
Thank you.
Signed-off-by: Charles Keepax
---
Documentation/devicetree/bindings/mfd/arizona.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt
b/Documentation/devicetree/bindings/mfd/arizona.txt
index 9b62831fdf3e..148ef621a5e5 100644
Commit 786534b92f3c introduced a regression that caused listxattr to
return the POSIX ACL attribute names even though sysfs doesn't support
POSIX ACLs. This happens because simple_xattr_list checks for NULL
i_acl / i_default_acl, but inode_init_always initializes those fields to
ACL_NOT_CACHED
1 - 100 of 2078 matches
Mail list logo
