Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1620900

Re: [PATCH] drivers/dax: Avoiding potential deadlock

From Dan Williams <dan.j.williams@intel.com>
Newsgroups linux.kernel
Subject Re: [PATCH] drivers/dax: Avoiding potential deadlock
Date 2017-04-11 07:00 +0200
Message-ID <tuW4h-2jb-3@gated-at.bofh.it> (permalink)
References <tuVUB-2g1-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Mon, Apr 10, 2017 at 9:45 PM, Pushkar Jambhlekar
<pushkar.iit@gmail.com> wrote:
> dax_dev_huge_fault returning without releasing lock. Making code change to avoid this situation
>
> Signed-off-by: Pushkar Jambhlekar <pushkar.iit@gmail.com>
> ---
>  drivers/dax/dax.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dax/dax.c b/drivers/dax/dax.c
> index 0d1ca24..fd9c4db 100644
> --- a/drivers/dax/dax.c
> +++ b/drivers/dax/dax.c
> @@ -590,7 +590,7 @@ static int dax_dev_huge_fault(struct vm_fault *vmf,
>                 rc = __dax_dev_pud_fault(dax_dev, vmf);
>                 break;
>         default:
> -               return VM_FAULT_FALLBACK;
> +               rc = VM_FAULT_FALLBACK;

Thanks for the fix! Luckily we never take that branch, but we should
fix it so we don't trip over it in some future where there are more
fault sizes than pte, pmd, and pud. However, it should be setting rc
to VM_FAULT_SIGBUS on an unknown / unsupported fault size.

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH] drivers/dax: Avoiding potential deadlock Pushkar Jambhlekar <pushkar.iit@gmail.com> - 2017-04-11 06:50 +0200
  Re: [PATCH] drivers/dax: Avoiding potential deadlock Dan Williams <dan.j.williams@intel.com> - 2017-04-11 07:00 +0200
    Re: [PATCH] drivers/dax: Avoiding potential deadlock Pushkar Jambhlekar <pushkar.iit@gmail.com> - 2017-04-11 07:30 +0200

csiph-web