2018-03-30 21:40 GMT+09:00 Mark Wielaard :
> On Thu, 2018-03-29 at 11:01 -0700, Laura Abbott wrote:
>> I'm still mostly looking for feedback whether
>> this would be acceptable for merging or if we should just persue a
>> --build-id-salt in binutils.
>
> Personally I would go with this approach. It
>From Ching Huang
Update driver version to v1.40.00.06-20180504
Signed-off-by: Ching Huang
---
diff --git a/drivers/scsi/arcmsr/arcmsr.h b/drivers/scsi/arcmsr/arcmsr.h
index 62eeef5..eb39623 100755
--- a/drivers/scsi/arcmsr/arcmsr.h
+++ b/drivers/scsi/arcmsr/arcmsr.h
@@ -49,7 +49,7 @@ struct d
Michael Schmitz - 07.05.18, 04:40:
> Al,
>
> I don't think there is USB sticks with affs on them as yet. There
> isn't even USB host controller support for Amiga hardware (yet).
>
> Last I tried USB on m68k (Atari, 060 accelerator) the desktop
> experience was such that I'd rather not repeat that
Hi,
On Sun, May 06, 2018 at 11:48:59PM +0200, Paul Kocialkowski wrote:
> This adds timings for the RGB666 variant of the Innolux AT070TN90 panel,
> as found on the Ainol AW1 tablet.
>
> The panel also supports RGB888 output. When RGB666 mode is used instead,
> the two extra lanes per component ar
On 06.05.2018 02:46, Randy Dunlap wrote:
> On 05/05/2018 04:22 PM, kbuild test robot wrote:
>> Hi Maciej,
>>
>> FYI, the error/warning still remains.
> Hi M. Robot,
>
> I am cc-ing dri-de...@lists.freedesktop.org so that they are aware of the
> multiple times that you have posted this kbuild error
Hi Daniel,
On Fri, May 4, 2018 at 6:30 PM, Daniel Wagner wrote:
> From: Daniel Wagner
>
> Commit 40f70c03e33a ("serial: sh-sci: add locking to console write
> function to avoid SMP lockup") copied the strategy to avoid locking
> problems in conjuncture with the console from the UART8250
> driver
Hi,
On Sun, May 06, 2018 at 11:49:01PM +0200, Paul Kocialkowski wrote:
> This adds support for the Ainol AW1, an A20-based 7" tablet from Ainol.
>
> The following board-specific features are supported:
> * LCD panel
> * Backlight
> * USB OTG
> * Buttons
> * Touchscreen (doesn't work without non-f
On Mon, May 07, 2018 at 10:35:46AM +0530, Viresh Kumar wrote:
> On 05-05-18, 23:50, Nathan Chancellor wrote:
> > Fixes the following W=1 warning: variable ‘intf_id’ set but
> > not used [-Wunused-but-set-variable]
> >
> > Signed-off-by: Nathan Chancellor
> > ---
> > drivers/staging/greybus/svc.c
James,
On Tue, May 01, 2018 at 06:46:11PM +0100, James Morse wrote:
> Hi Akashi,
>
> On 25/04/18 07:26, AKASHI Takahiro wrote:
> > This patch provides kexec_file_ops for "Image"-format kernel. In this
> > implementation, a binary is always loaded with a fixed offset identified
> > in text_offset
On Sat, Apr 28, 2018 at 01:29:17PM +0800, Wang YanQing wrote:
> On Sat, Apr 28, 2018 at 01:33:15AM +0200, Daniel Borkmann wrote:
> > On 04/28/2018 12:48 AM, Alexei Starovoitov wrote:
> > > On Thu, Apr 26, 2018 at 05:57:49PM +0800, Wang YanQing wrote:
> > >> All the testcases for BPF_PROG_TYPE_PERF_
On 06/05/18 17:28, Jiri Olsa wrote:
> On Sat, May 05, 2018 at 08:43:11PM -0700, Andi Kleen wrote:
>> Jiri Olsa writes:
>>
>> Please fix this quickly, PT is currently totally non functional in Linus
>> mainline.
>
> attached.. Kan, could you please test it wrt your latest changes?
>
> thanks,
> j
On 05/04/2018 12:44 PM, Sebastian Andrzej Siewior wrote:
> This patch reverts commit c7f26ccfb2c3 ("mm/vmstat.c: fix
> vmstat_update() preemption BUG").
> Steven saw a "using smp_processor_id() in preemptible" message and
> added a preempt_disable() section around it to keep it quiet. This is
> not
On Fri, May 04, 2018 at 11:52:59PM +0200, Giulio Benetti wrote:
> Hi Maxime!
>
> Il 04/05/2018 10:06, Maxime Ripard ha scritto:
> > Hi,
> >
> > On Wed, May 02, 2018 at 06:41:34PM +0200, Giulio Benetti wrote:
> > > > > You don't have to handcode the fragments anymore with the new syntax,
> > > > >
On 2018-05-06 12:59:19 [+0200], Mike Galbraith wrote:
> On Sun, 2018-05-06 at 12:26 +0200, Thomas Gleixner wrote:
> > On Fri, 4 May 2018, Sebastian Andrzej Siewior wrote:
> >
> > > From: Mike Galbraith
> > >
> > > Shrug. Lots of hobbyists have a beast in their basement, right?
> >
> > This har
On Mon, 7 May 2018 12:40:39 +0900
Masahiro Yamada wrote:
> 2018-05-03 21:20 GMT+09:00 Abhishek Sahu :
> > commit 2c8f8afa7f92 ("mtd: nand: add generic helpers to check,
> > match, maximize ECC settings") provides generic helpers which
> > drivers can use for setting up ECC parameters.
> >
> > Sin
I believe the flush_cache_all() after scu_enable() is to "Ensure that
the data accessed by CPU0 before the SCU was initialised is visible
to the other CPUs." as commented in scu_enable(). So flush_cache_all()
here is a duplication of the one in scu_enable(), remove it.
Signed-off-by: Jisheng Zhang
On Thu, 3 May 2018 14:21:28 +1200
Chris Packham wrote:
> marvell_nfc_wait_op() expects the delay to be expressed in milliseconds
> but nand_sdr_timings uses picoseconds. Use PSEC_TO_MSEC when passing
> tPROG_max to marvell_nfc_wait_op().
>
> Fixes: 02f26ecf8c772 ("mtd: nand: add reworked Marvel
I believe the flush_cache_all() after scu_enable() is to "Ensure that
the data accessed by CPU0 before the SCU was initialised is visible
to the other CPUs." as commented in scu_enable(). So flush_cache_all()
here is a duplication of the one in scu_enable(), remove it.
Signed-off-by: Jisheng Zhang
On Sun, May 6, 2018 at 3:07 PM, Luciano Coelho wrote:
> On Sun, 2018-05-06 at 14:46 +0200, Sedat Dilek wrote:
>> Hi Luca,
>>
>> I hope I catched the correct MLs (not sure if linux-firmware has a
>> ML,
>> I did not found any in the MAINTAINERS file).
>>
>> I have seen that in the WHENCE file there
On Mon, May 07, 2018 at 02:04:38PM +0800, Chunyan Zhang wrote:
> Hi Daniel,
>
> On 7 May 2018 at 13:51, Daniel Lezcano wrote:
> > On Thu, May 03, 2018 at 08:27:32PM +0800, Chunyan Zhang wrote:
> >> SPRD arch doesn't select SPRD_TIMER, so this config would not
> >> appear even if ARCH_SPRD is set
On Mon, 7 May 2018 11:02:10 +0800
"dongbo (E)" wrote:
> From: Dong Bo
>
> Update vfio_add_group_dev description to match the current API.
>
> Signed-off-by: Dong Bo
> ---
> Documentation/vfio.txt | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/vfi
It is a preparatory patch so next we will make prctl_set_mm_map
to accept struct prctl_mm_map as an argument and the only
thing prctl_set_mm_map will do is to setup new memory map,
not handling any other operations.
CC: Jonathan de Boyne Pollard
CC: Andrey Vagin
CC: Andrew Morton
CC: Michael Ke
Once we make it to accept struct prctl_mm_map as an argument it will
be possible to reuse this functionallity for the rest of PR_SET_MM_x
operations. Here we simply allocate struct prctl_mm_map in a caller
and provide it downstairs.
CC: Jonathan de Boyne Pollard
CC: Andrey Vagin
CC: Andrew Morto
Hi! Yesterday I've been pointed out that we unfortunatelly can't
drop off PR_SET_MM_x operations. So here is a series which bring
them back but instead of plain revert I tried to simplify the
code and make it as minimum as possible.
WARN: the series is compile-tested only for a while, I wanted
to
Recently the handling of PR_SET_MM_x been removed because we wanted to
improve locking scheme over mm::arg_start,arg_end and etc. Thus to
reduce code modification the old PR_SET_MM_x operations have been
removed (since initially they've been introduced for c/r sole sake).
Before making remove I goo
On 6 May 2018 at 11:04, Arnd Bergmann wrote:
> On Fri, May 4, 2018 at 3:07 AM, Baolin Wang wrote:
>> Since struct timespec is not y2038 safe on 32bit machines, this patch
>> converts update_persistent_clock() to update_persistent_clock64() using
>> struct timespec64.
>>
>> The rtc_mips_set_time()
On 5 May 2018 at 13:54, kbuild test robot wrote:
> Hi Eric,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on slave-dma/next]
> [also build test WARNING on next-20180504]
> [cannot apply to linus/master v4.17-rc3]
> [if your patch is applied to the wrong gi
On Fri, Apr 27, 2018 at 12:02:02PM +0200, Thierry Reding wrote:
> Joerg, I've gone over the git log and header files and I see no mention
> of why the TLB flush interface isn't used for mapping. Do you recall any
> special reasons why the same shouldn't be applied for mapping? Would you
> accept an
On Mon, 2018-05-07 at 09:39 +0200, Sebastian Andrzej Siewior wrote:
> On 2018-05-06 12:59:19 [+0200], Mike Galbraith wrote:
> > On Sun, 2018-05-06 at 12:26 +0200, Thomas Gleixner wrote:
> > > On Fri, 4 May 2018, Sebastian Andrzej Siewior wrote:
> > >
> > > > From: Mike Galbraith
> > > >
> > > >
On Thu, May 03, 2018 at 10:19:52PM +0200, Uwe Kleine-König wrote:
> The rx trigger fires when data is pushed to the ldisc. This is a bit later
> than the actual receiving of data but has the nice benefit that it
> doesn't need adaption for each driver and isn't in the hot path.
>
> Similarily the
On Mon, May 07, 2018 at 12:19:01AM +0300, Dmitry Osipenko wrote:
> Probably the best variant would be to give an explicit control over syncing
> to a
> user of the IOMMU API, like for example device driver may perform multiple
> mappings / unmappings and then sync/flush in the end. I'm not sure th
On 2018/5/1 17:28, Rafael J. Wysocki wrote:
>> drivers/acpi/pci_root.c | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/drivers/acpi/pci_root.c b/drivers/acpi/pci_root.c
>> > index 6fc204a..b758ca3 100644
>> > --- a/drivers/acpi/pci_root.c
>> > +++ b/drivers/acp
On 7 May 2018 at 15:49, Daniel Lezcano wrote:
> On Mon, May 07, 2018 at 02:04:38PM +0800, Chunyan Zhang wrote:
>> Hi Daniel,
>>
>> On 7 May 2018 at 13:51, Daniel Lezcano wrote:
>> > On Thu, May 03, 2018 at 08:27:32PM +0800, Chunyan Zhang wrote:
>> >> SPRD arch doesn't select SPRD_TIMER, so this c
On Fri, May 4, 2018 at 2:55 PM, Jian-Hong Pan wrote:
> Hi,
>
> We have an ASUS X580GD (Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz) laptop
> equipped with ELAN1200 touchpad which does not work totally, but the
> external mouse works fine.
>
> We have checked the input devices by "cat /proc/bus/input/
Hi Kiran,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on backlight/for-backlight-next]
[also build test WARNING on v4.17-rc3 next-20180504]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://git
Hi Kristian,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on nf-next/master]
[also build test WARNING on v4.17-rc3 next-20180504]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0da
Masami Hiramatsu wrote:
On Sat, 05 May 2018 13:16:04 +0530
"Naveen N. Rao" wrote:
Masami Hiramatsu wrote:
> On Fri, 4 May 2018 12:06:42 -0400
> Steven Rostedt wrote:
>
>> On Sat, 5 May 2018 00:48:28 +0900
>> Masami Hiramatsu wrote:
>>
>> > > Also, when looking at the kprobe code, I was lo
On Mon, May 07, 2018 at 10:21:42AM +0300, Adrian Hunter wrote:
> On 06/05/18 17:28, Jiri Olsa wrote:
> > On Sat, May 05, 2018 at 08:43:11PM -0700, Andi Kleen wrote:
> >> Jiri Olsa writes:
> >>
> >> Please fix this quickly, PT is currently totally non functional in Linus
> >> mainline.
> >
> > att
Hi Taniya,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on clk/clk-next]
[also build test WARNING on v4.17-rc3 next-20180503]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On 05/07/2018 06:10 AM, Stephen Rothwell wrote:
> On Mon, 7 May 2018 12:09:09 +1000 Stephen Rothwell
> wrote:
>>
>> Today's linux-next merge of the tip tree got a conflict in:
>>
>> arch/x86/net/bpf_jit_comp.c
>>
>> between commit:
>>
>> e782bdcf58c5 ("bpf, x64: remove ld_abs/ld_ind")
>>
>> f
On Thu, 3 May 2018 17:50:28 +0530
Abhishek Sahu wrote:
> commit 2c8f8afa7f92 ("mtd: nand: add generic helpers to check,
> match, maximize ECC settings") provides generic helpers which
> drivers can use for setting up ECC parameters.
>
> Since same board can have different ECC strength nand chip
f_op->dedupe_file_range() gets a u64 length to dedup and returns an ssize_t
actual length deduped. This breaks badly on 32bit archs since the returned
length will be truncated and possibly overflow into the sign bit (xfs and
ocfs2 are affected, btrfs limits actual length to 16MiB).
Returning s64
Hi Al,
Please apply this is a small cleanup/fix series. It is also a prerequisite
to the overlayfs file stacking patchset.
Git tree is here:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git dedupe-cleanup
Thanks,
Miklos
---
Miklos Szeredi (3):
vfs: dedpue: return s64
vfs:
Clean up f_op->dedupe_file_range() interface.
1) Use loff_t for offsets instead of u64
2) Order the arguments the same way as {copy|clone}_file_range().
Signed-off-by: Miklos Szeredi
---
fs/btrfs/ctree.h | 4 ++--
fs/btrfs/ioctl.c | 4 ++--
fs/ocfs2/file.c| 6 +++---
fs/read_write.c
Extract vfs_dedupe_file_range_one() helper to deal with a single dedup
request.
Signed-off-by: Miklos Szeredi
---
fs/read_write.c | 89 +++--
1 file changed, 49 insertions(+), 40 deletions(-)
diff --git a/fs/read_write.c b/fs/read_write.c
inde
Hi Masami,
On 05/04/2018 07:51 PM, Ravi Bangoria wrote:
>
>>> +}
>>> +
>>> +static void sdt_increment_ref_ctr(struct trace_uprobe *tu)
>>> +{
>>> + struct uprobe_map_info *info;
>>> +
>>> + uprobe_down_write_dup_mmap();
>>> + info = uprobe_build_map_info(tu->inode->i_mapping,
>>> +
On Sun, Apr 29, 2018 at 2:22 PM, Etienne Carriere
wrote:
> This change prevents userland from referencing TEE shared memory
> outside the area initially allocated by its owner. Prior this change an
> application could not reference or access memory it did not own but
> it could reference memory no
On 04/05/2018 at 20:38, Boris Brezillon wrote:
Hi Radu,
Sorry for the late reply.
On Wed, 28 Feb 2018 13:55:01 +0200
Radu Pirea wrote:
This patch add support in spi-nor for allmost all dataflash memories
supported by old mtd_dataflash driver.
Those devices clearly use a different instructi
On 05/07/2018 09:23 AM, Wang YanQing wrote:
> On Sat, Apr 28, 2018 at 01:29:17PM +0800, Wang YanQing wrote:
>> On Sat, Apr 28, 2018 at 01:33:15AM +0200, Daniel Borkmann wrote:
>>> On 04/28/2018 12:48 AM, Alexei Starovoitov wrote:
On Thu, Apr 26, 2018 at 05:57:49PM +0800, Wang YanQing wrote:
>>
On Thu, 3 May 2018 17:50:31 +0530
Abhishek Sahu wrote:
> Currently the driver uses the ECC strength specified in DT.
> The QPIC/EBI2 NAND supports 4 or 8-bit ECC correction. The same
> kind of board can have different NAND parts so use the ECC
> strength from device parameters if it is not speci
Hi Nicolas,
On Mon, 7 May 2018 10:23:56 +0200
Nicolas Ferre wrote:
> On 04/05/2018 at 20:38, Boris Brezillon wrote:
> > Hi Radu,
> >
> > Sorry for the late reply.
> >
> > On Wed, 28 Feb 2018 13:55:01 +0200
> > Radu Pirea wrote:
> >
> >> This patch add support in spi-nor for allmost all dat
[Al, can you please review the vfs affecting patches? ]
Up till now overlayfs didn't stack regular file operations. Instead, when
a file was opened on an overlay, the file from one of the underlying layers
would be opened and any file operations performed would directly go to the
underlying file
This is needed by overlayfs to be able to copy up a file from a read-only
lower layer to a writable layer when being mapped shared. When copying up,
overlayfs takes VFS locks that would violate locking order when nested
inside mmap_sem.
Add a new f_op->pre_mmap method, which is called before taki
Signed-off-by: Miklos Szeredi
---
fs/overlayfs/super.c | 4
1 file changed, 4 insertions(+)
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index e8551c97de51..ad6a5baf226b 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -97,6 +97,10 @@ static struct dentry *ovl_d_r
Copy i_size of the underlying inode to the overlay inode in ovl_copyattr().
This is in preparation for stacking I/O operations on overlay files.
This patch shouldn't have any observable effect.
Remove stale comment from ovl_setattr() [spotted by Vivek Goyal].
Signed-off-by: Miklos Szeredi
---
This reverts commit cd91304e7190b4c4802f8e413ab2214b233e0260.
Overlayfs no longer relies on the vfs correct atime handling.
Signed-off-by: Miklos Szeredi
---
fs/inode.c | 21 -
fs/overlayfs/super.c | 3 ---
include/linux/dcache.h | 3 ---
3 files changed, 4 i
Since set of arguments are so similar, handle in a common helper.
Signed-off-by: Miklos Szeredi
---
fs/overlayfs/file.c | 88 +
1 file changed, 88 insertions(+)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index ce871a15e185..2ac95c9
This reverts commit 495e642939114478a5237a7d91661ba93b76f15a.
No user of "flags" argument of d_real() remain.
Signed-off-by: Miklos Szeredi
---
Documentation/filesystems/Locking | 2 +-
Documentation/filesystems/vfs.txt | 2 +-
fs/open.c | 2 +-
fs/overlayfs/super.c
This reverts commit 598e3c8f72f5b77c84d2cb26cfd936ffb3cfdbaa.
Overlayfs no longer relies on the vfs correct atime handling.
Signed-off-by: Miklos Szeredi
---
fs/inode.c | 33 ++---
fs/internal.h | 7 ---
fs/namei.c | 2 +-
include/linux/fs.
This partially reverts commit c568d68341be7030f5647def68851e469b21ca11.
Overlayfs files will now automatically get the correct locks, no need to
hack overlay support in VFS.
It is a partial revert, because it leaves the locks_inode() calls in place
and defines locks_inode() to file_inode(). We c
On Thu, 3 May 2018 17:50:30 +0530
Abhishek Sahu wrote:
> Now, nand-ecc-strength is optional. If specified in DT, then
> controller will use this ECC strength otherwise ECC strength will
> be calculated according to chip requirement and available OOB size.
>
> Signed-off-by: Abhishek Sahu
> ---
This reverts commit 4d0c5ba2ff79ef9f5188998b29fd28fcb05f3667.
We now get write access on both overlay and underlying layers so this patch
is no longer needed for correct operation.
Signed-off-by: Miklos Szeredi
---
fs/locks.c | 3 +--
fs/open.c | 15 ++-
2 files changed, 3 inserti
This reverts commit 954c736f865d6c0c68ae4263a2f3502ee7c447a3.
Overlayfs no longer relies on the vfs for checking writability of files.
Signed-off-by: Miklos Szeredi
---
fs/namespace.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/fs/namespace.c b/fs/namespace.c
index 5f
This reverts commit f3fbbb079263bd29ae592478de6808db7e708267.
Overlayfs now works correctly without adding hacks to fsnotify.
Signed-off-by: Miklos Szeredi
---
include/linux/fsnotify.h | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/include/linux/fsnotify.h b/
Hello Johan,
thanks for your feedback.
On Mon, May 07, 2018 at 10:02:52AM +0200, Johan Hovold wrote:
> On Thu, May 03, 2018 at 10:19:52PM +0200, Uwe Kleine-König wrote:
> > The rx trigger fires when data is pushed to the ldisc. This is a bit later
> > than the actual receiving of data but has the
This reverts commit 7c6893e3c9abf6a9676e060a1e35e5caca673d57.
Overlayfs no longer relies on the vfs for checking writability of files.
Signed-off-by: Miklos Szeredi
---
fs/internal.h | 2 --
fs/namespace.c | 64 +++---
fs/open.c | 4 ++
The underlying real file used by overlayfs still contains the overlay path.
This results in mnt_want_write_file() calls by the filesystem getting
freeze protection on the wrong inode (the overlayfs one instead of the real
one).
Fix by using file_inode(file)->i_sb instead of file->f_path.mnt->mnt_s
Opening regular files on overlayfs is now handled via ovl_open(). Remove
the now unused "open_flags" argument from d_op->d_real() and the d_real()
helper.
Signed-off-by: Miklos Szeredi
---
Documentation/filesystems/Locking | 3 +--
Documentation/filesystems/vfs.txt | 16
fs/ov
We can now drop description of the ro/rw inconsistency from the
documentation.
Also clarify, that now fully standard compliant behavior can be enabled
with kernel/module/mount options.
Signed-off-by: Miklos Szeredi
---
Documentation/filesystems/overlayfs.txt | 60 +--
On Sun, May 06, 2018 at 12:33:21PM -0700, Matt Turner wrote:
> On Tue, Apr 17, 2018 at 3:11 AM, James Hogan wrote:
> > Use CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING and CONFIG_OPTIMIZE_INLINING
> > instead of undefining the inline macros in the alpha specific
> > asm/compiler.h. This is to allow asm
Let overlayfs do its thing when opening a file.
This enables stacking and fixes the corner case when a file is opened for
read, modified through a writable open, and data is read from the read-only
file. After this patch the read-only open will not return stale data even
in this case.
Signed-off
On Sat, 2018-05-05 at 15:07 -0700, Greg KH wrote:
> > > > syzbot found the following crash on:
Maybe it should learn to differentiate warnings, if it's going to set
panic_on_warn :-)
I get why, but still, at least differentiating in the emails wouldn't be
bad.
> > > > kernfs: ns required in 'ie
On Sunday 06 May 2018 15:47:33 Pali Rohár wrote:
> On Thursday 01 February 2018 11:29:45 Dmitry Torokhov wrote:
> > Hi Pali,
> >
> > On Wed, Jan 24, 2018 at 11:41:21AM +0100, Pali Rohár wrote:
> > > Hi Dmitry!
> > >
> > > I'm observing a problem with internal touchpad (handled by psmouse.ko)
> >
A corner case of a corner case is when
- file opened for O_RDONLY
- which is then memory mapped SHARED
- file opened for O_WRONLY
- contents modified
- contents read back though the shared mapping
Unfortunately it looks very difficult to do anything about the established
shared map after the
dentry_open() can now just call path_open().
Signed-off-by: Miklos Szeredi
---
fs/open.c | 15 +--
1 file changed, 1 insertion(+), 14 deletions(-)
diff --git a/fs/open.c b/fs/open.c
index 244cd2ecfefd..1d4bc541c619 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -935,25 +935,12 @@ EXPORT_
Implement stacked fiemap().
Need to split inode operations for regular file (which has fiemap) and
special file (which doesn't have fiemap).
Signed-off-by: Miklos Szeredi
---
fs/overlayfs/inode.c | 29 -
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/f
Signed-off-by: Miklos Szeredi
---
fs/overlayfs/file.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index 2028f6886649..ce871a15e185 100644
--- a/fs/overlayfs/file.c
+++ b/fs/overlayfs/file.c
@@ -110,6 +110,9 @@ static int ovl_open(struct inode *
Implement FS_IOC_GETFLAGS and FS_IOC_SETFLAGS.
Signed-off-by: Miklos Szeredi
---
fs/overlayfs/file.c | 79 +
1 file changed, 79 insertions(+)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index 3a85bbfa266a..2028f6886649 100644
--- a/
Implement stacked fallocate.
Signed-off-by: Miklos Szeredi
---
fs/overlayfs/file.c | 24
1 file changed, 24 insertions(+)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index b75ee0a3655e..3a85bbfa266a 100644
--- a/fs/overlayfs/file.c
+++ b/fs/overlayfs/file.c
@
Implement file operations on a regular overlay file. The underlying file
is opened separately and cached in ->private_data.
It might be worth making an exception for such files when accounting in
nr_file to confirm to userspace expectations. We are only adding a small
overhead (248bytes for the
In the common case we can just use the real file cached in
file->private_data. There are two exceptions:
1) File has been copied up since open: in this unlikely corner case just
use a throwaway real file for the operation. If ever this becomes a
perfomance problem (very unlikely, since overlayfs
Implement stacked reading.
Signed-off-by: Miklos Szeredi
---
fs/overlayfs/file.c | 67 +
1 file changed, 67 insertions(+)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index db8778e7c37a..bbc40a14acf8 100644
--- a/fs/overlayfs/file.c
Implement stacked mmap.
Signed-off-by: Miklos Szeredi
---
fs/overlayfs/file.c | 28
1 file changed, 28 insertions(+)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index 419aa3f9967b..b75ee0a3655e 100644
--- a/fs/overlayfs/file.c
+++ b/fs/overlayfs/file.c
@@
This reverts commit 31c3a7069593b072bd57192b63b62f9a7e994e9a.
Re-add functionality dealing with i_writecount on truncate to overlayfs.
This patch shouldn't have any observable effects, since we just re-assert
the writecout that vfs_truncate() already got for us.
This is in preparation for moving
Implement stacked fsync().
Signed-off-by: Miklos Szeredi
---
fs/overlayfs/file.c | 20
1 file changed, 20 insertions(+)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index a7af56861aa5..419aa3f9967b 100644
--- a/fs/overlayfs/file.c
+++ b/fs/overlayfs/file.c
@@ -233
Implement stacked writes.
Signed-off-by: Miklos Szeredi
---
fs/overlayfs/file.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index bbc40a14acf8..a7af56861aa5 100644
--- a/fs/overlayfs/file.c
+++ b/fs/overla
This is needed by the stacked dedupe implementation in overlayfs.
Signed-off-by: Miklos Szeredi
---
fs/read_write.c| 6 +++---
include/linux/fs.h | 4
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/fs/read_write.c b/fs/read_write.c
index 023df230e2a0..08708f903fc5 100644
This is needed by the stacked ioctl implementation in overlayfs.
Signed-off-by: Miklos Szeredi
---
fs/internal.h | 1 -
fs/ioctl.c | 1 +
include/linux/fs.h | 2 ++
3 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/internal.h b/fs/internal.h
index b82725ba3054..6821cf
Stacking file operations in overlay will store an extra open file for each
overlay file opened.
The overhead is just that of "struct file" which is about 256bytes, because
overlay already pins an extra dentry and inode when the file is open, which
add up to a much larger overhead.
For fear of bre
Copy up mtime and ctime to overlay inode after times in real object are
modified. Be careful not to dirty cachelines when not necessary.
This is in preparation for moving overlay functionality out of the VFS.
This patch shouldn't have any observable effect.
Signed-off-by: Miklos Szeredi
---
f
On 2018/5/7 6:20, Alexandru Moise wrote:
When using NVME over Fabrics we may end up sending IP
packets in interrupt context, we should defer this work
to a tasklet.
[ 50.939957] WARNING: CPU: 3 PID: 0 at kernel/softirq.c:161
__local_bh_enable_ip+0x1f/0xa0
[ 50.942602] CPU: 3 PID: 0 Comm: s
On inode creation copy certain inode flags from the underlying real inode
to the overlay inode.
This is in preparation for moving overlay functionality out of the VFS.
Signed-off-by: Miklos Szeredi
---
fs/overlayfs/overlayfs.h | 7 +++
fs/overlayfs/util.c | 1 +
2 files changed, 8 inse
Currently opening an overlay file results in:
- the real file on the underlying layer being opened
- f_path being set to the overlay {mount, dentry} pair
This patch adds a new helper that allows the above to be explicitly
performed. I.e. it's the same as dentry_open(), except the underlying
in
On 2018-05-04 13:14:58 [+0200], To linux-kernel@vger.kernel.org wrote:
> From: Thomas Gleixner
>
> mce_timer is started in atomic contexts of cpu bringup. This results
> in might_sleep() warnings on RT. Convert mce_timer to a hrtimer to
> avoid this.
After an additional review I got to say that
On 25/04/18 19:22, Mauro Carvalho Chehab wrote:
> Em Wed, 25 Apr 2018 17:58:25 +0200
> Arnd Bergmann escreveu:
>
>> On Wed, Apr 25, 2018 at 5:26 PM, Christoph Hellwig
>> wrote:
>>> On Wed, Apr 25, 2018 at 01:15:18PM +0200, Arnd Bergmann wrote:
That thought had occurred to me as well. I r
On Wed, May 02, 2018 at 08:16:11AM -0500, Rob Herring wrote:
> On Wed, May 2, 2018 at 3:16 AM, Johan Hovold wrote:
> > On Tue, May 01, 2018 at 09:05:42AM -0500, Rob Herring wrote:
> >> On Thu, Apr 26, 2018 at 4:10 AM, Johan Hovold wrote:
> >> > On Wed, Apr 25, 2018 at 01:16:58PM -0500, Rob Herrin
SPRD arch doesn't select SPRD_TIMER, so this config would not
appear even if ARCH_SPRD is set but COMPILE_TEST not.
Fix the dependency of this config with SPRD arch, and set a
default value for it, also leave other choices for EXPERT.
Signed-off-by: Chunyan Zhang
---
drivers/clocksource/Kconfig
On 2018-05-07 13:36, Dan Carpenter wrote:
Hi Kiran,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on backlight/for-backlight-next]
[also build test WARNING on v4.17-rc3 next-20180504]
[if your patch is applied to the wrong git tree, please drop us a note
to hel
://github.com/0day-ci/linux/commits/linux-kernel-owner-vger-kernel-org/scsi-libsas-dynamically-allocate-and-free-ata-host/20180507-105656
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
config: x86_64-federa-25 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce
Hi Jacopo,
On Wed, Apr 25, 2018 at 01:00:13PM +0200, Jacopo Mondi wrote:
> Add device tree bindings documentation for Micron MT9T111/MT9T112 image
> sensors.
>
> Signed-off-by: Jacopo Mondi
> ---
> Documentation/devicetree/bindings/mt9t112.txt | 41
> +++
> 1 file chang
1 - 100 of 946 matches
Mail list logo
