On Thu, May 17, 2018 at 12:34 PM, Tejun Heo wrote:
> For historical reasons, the worker attach/detach functions don't
> currently manage worker->pool and the callers are manually and
> inconsistently updating it.
>
> This patch moves worker->pool updates into the worker attach/detach
> functions.
On Wed, Apr 25, 2018 at 1:05 PM, Tetsuo Handa
wrote:
> OK. Patch is in vfs.git#for-next as 4fb48871409e2fcd.
>
> #syz fix: restore cond_resched() in shrink_dcache_parent()
I see there is another patch titled "fs/dcache.c: re-add
cond_resched() in shrink_dcache_parent()" points to this bug:
http:/
On Fri, May 18, 2018 at 10:05:51PM +0200, Helge Deller wrote:
> This patch seems to fix the dma issues I faced on my 32bit B160L parisc box.
>
> So it leaves only one open issue on parisc:
> Now every 32 bit parisc system is unnecessarily non-coherent.
I diagree with those comments, let me resend
On Fri, May 18, 2018 at 03:31:38PM -0700, Andrew Morton wrote:
> On Fri, 18 May 2018 10:50:25 -0700 Matthew Wilcox wrote:
>
> > If the radix tree underlying the IDR happens to be full and we attempt
> > to remove an id which is larger than any id in the IDR, we will call
> > __radix_tree_delete()
Commit-ID: 7dec80ccbe310fb7e225bf21c48c672bb780ce7b
Gitweb: https://git.kernel.org/tip/7dec80ccbe310fb7e225bf21c48c672bb780ce7b
Author: Josh Poimboeuf
AuthorDate: Fri, 18 May 2018 15:10:34 -0500
Committer: Ingo Molnar
CommitDate: Sat, 19 May 2018 08:10:04 +0200
objtool: Detect RIP-rela
Commit-ID: 4f74d72aa7067e75af92fbab077e6d7d0210be66
Gitweb: https://git.kernel.org/tip/4f74d72aa7067e75af92fbab077e6d7d0210be66
Author: Mark Rutland
AuthorDate: Fri, 18 May 2018 16:08:41 +0200
Committer: Ingo Molnar
CommitDate: Sat, 19 May 2018 08:07:56 +0200
efi/libstub/arm64: Handle
This is a fix from reviewing the code, but it looks like it might be
able to lead to an Oops. It affects 32bit systems.
The KVM_MEMORY_ENCRYPT_REG_REGION ioctl uses a u64 for range->addr and
range->size but the high 32 bits would be truncated away on a 32 bit
system. This is harmless but it's al
> Subject: Re: [RFC PATCH 05/09] Change RDMA send to regonize page offset
> in the 1st page
>
> On 5/17/2018 5:22 PM, Long Li wrote:
> > From: Long Li
>
> There's a typo "recognize" in the patch title
>
>
> > When doing RDMA send, the offset needs to be checked as data may start
> > in an offs
On Fri, 18 May 2018, Christoph Hellwig wrote:
> > This implementation of arch_setup_pdev_archdata() differs from the
> > powerpc one, in that this one avoids clobbering a device dma mask
> > which has already been initialized.
>
> I think your implementation should move into the generic impleme
usuarios de webmail
Tenga en cuenta que el 95% de sus correos electrónicos recibidos después de
actualizar el servidor webmail recientemente en nuestra base de datos se han
suspendido. Reciba su mensaje regularmente. Nuestro personal técnico
actualizará su cuenta dentro de los tres días hábiles
Hi Tycho,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc5]
[cannot apply to next-20180517]
[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
The ALWAYS_SYNC flag is currently honored by the usb-storage driver but not UAS
and is required to work around devices that become unstable upon being
queried for cache. This code is taken straight from:
drivers/usb/storage/scsiglue.c:284
Signed-off-by: Alexander Kappner
---
drivers/usb/storage/
The "G-Drive" (sold by G-Technology) external USB 3.0 drive
hangs on write access under UAS and usb-storage:
[ 136.079121] sd 15:0:0:0: [sdi] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 136.079144] sd 15:0:0:0: [sdi] tag#0 Sense Key : Illegal Request [current]
[ 136.079152]
v2 of this patch implements the FL_ALWAYS_SYNC flag in the UAS driver, and then
adds the flag as quirks for the device at issue. This allows the G-Drive to work
under both UAS and usb-storage.
Alexander Kappner (2):
[usb-storage] Add support for FL_ALWAYS_SYNC flag in the UAS driver
[usb-stora
Hi Nadav,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on v4.17-rc5 next-20180517]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
h
On Fri, May 18, 2018 at 9:12 PM Linus Torvalds <
torva...@linux-foundation.org> wrote:
> (So we'd still have a "sb_maxbytes" that filesystems would fill in, but it
> would only be used as a "fill in inode value for regular files for this
> superblock").
Actually, maybe we could just make rw_verif
On Fri, May 18, 2018 at 8:43 PM Al Viro wrote:
> Not quite. The things like
> if (unlikely(*ppos >= inode->i_sb->s_maxbytes))
> return 0;
> iov_iter_truncate(iter, inode->i_sb->s_maxbytes);
> protect most of the regular files (see mm/filemap.c). And for device
On Fri, May 18, 2018 at 08:33:37PM -0700, Linus Torvalds wrote:
> On Fri, May 18, 2018 at 8:20 PM Linus Torvalds <
> torva...@linux-foundation.org> wrote:
>
> > I'd *much* rather just set FMODE_UNSIGNED_OFFSET for /proc/vmcore _only_,
> > rather than open up all proc files to issues with 4G+ offse
On Fri, May 18, 2018 at 8:20 PM Linus Torvalds <
torva...@linux-foundation.org> wrote:
> I'd *much* rather just set FMODE_UNSIGNED_OFFSET for /proc/vmcore _only_,
> rather than open up all proc files to issues with 4G+ offsets.
Hmm. I was going to point to the s_maxbytes check in rw_verify_area()
On Fri, May 18, 2018 at 8:15 PM Vasily Gorbik wrote:
> Commit be83bbf80682 ("mmap: introduce sane default mmap limits")
> introduced "pgoff" limits checks for mmap, considering fs max file size
> as upper limit, which made it impossible to mmap /proc/vmcore file
> contents above 2Gb (/proc/vmcore
Procfs does not set max file size (s_maxbytes) and ends up with default
value of
MAX_NON_LFS ((1UL<<31) - 1)
Commit be83bbf80682 ("mmap: introduce sane default mmap limits")
introduced "pgoff" limits checks for mmap, considering fs max file size
as upper limit, which made it impossible to mmap
Greetings,
be83bbf80682 "mmap: introduce sane default mmap limits" introduced a
problem with mapping /proc/vmcore if it is bigger than 2gb. This
breaks s390 kernel zfcpdump. But it should be a general problem.
Please consider the following one-liner fix, if it makes sense.
Vasily Gorbik (1):
p
On Fri, May 18, 2018 at 8:45 AM, Vlad Buslov wrote:
> Underlying implementation of action map has changed and doesn't require
> disabling bh anymore. Replace all action idr spinlock usage with regular
> calls that do not disable bh.
Please explain explicitly why it is not required, don't let peop
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit.
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Will Deac
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit.
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Will Deac
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Will Deaco
Remove the dance around old and new attributes. Just don't modify the
previous breakpoint at all until we have verified everything.
Reported-by: Linus Torvalds
Original-patch-by: Andy Lutomirski
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc:
All architectures have implemented it, we can now remove the poor weak
version.
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Will Deacon
Cc: Mark Rutland
Cc: Max Filippov
Cc: Chris Zan
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Will Deaco
We soon won't be able to rely on bp->attr anymore to get the new
type of the modifying breakpoint because the new attributes are going
to be copied only once we successfully modified the breakpoint slot.
This will fix the current misdesigned layout where the new attr are
copied to the modifying br
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit.
Original-patch-by: Andy Lutomirski
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
We can't pass the breakpoint directly on arch_check_bp_in_kernelspace()
anymore because its architecture internal datas (struct arch_hw_breakpoint)
are not yet filled by the time we call the function, and most
implementation need this backend to be up to date. So arrange the
function to take the pr
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Will Deaco
This field seem to be unused, perhaps a leftover from old code...
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Will Deacon
Cc: Mark Rutland
Cc: Max Filippov
Cc: Chris Zankel
Cc: Catal
arch_validate_hwbkpt_settings() mixes up attribute check and commit into
a single code entity. Therefore the validation may return an error due to
incorrect atributes while still leaving halfway modified architecture
breakpoint data.
This is harmless when we deal with a new breakpoint but it becom
Changes since v1:
- Avoid arch code duplication between check and commit. Use a temporary
struct arch_hw_breakpoint to fill up arch data on the fly
(Mark Rutland)
- Start with a default weak version of hw_breakpoint_arch_parse() that
architectures override one by one (Peter Zijlstra, Andy
On Tue, May 15, 2018 at 09:58:03PM -0700, Andy Lutomirski wrote:
>
>
> > On May 15, 2018, at 8:11 PM, Frederic Weisbecker
> > wrote:
> >
> >> On Wed, May 09, 2018 at 11:17:03AM +0200, Peter Zijlstra wrote:
> >>> On Sun, May 06, 2018 at 09:19:54PM +0200, Frederic Weisbecker wrote:
> >>> arch/ar
2018-05-19 3:25 GMT+01:00 Dmitry Safonov <0x7f454...@gmail.com>:
>> Here is the function:
>> 00400842 :
>> 400842: 53 push %rbx
>> 400843: 55 push %rbp
>> 400844: 41 54 push %r12
>> 400846: 41
On Sat, May 19, 2018 at 09:12:30AM +0800, Jason Wang wrote:
> On 2018年05月18日 22:33, Tiwei Bie wrote:
> > On Fri, May 18, 2018 at 09:17:05PM +0800, Jason Wang wrote:
> > > On 2018年05月18日 19:29, Tiwei Bie wrote:
> > > > On Thu, May 17, 2018 at 08:01:52PM +0800, Jason Wang wrote:
> > > > > On 2018年05月
On Fri, May 18, 2018 at 11:36:23AM -0700, Joel Fernandes wrote:
> Hi,
>
> I was thinking about tasks-RCU and why its needed. Since preempt-RCU allows
> tasks to be preempted in read-sections, can we not just reuse that mechanism
> for the trampolines since we track all preempted tasks so we would
2018-05-19 3:22 GMT+01:00 Dmitry Safonov :
> On Fri, 2018-05-18 at 19:05 -0700, Andy Lutomirski wrote:
>> > On May 18, 2018, at 4:10 PM, Dmitry Safonov <0x7f454...@gmail.com>
>> > cpu family: 6
>> > model: 142
>> > model name: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
>> > But I usua
On Fri, 2018-05-18 at 19:05 -0700, Andy Lutomirski wrote:
> > On May 18, 2018, at 4:10 PM, Dmitry Safonov <0x7f454...@gmail.com>
> > cpu family: 6
> > model: 142
> > model name: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
> > But I usually test kernels in VM. So, I use virt-manager as
> On May 18, 2018, at 4:10 PM, Dmitry Safonov <0x7f454...@gmail.com> wrote:
> Hi Andy,
> 2018-05-18 23:03 GMT+01:00 Andy Lutomirski :
>>> On Thu, May 17, 2018 at 4:40 PM Dmitry Safonov wrote:
>>> Some selftests are failing, but the same way as before the patch
>>> (ITOW, it's not regression):
>>
On Fri, 2018-05-18 at 23:29 +0300, Andy Shevchenko wrote:
> On Fri, May 18, 2018 at 12:10 PM, Joe Perches wrote:
> > On Fri, 2018-05-18 at 10:42 +0200, Petr Mladek wrote:
> > > On Thu 2018-05-10 08:45:29, Joe Perches wrote:
> > > [0.00] libftrace: ftrace: allocating 40753 entries in 160 pa
Hi Taniya,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.17-rc5 next-20180517]
[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/linux/
FROM MR NELSON CAPPER
MANAGER AUDIT AND ACCOUNTING DEPARTMENT
KOREA DEVELOPMENT BANK (K.D.B) LONDON U.K
PLEASE READ CAREFULLY
This message might meet you in utmost surprise. However, it’s just my
urgent need for foreign partner that made me to contact you for this
transaction.
I am Mr, Nelson C
On 5/18/2018 1:58 PM, Long Li wrote:
Subject: Re: [RFC PATCH 09/09] Introduce cache=rdma moutning option
On Fri, May 18, 2018 at 12:00 PM, Long Li via samba-technical wrote:
Subject: Re: [RFC PATCH 09/09] Introduce cache=rdma moutning option
On Thu, May 17, 2018 at 05:22:14PM -0700, Long Li w
pdev_nr and rhport can be controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1 vulnerability.
This issue was detected with the help of Smatch:
drivers/usb/usbip/vhci_sysfs.c:238 detach_store() warn: potential spectre issue
'vhcis'
drivers/usb/usbip/vhci_sys
On 2018年05月18日 22:33, Tiwei Bie wrote:
On Fri, May 18, 2018 at 09:17:05PM +0800, Jason Wang wrote:
On 2018年05月18日 19:29, Tiwei Bie wrote:
On Thu, May 17, 2018 at 08:01:52PM +0800, Jason Wang wrote:
On 2018年05月16日 22:33, Tiwei Bie wrote:
On Wed, May 16, 2018 at 10:05:44PM +0800, Jason Wang w
On 5/17/2018 5:22 PM, Long Li wrote:
From: Long Li
There's a typo "recognize" in the patch title
When doing RDMA send, the offset needs to be checked as data may start in an
offset
in the 1st page.
Doesn't this patch alter the generic smb2pdu.c code too? I think this
should note "any" se
On 2018年05月18日 22:46, Michael S. Tsirkin wrote:
On Fri, May 18, 2018 at 10:11:54PM +0800, Jason Wang wrote:
On 2018年05月18日 22:06, Michael S. Tsirkin wrote:
On Fri, May 18, 2018 at 10:00:31PM +0800, Jason Wang wrote:
On 2018年05月18日 21:26, Jason Wang wrote:
On 2018年05月18日 21:13, Michael S. T
Host1x's CDMA can't access the command buffers if IOMMU and Host1x
firewall are enabled in the kernels config because firewall doesn't map
the copied buffer into IOVA space. Fix this by skipping IOMMU
initialization if firewall is enabled as firewall merges sparse cmdbufs
into a single contiguous b
On 5/17/2018 11:03 PM, Long Li wrote:
Subject: Re: [RFC PATCH 00/09] Implement direct user I/O interfaces for
RDMA
On 5/17/2018 8:22 PM, Long Li wrote:
From: Long Li
This patchset implements direct user I/O through RDMA.
In normal code path (even with cache=none), CIFS copies I/O data from
u
On 5/17/2018 5:22 PM, Long Li wrote:
From: Long Li
When using direct pages from user space, there is no need to allocate pages.
Just ping those user pages for RDMA.
Did you mean "pin" those user pages? If so, where does that pinning
occur, it's not in this patch.
Perhaps this should just sa
Apologies for not having more in the way of diagnostic info.
Every one of the 4.17-rcX series has hung during boot at the point where
"acpid" starts up. Beginning with -rc5, the boot actually proceeds to
completion after an "uncomfortably" long delay.
Attempting to run the X11 server results in
On 19.05.2018 02:52, Dmitry Osipenko wrote:
> Map firewall-copied buffers into Host1x's IOVA space, otherwise Host1x
> CDMA can't access the command buffers and all submitted jobs fail if IOMMU
> and Host1x firewall are enabled in the kernels config.
>
> Signed-off-by: Dmitry Osipenko
> ---
> dr
In 4.17-rc, commit 03ea6d6e9e1f ("usb: dwc2: Enable power down")
caused the HiKey board to not correctly handle switching between
usb-gadget and usb-host mode.
Unplugging the OTG port would result in:
[ 42.240973] dwc2 f72c.usb: dwc2_restore_host_registers: no host
registers to restore
[
On 05/17/2018 06:01 PM, Doug Anderson wrote:
> On Thu, May 17, 2018 at 5:16 PM, David Collins
> wrote:
>> On 05/17/2018 02:22 PM, Doug Anderson wrote:
>>> On Fri, May 11, 2018 at 7:28 PM, David Collins
>>> wrote:
+- qcom,regulator-initial-microvolt
+ Usage: optional; VRM re
On Freitag, 18. Mai 2018 09:14:36 CEST Maxime Ripard wrote:
> On Mon, May 14, 2018 at 10:36:08PM +0200, Paul Kocialkowski wrote:
> > > > + backlight: backlight {
> > > > + compatible = "pwm-backlight";
> > > > + pwms = <&pwm 0 5 PWM_POLARITY_INVERTED>;
> > > >
On Fri, May 18, 2018 at 11:23:08PM +0300, Roman Kagan wrote:
> On Fri, May 18, 2018 at 10:50:25AM -0700, Matthew Wilcox wrote:
> > It'd be nice if you cc'd the person who wrote the code you're patching.
> > You'd get a response a lot quicker than waiting until I happened to
> > notice the email in
On Fri, May 18, 2018 at 03:31:38PM -0700, Andrew Morton wrote:
> On Fri, 18 May 2018 10:50:25 -0700 Matthew Wilcox wrote:
> > If the radix tree underlying the IDR happens to be full and we attempt
> > to remove an id which is larger than any id in the IDR, we will call
> > __radix_tree_delete() wi
Geschäfts vorschlag
Ich habe ein Geschäft von $ 65.400.000.00 Million (fünfundsechzig Millionen,
vierhunderttausend US-Dollar), die er in unserer Bank hinterlegt hat und gerade
lügt, nicht beansprucht zu teilen, sollten Sie interessiert sein. Sollten Sie
interessiert sein, wenden Sie sich bitt
Hi Tycho,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc5]
[cannot apply to next-20180517]
[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
On Fri, 18 May 2018 18:27:39 +0200
Oleg Nesterov wrote:
> insn_get_length() has the side-effect of processing the entire instruction
> but only if it was decoded successfully, otherwise insn_complete() can fail
> and in this case we need to just return an error without warning.
>
This looks goo
Map firewall-copied buffers into Host1x's IOVA space, otherwise Host1x
CDMA can't access the command buffers and all submitted jobs fail if IOMMU
and Host1x firewall are enabled in the kernels config.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/host1x/job.c | 58 ++
The mm-of-the-moment snapshot 2018-05-18-16-44 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
2018-05-18 23:41 GMT+01:00 Dmitry Safonov <0x7f454...@gmail.com>:
> What I did - was running x86 selftests and ssh'ing at the same moment.
> Will try it again if it'll fire by any chance.
No, I've tried a couple of times (after reboot as it's ONCE), but it looks
hard to reproduce by hands without
Hi Linus,
DELL_WMI had a lingering "select DELL_SMBIOS" leading to possible
misconfiguration. This removes the last of the "select DELL_SMBIOS"
lines in the Kconfig.
Obviously this has been an unacceptable sequence of failures. I will be
adding some contextual fuzz testing for this Kconfig to try
2018-05-19 0:16 GMT+01:00 Dmitry Safonov <0x7f454...@gmail.com>:
> 2018-05-19 0:10 GMT+01:00 Dmitry Safonov <0x7f454...@gmail.com>:
>> Sure.
>> I'm on Intel actually:
>> cpu family: 6
>> model: 142
>> model name: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
>>
>> But I usually test kern
Hello,
syzbot found the following crash on:
HEAD commit:1f7455c3912d tcp: tcp_rack_reo_wnd() can be static
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=171a133780
kernel config: https://syzkaller.appspot.com/x/.config?x=b632d8e2c2ab2c1
dashboard lin
On Fri, May 18, 2018 at 10:56:18PM +, Trent Piepho wrote:
>
> I feel like "fix" might overstate the result a bit.
>
> This ends up taking a full second to make each UUID. Having gone to
> great effort to make an iMX25 complete userspace startup in 250 ms, a
> full second, per UUID, in early
2018-05-19 0:10 GMT+01:00 Dmitry Safonov <0x7f454...@gmail.com>:
> Sure.
> I'm on Intel actually:
> cpu family: 6
> model: 142
> model name: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
>
> But I usually test kernels in VM. So, I use virt-manager as it's
> easier to manage
> multiple VM
On Friday, May 18, 2018 11:21:14 PM CEST Andy Shevchenko wrote:
> On Sat, May 19, 2018 at 12:09 AM, Janusz Krzysztofik
>
> wrote:
> > + gpiod_rdy = devm_gpiod_get_optional(&pdev->dev, "rdy", GPIOD_IN);
> > + if (!IS_ERR_OR_NULL(gpiod_rdy)) {
>
> So, is it optional or not at the end?
Hi Andy,
2018-05-18 23:03 GMT+01:00 Andy Lutomirski :
> On Thu, May 17, 2018 at 4:40 PM Dmitry Safonov wrote:
>> Some selftests are failing, but the same way as before the patch
>> (ITOW, it's not regression):
>> [root@localhost self]# grep FAIL out
>> [FAIL] Reg 1 mismatch: requested 0x0; got 0
From: Stephen Boyd
The following changes since commit c964cfc612b59910593fa10ee1c2673db274c9c7:
Merge tag 'meson-clk-fixes-4.17-1' of https://github.com/BayLibre/clk-meson
into clk-fixes (2018-05-01 14:44:16 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/lin
The last few months have been busy and I've not been ontop of my
upstream testing as well as I'd like, but today I did manage to chase
down an issue I've been seeing since 4.17-rc1 on the HiKey board,
which was causing emmc corruption and stopping the board from booting.
Symptoms usually looked li
On Sat, May 19, 2018 at 12:09:46AM +0300, Andy Shevchenko wrote:
> On Fri, May 18, 2018 at 4:59 AM, Joel Fernandes wrote:
> > From: "Joel Fernandes (Google)"
> >
> > In this patch we introduce a test module for simulating a long atomic
> > section in the kernel which the preemptoff or irqsoff tra
On Thu, 2018-05-17 at 22:32 -0400, Theodore Y. Ts'o wrote:
> On Fri, May 18, 2018 at 01:27:03AM +, Trent Piepho wrote:
> > I've hit this on an embedded system. mke2fs hangs trying to format a
> > persistent writable filesystem, which is where the random seed to
> > initialize the kernel entrop
Sedat,
Thanks for the report. We have a fix ready in
https://bugs.llvm.org/show_bug.cgi?id=37512. Can you report what
version of clang you were using and if earlier versions of clang have
this issue?
Thanks,
~Nick
The current hugetlbfs maintainer has not been active for more than
a few years. I have been been active in this area for more than
two years and plan to remain active in the foreseeable future.
Also, update the hugetlbfs entry to include linux-mm mail list and
additional hugetlbfs related files.
This macro doesn't work, because it hides a local variable inside of the
macro to hold the version and that variable name is called 'ver' and
'version' sometimes.
Let's change this to be more explicit. Introduce three macros for the
major, minor, and step of the version, and require callers to pas
On Fri, May 18, 2018 at 08:55:47AM +0200, Ingo Molnar wrote:
>
> * Jiri Slaby wrote:
>
> > Josh pointed out, that there is no way a frame can be after user regs.
> > So remove the last unwind and the check.
> >
> > Signed-off-by: Jiri Slaby
> > Cc: Thomas Gleixner
> > Cc: Ingo Molnar
> > Cc:
Hi Thomas, Tariq,
2018-02-20 18:11 GMT+00:00 Thomas Gleixner :
> On Tue, 20 Feb 2018, Tariq Toukan wrote:
>
>> Hi Thomas,
>>
>> We started seeing new issues in our net-device daily regression tests.
>> They are related to patch [1] introduced in kernel 4.15-rc1.
>>
>> We frequently see a warning i
On Mon Mar 26 18, Jarkko Sakkinen wrote:
In order to make struct tpm_buf the first class object for constructing TPM
commands, migrate tpm2_get_tpm_pt() to use it.
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Jerry Snitselaar
---
drivers/char/tpm/tpm2-cmd.c | 63 +---
On Mon Mar 26 18, Jarkko Sakkinen wrote:
In order to make struct tpm_buf the first class object for constructing TPM
commands, migrate tpm2_probe() to use it.
Signed-off-by: Jarkko Sakkinen
Acked-by: Jay Freyensee
Reviewed-by: Jerry Snitselaar
---
drivers/char/tpm/tpm2-cmd.c | 37
Hi Florian,
I love your patch! Yet something to improve:
[auto build test ERROR on net-next/master]
url:
https://github.com/0day-ci/linux/commits/Florian-Fainelli/net-ethernet-ti-Allow-most-drivers-with-COMPILE_TEST/20180519-043005
config: sparc64-allyesconfig (attached as .config)
compiler:
On Fri, 18 May 2018 10:50:25 -0700 Matthew Wilcox wrote:
> If the radix tree underlying the IDR happens to be full and we attempt
> to remove an id which is larger than any id in the IDR, we will call
> __radix_tree_delete() with an uninitialised 'slot' pointer, at which
> point anything could ha
From: Bjorn Helgaas
Host bridge drivers do not use the portdrv interfaces (struct pcie_device,
struct pcie_port_service_driver, pcie_port_service_register(), etc), and
they should not select CONFIG_PCIEPORTBUS.
If users need the portdrv services, they can select CONFIG_PCIEPORTBUS just
like all
On Mon Mar 26 18, Jarkko Sakkinen wrote:
In order to make struct tpm_buf the first class object for constructing TPM
commands, migrate tpm2_shutdown() to use it. In addition, removed the klog
entry when tpm_transmit_cmd() fails because tpm_tansmit_cmd() already
prints an error message.
Signed-of
The reuseport_bpf_numa test case fails there's no numa support. The
test shouldn't fail if there's no support it should be skipped.
Fixes: 3c2c3c16aaf6 ("reuseport, bpf: add test case for bpf_get_numa_node_id")
Signed-off-by: Anders Roxell
---
tools/testing/selftests/net/reuseport_bpf_numa.c |
On 05/18/2018 11:06 AM, Shuah Khan wrote:
On 05/18/2018 07:47 AM, Greg Kroah-Hartman wrote:
On Thu, May 17, 2018 at 03:16:28PM -0500, Gustavo A. R. Silva wrote:
pdev_nr and rhport can be controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1 vulnerability
On Thu, May 17, 2018 at 05:16:13PM -0700, David Collins wrote:
> On 05/17/2018 02:22 PM, Doug Anderson wrote:
> > On Fri, May 11, 2018 at 7:28 PM, David Collins
> > wrote:
> >> +- qcom,regulator-initial-microvolt
> >> + Usage: optional; VRM regulators only
> >> + Value type:
> >
On Fri, May 11, 2018 at 01:38:18PM +0300, Radu Pirea wrote:
> This mfd driver is just a wrapper over atmel_serial driver and
> spi-at91-usart driver. Selection of one of the drivers is based on a
> property from device tree. If the property is not specified, the default
> driver is atmel_serial.
>
On 05/17/2018 04:26 AM, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Signed-off-by: Oleksandr Andrushchenko
> ---
> drivers/xen/grant-table.c | 49 +++
> include/xen/grant_table.h | 7 ++
> 2 files changed, 56 insertions(+)
>
> diff
On 05/18/2018 05:08 PM, Dan Williams wrote:
Oh I see now. Just to double check, then something like the following would
be broken too, because is basically the same as the code above, and well, it
doesn't make much sense to store the value returned by macro
array_index_nospec into x, correct?:
On Fri, May 18, 2018 at 3:01 PM, Gustavo A. R. Silva
wrote:
>
>
> On 05/18/2018 04:45 PM, Dan Williams wrote:
>>
>> On Fri, May 18, 2018 at 2:27 PM, Gustavo A. R. Silva
>> wrote:
>>>
>>>
>>>
>>> On 05/18/2018 03:44 PM, Gustavo A. R. Silva wrote:
>>>
>>>
>>>
>>
>> Oops, it seem
On Fri, May 18, 2018 at 05:24:04PM +0200, Fabrice Gasnier wrote:
> This removes build warning when COMPILE_TEST=y and MFD_STM32_TIMERS=n
> in drivers/pwm/pwm-stm32.c. In function 'stm32_pwm_capture' 'raw_prd' and
> 'raw_dty' may be used uninitialized in this function
> [-Wmaybe-uninitialized]
>
>
From: Corneliu Doban
The SDHCI_QUIRK2_HOST_OFF_CARD_ON is needed for the driver to
properly reset the host controller (reset all) on initialization
after exiting deep sleep.
Signed-off-by: Corneliu Doban
Signed-off-by: Scott Branden
Reviewed-by: Ray Jui
Reviewed-by: Srinath Mannam
---
drive
From: Srinath Mannam
Remove hard coded mmc cap 1.8v from platform data as it is board specific.
The 1.8v DDR mmc caps can be enabled using DTS property for those
boards that support it.
Fixes: b17b4ab8ce38 ("mmc: sdhci-iproc: define MMC caps in platform data")
Signed-off-by: Srinath Mannam
Sign
From: Corneliu Doban
When the host controller accepts only 32bit writes, the value of the
16bit TRANSFER_MODE register, that has the same 32bit address as the
16bit COMMAND register, needs to be saved and it will be written
in a 32bit write together with the command as this will trigger the
host
1 - 100 of 1187 matches
Mail list logo
