在 2018/5/24 15:45, Rafael J. Wysocki 写道:
On Thu, May 24, 2018 at 8:43 AM, Kevin Wangtao
wrote:
consider such situation, current user_policy.min is 100,
current user_policy.max is 120, in cpufreq_set_policy,
other driver may update policy.min to 120, policy.max to
130. After th
On Thu, May 24, 2018 at 4:14 AM, Sergey Senozhatsky
wrote:
>> First, we should ask what we expect from this feature.
>
> Yeah. Can't really comment on this, it's up to Tetsuo and Dmitry to
> decide. So far I've seen slightly different requirements/expectations.
The root problem is that it's not p
On 26 May 2018 at 01:08, Prakhya, Sai Praneeth
wrote:
>> > Changes from V3 to V4:
>> > --
>> > 1. As suggested by Peter, use completions instead of flush_work() as the
>> > former is cheaper
>> > 2. Call efi_delete_dummy_variable() from efisubsys_init(). Sorry! Ard,
>> > wa
Looks fine:
Reviewed-by: Christoph Hellwig
On 2018/5/26 3:49, Jaegeuk Kim wrote:
> The fstrim gathers huge number of large discard commands, and tries to issue
> without IO awareness, which results in long user-perceive IO latencies on
> READ, WRITE, and FLUSH in UFS. We've observed some of commands take several
> seconds due to long discar
On Sat, May 26, 2018 at 11:16:42AM +0800, Liu Bo wrote:
> > +/*
> > + * Returns pointer to the specified byte @offset within @radix, allocating
> > it if
> > + * necessary - newly allocated slots are always zeroed out:
> > + */
> > +void *__genradix_ptr_alloc(struct __genradix *radix, size_t offse
On Fri, May 25, 2018 at 08:10:47PM -0700, John Stultz wrote:
> This patch is a partial revert of commit
> abd7d0972a19 ("arm64: dts: hikey: Enable HS200 mode on eMMC")
>
> which has been causing eMMC corruption on my HiKey board.
>
> Symptoms usually looked like:
>
> mmc_host mmc0: Bus speed (sl
Hi Mauro,
On Thu, 17 May 2018 07:06:57 -0300 Mauro Carvalho Chehab
wrote:
>
> What do you use in order to check it? Maybe we could have some git
> hook running such check, in order to prevent merging patches without
> the right SOBs.
I run the script below on the range of new commits each time
On 5/24/18 6:12 AM, Vitaly Andrianov wrote:
This series adds dts nodes for Keystone2 hw_rng driver
Vitaly Andrianov (3):
ARM: dts: k2hk: add dts node for k2hk hw_rng driver
ARM: dts: k2l: add dts node for k2l hw_rng driver
ARM: dts: k2e: add dts node for k2e hw_rng driver
Looks good.
Dear Linux folks,
Building the configuration created with `make tinyconfig` on the Power 8
system IBM S822LC with Ubuntu 18.04 fails with the error below.
```
$ git describe --dirty
v4.17-rc6-296-gbc2dbc5420e8
$ git log --oneline -1
bc2dbc5420e8 (HEAD -> master, origin/master, origin/HEAD) Me
Hi Alexandre,
On Tue, 15 May 2018 09:15:23 +0200 Alexandre Torgue
wrote:
>
> On 05/14/2018 11:22 PM, Stephen Rothwell wrote:
> >
> > Commit
> >
> >949a0c0dec85 ("ARM: dts: stm32: add USB Host (USBH) support to
> > stm32mp157c")
> >
> > is missing a Signed-off-by from its committer.
>
>
On Fri 25 May 09:08 PDT 2018, Arnd Bergmann wrote:
> Without CONFIG_OF_RESERVED_MEM, gcc sees that the global cmd_db_header
> variable is never initialized, and through code optimization concludes
> that a lot of other code cannot possibly work after that:
>
> drivers/soc/qcom/cmd-db.c: In functi
On 5/25/18 9:50 PM, Stephen Rothwell wrote:
> Hi Jens,
>
> Commits
>
> 287a63ebbe7c ("nvme: mark the result argument to nvme_complete_async_event
> volatile")
> 750dde4472e4 ("nvme-pci: simplify nvme_cqe_valid")
> d1f06f4ae041 ("nvme-pci: move ->cq_vector == -1 check outside of ->q_lock")
Hi Jens,
Commits
287a63ebbe7c ("nvme: mark the result argument to nvme_complete_async_event
volatile")
750dde4472e4 ("nvme-pci: simplify nvme_cqe_valid")
d1f06f4ae041 ("nvme-pci: move ->cq_vector == -1 check outside of ->q_lock")
1ab0cd6966fc ("nvme-pci: split the nvme queue lock into su
On Sat, 26 May 2018 11:31:35 +0800 kbuild test robot wrote:
> Hi Andrey,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on mmotm/master]
> [cannot apply to v4.17-rc6]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the sys
Hi all,
Commits
116aeb887371 ("iw_cxgb4: provide detailed provider-specific CM_ID
information")
to
0252f73334f9 ("IB/qib: Fix DMA api warning with debug kernel")
are missing a Signed-off-by from their committer. I presume they have
been rebased?
--
Cheers,
Stephen Rothwell
pgpeYCv9hbe7
Hi Andrey,
I love your patch! Yet something to improve:
[auto build test ERROR on mmotm/master]
[cannot apply to v4.17-rc6]
[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/commits/Andrey-Ryabinin/mm-kas
Hi Kent,
(Add all ML to cc this time.)
On Wed, May 23, 2018 at 9:18 AM, Kent Overstreet
wrote:
> Very simple radix tree implementation that supports storing arbitrary
> size entries, up to PAGE_SIZE - upcoming patches will convert existing
> flex_array users to genradixes. The new genradix code
This patch is a partial revert of commit
abd7d0972a19 ("arm64: dts: hikey: Enable HS200 mode on eMMC")
which has been causing eMMC corruption on my HiKey board.
Symptoms usually looked like:
mmc_host mmc0: Bus speed (slot 0) = 2480Hz (slot req 40Hz, actual
40HZ div = 31)
...
mmc_hos
Hi Souptick,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on v4.17-rc6]
[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/commi
On 05/16/2018 04:50 PM, Alan Tull wrote:
> Move Documentation/fpga/fpga-region.txt to
> driver-api/fpga/fpga-region.rst. Including:
> - Add it to driver-api/fpga/index.rst
> - Formatting changes to build cleanly as ReST documentation
> - Some rewrites for better flow as a ReST doc such as movin
On 05/16/2018 04:50 PM, Alan Tull wrote:
> Move Documentation/fpga/fpga-mgr.txt to driver-api/fpga/fpga-mgr.rst
> and:
> - Add to driver-api/fpga/index.rst
> - Format changes so documentation builds cleanly.
> - Minor rewrites that make the doc flow better as ReST documentation.
>- Such as m
On 2018/5/26 0:19, Alexei Starovoitov wrote:
> On Fri, May 25, 2018 at 06:17:57PM +0800, YueHaibing wrote:
>> gcc-7.3.0 report following err:
>>
>> HOSTCC net/bpfilter/main.o
>> In file included from net/bpfilter/main.c:9:0:
>> ./include/uapi/linux/bpf.h:12:10: fatal error: linux/bpf_common.h: N
On 05/16/2018 04:50 PM, Alan Tull wrote:
> Start of moving Documentation/fpga/*.txt to driver-api, including:
> - Add new directory driver-api/fpga
> - Add new file driver-api/fpga/index.rst
> - Add driver-api/fpga to driver-api/index.rst
> - Move Documentation/fpga/overview.txt to driver-api/f
On 05/16/2018 11:16 PM, Masahiro Yamada wrote:
> Add a document for the macro language introduced to Kconfig.
>
> The motivation of this work is to move the compiler option tests to
> Kconfig from Makefile. A number of kernel features require the
> compiler support. Enabling such features blindl
Make sure that MX51_PAD_GPIO1_1 does not remain configure as
ALT0/SD1_WP (it is out of reset). This is needed because of external
pull-up resistor attached to that pad that, when left unchanged, will
drive SD1_WP high preventing eSDHC1/eMMC from working correctly.
To fix that add a pinmux configur
There is no point in testing .set_mmss versus .set_mmss64 as there are both
taking the exact same argument (truncated for set_mmss though).
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-test.c | 19 ++-
1 file changed, 2 insertions(+), 17 deletions(-)
diff --git a/drivers
On 2018/5/25 22:55, Jason Gunthorpe wrote:
> On Fri, May 25, 2018 at 01:54:31PM +0800, Wei Hu (Xavier) wrote:
>>
>> On 2018/5/25 5:31, Jason Gunthorpe wrote:
static const struct hnae3_client_ops hns_roce_hw_v2_ops = {
.init_instance = hns_roce_hw_v2_init_instance,
.uninit_in
On 2018/5/26 9:04, Jaegeuk Kim wrote:
> For non-atomic files, this patch adds an option to give nobarrier which
> doesn't issue flush commands to the device.
>
> Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
Thanks,
syzbot is reporting NULL pointer dereference [1] which is caused by
race condition between ioctl(loop_fd, LOOP_CLR_FD, 0) versus
ioctl(other_loop_fd, LOOP_SET_FD, loop_fd) due to traversing other
loop devices without holding corresponding locks.
syzbot is also reporting circular locking dependency
Mark cros_ec_keyb has wake enabled by default. If we see a MKBP event
related to keyboard, call pm_wakeup_event() to make sure wakeup
triggers are accounted to keyb during suspend resume path.
Signed-off-by: Ravi Chandra Sadineni
---
V2: Marked the ckdev as wake enabled instead of input devices.
Some of the INT340X devices may not have hysteresis defined in the ACPI
definition. In that case reading trip hysteresis results in error. This
spams logs of user space utilities.
In this case instead of returning error, just return hysteresis as 0,
which is correct as there is no hysteresis defin
Hello Rajendra,
On 05/25/2018 03:01 AM, Rajendra Nayak wrote:
> The RPMh powerdomain driver aggregates the corner votes from various
s/powerdomain/power domain/
This applies to all instances in this patch. "Power domain" seems to be
the preferred spelling in the kernel.
> consumers for the AR
For non-atomic files, this patch adds an option to give nobarrier which
doesn't issue flush commands to the device.
Signed-off-by: Jaegeuk Kim
---
Documentation/filesystems/f2fs.txt | 16 +---
fs/f2fs/f2fs.h | 1 +
fs/f2fs/file.c | 2 +-
fs/f
For non-migration IO, we will keep order of data/node blocks' submitting
as allocation sequence by sorting IOs in per log io_list list, but for
migration IO, it could be out-of-order.
In LFS mode, we should keep all IOs including migration IO be ordered,
so that this patch fixes to add an addition
syzbot is reporting NULL pointer dereference at snapshot_write() [1].
This is because data->handle is zero-cleared by ioctl(SNAPSHOT_FREE).
Fix this by checking data_of(data->handle) != NULL before using it.
[1]
https://syzkaller.appspot.com/bug?id=828a3c71bd344a6de8b6a31233d51a72099f27fd
Signed
syzbot is reporting stalls at n_tty_receive_char_special() [1]. This is
because comparison is not working as expected since ldata->read_head can
change at any moment. Mitigate this by explicitly masking with buffer size
when checking condition for "while" loops.
[1]
https://syzkaller.appspot.com/
syzbot is reporting stalls at __process_echoes() [1]. This is because
since ldata->echo_commit < ldata->echo_tail becomes true for some reason,
the discard loop is serving as almost infinite loop. This patch tries to
avoid falling into ldata->echo_commit < ldata->echo_tail situation by
making acces
On 2018/5/26 3:49, Jaegeuk Kim wrote:
> The fstrim gathers huge number of large discard commands, and tries to issue
> without IO awareness, which results in long user-perceive IO latencies on
> READ, WRITE, and FLUSH in UFS. We've observed some of commands take several
> seconds due to long discar
On 2018/5/18 14:21, Sahitya Tummala wrote:
> f2fs_ioc_shutdown() ioctl gets stuck in the below path
> when issued with F2FS_GOING_DOWN_FULLSYNC option.
>
> __switch_to+0x90/0xc4
> percpu_down_write+0x8c/0xc0
> freeze_super+0xec/0x1e4
> freeze_bdev+0xc4/0xcc
> f2fs_ioctl+0xc0c/0x1ce0
> f2fs_compat_
On Fri, May 25, 2018 at 06:22:04PM +0200, Christoph Hellwig wrote:
> Looks fine to me:
>
> Reviewed-by: Christoph Hellwig
>
> Al, can you pick this up?
Done
On Fri, May 25, 2018 at 2:32 PM Arnd Bergmann wrote:
> Several subsystems depend on INFINIBAND_ADDR_TRANS, which in turn depends
> on INFINIBAND. However, when with CONFIG_INIFIBAND=m, this leads to a
> link error when another driver using it is built-in. The
> INFINIBAND_ADDR_TRANS dependency is
On Thu, May 24, 2018 at 11:10:14PM +0800, Liu, Changcheng wrote:
> Hi all,
> I have one confusion about workqueue_struct:
> 1) Why struct workqueue_struct is defined in C file instead of
> header file?
To prevent all other code poking in its guts?
> I'm trying to print
Hi Johannes,
I tried your previous memdelay patches before this new set was posted
and results were promising for predicting when Android system is close
to OOM. I'm definitely going to try this one after I backport it to
4.9.
On Mon, May 7, 2018 at 2:01 PM, Johannes Weiner wrote:
> Hi,
>
> I pre
On 5/25/18 4:37 PM, Arnd Bergmann wrote:
+#ifdef CONFIG_ACPI
static int emac_sgmii_irq_clear(struct emac_adapter *adpt, u8 irq_bits)
{
struct emac_sgmii *phy = &adpt->phy;
@@ -288,6 +289,7 @@ static struct sgmii_ops qdf2400_ops = {
.link_change = emac_sgmii_common_link_change,
Hi,
With the latest tip.git perf, if you run
$ perf record -a -o - sleep 2 | perf inject -b -i - | perf buildid-list -i -
SEGFAULT in perf inject:
free_dup_event (oe=0x55d25b88, oe=0x55d25b88,
event=0x3030310931303031) at util/ordered-events.c:86
86 oe->cur_alloc_size -= event->header.si
On Wed, May 23, 2018 at 09:19:49PM +0200, Christoph Hellwig wrote:
> Hi all,
>
> this series adds support for the IOCB_CMD_POLL operation to poll for the
> readyness of file descriptors using the aio subsystem. The API is based
> on patches that existed in RHAS2.1 and RHEL3, which means it alread
Hi Thomas,
This is a pull request for the series that I sent earlier.
The series aims to switch vfs timestamps to use
struct timespec64. Currently vfs uses struct timespec,
which is not y2038 safe.
The flag patch applies cleanly. I've not seen the timestamps
update logic change often. The series
On Fri, May 25, 2018 at 08:43:39PM +0900, Namhyung Kim wrote:
> Hi Joel,
>
> On Wed, May 23, 2018 at 06:21:55PM -0700, Joel Fernandes wrote:
> > From: "Joel Fernandes (Google)"
> >
> > This patch detaches the preemptirq tracepoints from the tracers and
> > keeps it separate.
> >
> > Advantages:
On Fri, 2018-05-25 at 23:36 +0200, Arnd Bergmann wrote:
> With CONFIG_TLS=m and MLX5_CORE_EN=y, we get a link failure:
>
> drivers/net/ethernet/mellanox/mlx5/core/en_accel/tls_rxtx.o: In
> function `mlx5e_tls_handle_ooo':
> tls_rxtx.c:(.text+0x24c): undefined reference to `tls_get_record'
> driver
[forgot to add netdev]
On 05/25/2018 04:14 PM, Randy Dunlap wrote:
> On 05/25/2018 02:52 PM, a...@linux-foundation.org wrote:
>> The mm-of-the-moment snapshot 2018-05-25-14-52 has been uploaded to
>>
>>http://www.ozlabs.org/~akpm/mmotm/
>>
>> mmotm-readme.txt says
>>
>> README for mm-of-the-mo
On 05/25/2018 02:52 PM, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2018-05-25-14-52 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 m
The tail of a queue is supposed to be pointing to the next available slot
in a queue. In this implementation the tail is incremented before it is
used and as such points to the last used element, something that has the
immense advantage of centralizing tail management at a single location
and elim
> > Changes from V3 to V4:
> > --
> > 1. As suggested by Peter, use completions instead of flush_work() as the
> > former is cheaper
> > 2. Call efi_delete_dummy_variable() from efisubsys_init(). Sorry! Ard,
> > wasn't able to find a better alternative to keep this change lo
Arnd, Olof,
I'm a bit late for this very small PR, as I had to extend the expiration
date for my GPG signature key.
Two small DT changes that have no functional impact.
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are
On Friday, May 18, 2018 11:09:52 PM CEST Janusz Krzysztofik wrote:
> Now as the Amstrad Delta board provides GPIO lookup tables, switch from
> GPIO numbers to GPIO descriptors and use the table to locate required
> GPIO pins.
>
> Declare static variables for storing GPIO descriptors and replace
>
On Fri, May 25, 2018 at 2:06 PM H. Peter Anvin wrote:
> On 05/25/18 13:36, Nick Desaulniers wrote:
> > On Fri, May 25, 2018 at 10:56 AM wrote:
> >> You need the extern inline in the .h file and the out-of-line .S file
> > I don't see how you can specify to the linker from assembly source that
> >
On 2018-05-25 15:10, Bjorn Helgaas wrote:
On Fri, May 25, 2018 at 09:30:59AM -0400, Sinan Kaya wrote:
On 5/24/2018 2:35 PM, Bjorn Helgaas wrote:
> That sounds like a reasonable idea, and it is definitely another can
> of worms. I looked briefly at some of the .shutdown() cases:
should we throw
Hello Rajendra,
On 05/25/2018 03:01 AM, Rajendra Nayak wrote:
> On Qualcomm platforms, an OPP node needs to describe an
s/Qualcomm/Qualcomm Technologies, Inc./
> additional level/corner value that is then communicated to
> a remote microprocessor by the CPU, which then takes some
> actions (lik
On 5/25/18 5:00 PM, Ross Zwisler wrote:
From: "Darrick J. Wong"
Remove __bdev_dax_supported and change to bdev_dax_supported that takes a
bdev parameter. This enables multi-device filesystems like xfs to check
that a dax device can work for the particular filesystem. Once that's
in place, act
On Fri, May 25, 2018 at 06:09:13PM +0200, Arnd Bergmann wrote:
> The patch that enabled these had no useful changelog that explains
> why it is done, and it causes a build warning:
>
> WARNING: unmet direct dependencies detected for STM32_DMA
> Depends on [n]: DMADEVICES [=n] && (ARCH_STM32 [=y]
On Mon, Apr 16, 2018 at 10:40:04AM +0800, Baolin Wang wrote:
> Add the rtc enable clock for watchdog controller to make it work well.
>
> Signed-off-by: Baolin Wang
APplied with "sprd: whale2:" added to the patch subject.
-Olof
On Mon, Apr 16, 2018 at 10:40:03AM +0800, Baolin Wang wrote:
> This patch adds device nodes to enable one GPIO controller located on
> digital chip, 2 EIC (external interrupt controller) controllers loacted
> on PMIC and digital chip for Spreadtrum SC9860 platform.
>
> Moreover this patch adds 3 G
On Thu, May 24, 2018 at 08:20:15PM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> On top of previous pull request.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit 83cb529b2ef4f3446e60e75522d76fdaaea4724c:
>
> ARM: dts: exynos: Update x and y properties for mms114 touchscr
On Thu, May 24, 2018 at 08:20:16PM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> On top of previous pull request.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit 8dd6203f32f20cb83469eb859efded9e403b3e9f:
>
> arm64: dts: exynos: Add mem-2-mem Scaler devices (2018-05-13 11
Now as the Amstrad Delta board provides GPIO lookup tables, switch from
GPIO numbers to GPIO descriptors and use the table to locate required
GPIO pins.
Declare static variables for storing GPIO descriptors and replace
gpio_ functions with their gpiod_ equivalents. Return -EPROBE_DEFER
if the GPIO
On 26 May 2018 at 00:05, Sai Praneeth Prakhya
wrote:
> From: Sai Praneeth
>
> Problem statement:
> --
> Presently, efi_runtime_services() silently switch %cr3 from swapper_pgd
> to efi_pgd. As a consequence, kernel code that runs in efi_pgd (e.g.,
> perf code via an NMI) will have
On Fri, 25 May 2018, Andrew Morton wrote:
> > > > --- a/mm/hugetlb.c
> > > > +++ b/mm/hugetlb.c
> > > > @@ -2006,8 +2006,10 @@ struct page *alloc_huge_page(struct
> > > > vm_area_struct *vma,
> > > > * code of zero indicates a reservation exists (no change).
> > > > */
> > > >
On Fri, May 25, 2018 at 09:30:59AM -0400, Sinan Kaya wrote:
> On 5/24/2018 2:35 PM, Bjorn Helgaas wrote:
> > That sounds like a reasonable idea, and it is definitely another can
> > of worms. I looked briefly at some of the .shutdown() cases:
>
> should we throw it into 4.18 and see what happens?
It appears that a "#define DEBUG" was left in on the recent patch
landed for the Qualcomm DWC3 glue driver. Let's remove it.
Fixes: a4333c3a6ba9 ("usb: dwc3: Add Qualcomm DWC3 glue driver")
Signed-off-by: Douglas Anderson
---
drivers/usb/dwc3/dwc3-qcom.c | 1 -
1 file changed, 1 deletion(-)
d
From: Sai Praneeth
Invoking efi_runtime_services() through efi_rts_wq (efi runtime
services workqueue) means all accesses to efi_runtime_services() should
be done after efi_rts_wq has been created. efi_delete_dummy_variable()
calls set_variable(), hence efi_delete_dummy_variable() should be calle
On 05/22/2018 03:18 AM, Ulf Magnusson wrote:
> On Mon, May 21, 2018 at 5:47 AM, Randy Dunlap wrote:
>> On 05/20/2018 08:33 PM, Ulf Magnusson wrote:
>>> On Mon, May 21, 2018 at 4:45 AM, Randy Dunlap wrote:
On 05/19/2018 09:47 PM, Ulf Magnusson wrote:
> On Sun, May 20, 2018 at 6:03 AM, Ran
The USB Host Controller driver 'ohci-at91.c' reads a Special Function
Register - OHCI Interrupt Configuration Register (AT91_SFR_OHCIICR)
for bits SUSPEND_A/B/C. These bits are defined in sama5d2 alone, so
sfr register mapping is done with compatible string "atmel,sama5d2-sfr".
This gives a kernel
From: Sai Praneeth
Problem statement:
--
Presently, efi_runtime_services() silently switch %cr3 from swapper_pgd
to efi_pgd. As a consequence, kernel code that runs in efi_pgd (e.g.,
perf code via an NMI) will have incorrect user space mappings[1]. This
could lead to otherwise une
From: Sai Praneeth
Presently, when a user process requests the kernel to execute any
efi_runtime_service(), kernel switches the page directory (%cr3) from
swapper_pgd to efi_pgd. Other subsystems in the kernel aren't aware of
this switch and they might think, user space is still valid (i.e. the
u
From: Sai Praneeth
When a process requests the kernel to execute any efi_runtime_service(),
the requested efi_runtime_service (represented as an identifier) and its
arguments are packed into a struct named efi_runtime_work and queued
onto work queue named efi_rts_wq. The caller then waits until t
From: "Darrick J. Wong"
Remove __bdev_dax_supported and change to bdev_dax_supported that takes a
bdev parameter. This enables multi-device filesystems like xfs to check
that a dax device can work for the particular filesystem. Once that's
in place, actually fix all the parts of XFS where we ne
This stub was added so that we could use dm-snap with DM_TYPE_DAX_BIO_BASED
mode devices. That mode and the transition issues associated with it no
longer exist, so we can remove this dead code.
Signed-off-by: Ross Zwisler
---
drivers/md/dm-snap.c | 8
1 file changed, 8 deletions(-)
d
No code changes from v1. Just CCing the xfs mailing list & adding one
Reviewed-by from Darrick.
---
This series fixes a few issues that I found with DM's handling of DAX
devices. Here are some of the issues I found:
* We can create a dm-stripe or dm-linear device which is made up of an
fsd
From: Dave Jiang
The function return values are confusing with the way the function is
named. We expect a true or false return value but it actually returns
0/-errno. This makes the code very confusing. Changing the return values
to return a bool where if DAX is supported then return true and no
> On May 25, 2018, at 3:14 AM, Yafang Shao wrote:
>
> skb->len is meaningless to user.
> data length could be more helpful, with which we can easily filter out
> the packet without payload.
>
> Signed-off-by: Yafang Shao
Acked-by: Song Liu
> ---
> include/trace/events/tcp.h | 8
>
This stub was added so that we could use dm-error with
DM_TYPE_DAX_BIO_BASED mode devices. That mode and the transition issues
associated with it no longer exist, so we can remove this dead code.
Signed-off-by: Ross Zwisler
---
drivers/md/dm-target.c | 7 ---
1 file changed, 7 deletions(-)
Currently device_supports_dax() just checks to see if the QUEUE_FLAG_DAX
flag is set on the device's request queue to decide whether or not the
device supports filesystem DAX. This is insufficient because there are
devices like PMEM namespaces in raw mode which have QUEUE_FLAG_DAX set but
which do
The DM_TYPE_DAX_BIO_BASED dm_queue_mode was introduced to prevent DM
devices that could possibly support DAX from transitioning into DM devices
that cannot support DAX.
For example, the following transition will currently fail:
dm-linear: [fsdax pmem][fsdax pmem] => [fsdax pmem][fsdax raw]
Currently the code in dm_dax_direct_access() only checks whether the target
type has a direct_access() operation defined, not whether the underlying
block devices all support DAX. This latter property can be seen by looking
at whether we set the QUEUE_FLAG_DAX request queue flag when creating the
On Fri, May 25, 2018 at 11:09:46PM +0200, Arnd Bergmann wrote:
> Changing from UNIVERSAL_DEV_PM_OPS to SIMPLE_DEV_PM_OPS caused a harmless
> warning in configurations without CONFIG_PM_SLEEP:
>
> drivers/i2c/busses/i2c-i801.c:1723:12: error: 'i801_resume' defined but not
> used [-Werror=unused-fu
> On May 25, 2018, at 2:33 PM, Arnd Bergmann wrote:
>
> The stack_map_get_build_id_offset() function is too long for gcc to track
> whether 'work' may or may not be initialized at the end of it, leading
> to a false-positive warning:
>
> kernel/bpf/stackmap.c: In function 'stack_map_get_build_i
of_graph_get_next_endpoint() returns device_node with refcnt increased,
but these is no of_node_put() for it.
The patch adds one on error and normal paths.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/media/i2c/tc358743.c | 5
> On May 25, 2018, at 2:33 PM, Arnd Bergmann wrote:
>
> gcc warns about a noreturn function possibly returning in
> some configurations:
>
> kernel/bpf/btf.c: In function 'env_type_is_resolve_sink':
> kernel/bpf/btf.c:729:1: error: control reaches end of non-void function
> [-Werror=return-ty
The mm-of-the-moment snapshot 2018-05-25-14-52 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
The procfs interface changes caused one warning in afs for
a now unused function:
fs/afs/proc.c:818:12: error: 'afs_proc_stats_show' defined but not used
[-Werror=unused-function]
static int afs_proc_stats_show(struct seq_file *m, void *v)
This can be avoided by using an inline function instead
Currently we just check the "CAPID0" register to see whether the CPU
can recover from machine checks.
But there are also some special SKUs which do not have all advanced
RAS features, but do enable machine check recovery for use with NVDIMMs.
Add a check for any of bits {8:5} in the "CAPID5" regi
Some injection testing resulted in the following console log:
mce: [Hardware Error]: CPU 22: Machine Check Exception: f Bank 1:
bd8000100134
mce: [Hardware Error]: RIP 10: {pmem_do_bvec+0x11d/0x330
[nd_pmem]}
mce: [Hardware Error]: TSC c51a63035d52 ADDR 3234bc4000 MISC 88
mce: [Hardware
Since we added support to add recovery from some errors inside the kernel in:
commit b2f9d678e28c ("x86/mce: Check for faults tagged in EXTABLE_CLASS_FAULT
exception table entries")
we have done a less than stellar job at reporting the cause of recoverable
machine checks that occur in other part
The first two just get better error messages when we refuse to recover
from an error that the h/w says is recoverable because the error occurred
in a non-recoverable part of the kernel.
The third improves identification of Skylake SKUs that support
recovery.
Tony Luck (3):
x86/mce: Improve erro
On Fri, May 25, 2018 at 1:39 PM, Vlad Buslov wrote:
>
> On Thu 24 May 2018 at 23:34, Cong Wang wrote:
>> On Mon, May 14, 2018 at 7:27 AM, Vlad Buslov wrote:
>>> Currently, all netlink protocol handlers for updating rules, actions and
>>> qdiscs are protected with single global rtnl lock which re
On Fri, May 25, 2018 at 11:29:59PM +0200, Arnd Bergmann wrote:
> Several subsystems depend on INFINIBAND_ADDR_TRANS, which in turn depends
> on INFINIBAND. However, when with CONFIG_INIFIBAND=m, this leads to a
> link error when another driver using it is built-in. The
> INFINIBAND_ADDR_TRANS depen
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/wireless/marvell/mwifiex/cfg80211.c | 4
drivers/net/wireless/marvell/mwifiex/scan.c | 1 +
2 files changed, 5 insertions(+)
d
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 62d18ecfa64137349fac9c5817784fbd48b54f48
commit: 9533b292a7acc62c294ebcbd9e1f9f9d52adb10b IB: remove redundant
INFINIBAND kconfig dependencies
date: 2 weeks ago
config: x86_64-randconfig-x003-05251014 (att
A couple of functions in this file are only used when building with
ACPI enabled, leading to a build warning on most architectures:
drivers/net/ethernet/qualcomm/emac/emac-sgmii.c:284:25: error: 'qdf2400_ops'
defined but not used [-Werror=unused-variable]
static struct sgmii_ops qdf2400_ops = {
1 - 100 of 800 matches
Mail list logo
