linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 112631] Cannot open encrypted Luks root filesystem
Date: Sat, 20 Feb 2016 02:28:03 +0000	[thread overview]
Message-ID: <bug-112631-13602-f2pCFB0vFw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-112631-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=112631

Andreas Amann <andreas.amann@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andreas.amann@gmx.de

--- Comment #3 from Andreas Amann <andreas.amann@gmx.de> ---
I have the same problem. Bisection leads to the following commit:

commit 0571ba52a19e18a1c20469454231eef681cb1310
Author: Herbert Xu <herbert@gondor.apana.org.au>
Date:   Wed Dec 30 11:47:53 2015 +0800

    crypto: af_alg - Disallow bind/setkey/... after accept(2)

    [ Upstream commit c840ac6af3f8713a71b4d2363419145760bd6044 ]

    Each af_alg parent socket obtained by socket(2) corresponds to a
    tfm object once bind(2) has succeeded.  An accept(2) call on that
    parent socket creates a context which then uses the tfm object.

    Therefore as long as any child sockets created by accept(2) exist
    the parent socket must not be modified or freed.

    This patch guarantees this by using locks and a reference count
    on the parent socket.  Any attempt to modify the parent socket will
    fail with EBUSY.

    Cc: stable@vger.kernel.org
    Reported-by: Dmitry Vyukov <dvyukov@google.com>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Sasha Levin <sasha.levin@oracle.com>

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2016-02-20  2:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 20:08 [Bug 112631] New: Cannot open encrypted Luks root filesystem bugzilla-daemon
2016-02-17 20:10 ` [Bug 112631] " bugzilla-daemon
2016-02-17 20:22 ` bugzilla-daemon
2016-02-17 20:30 ` bugzilla-daemon
2016-02-19 18:52 ` bugzilla-daemon
2016-02-20  2:28 ` bugzilla-daemon [this message]
2016-02-20 10:15 ` bugzilla-daemon
2016-02-20 18:46 ` bugzilla-daemon
2016-02-21 12:00 ` bugzilla-daemon
2016-02-21 12:02 ` bugzilla-daemon
2016-02-21 12:55 ` bugzilla-daemon
2016-02-21 14:23 ` bugzilla-daemon
2016-02-21 16:12 ` bugzilla-daemon
2016-02-21 16:18 ` [Bug 112631] Cannot open encrypted Luks filesystem. Cruptsetup error bugzilla-daemon
2016-02-21 16:19 ` bugzilla-daemon
2016-02-21 16:20 ` bugzilla-daemon
2016-02-21 16:22 ` bugzilla-daemon
2016-02-21 16:35 ` bugzilla-daemon
2016-02-21 20:14 ` bugzilla-daemon
2016-02-21 21:27 ` bugzilla-daemon
2016-02-23  8:34 ` bugzilla-daemon
2016-02-23  9:37 ` bugzilla-daemon
2016-02-23 19:41 ` bugzilla-daemon
2016-02-23 20:30 ` bugzilla-daemon
2016-02-23 20:52 ` bugzilla-daemon
2016-02-24 21:01 ` bugzilla-daemon
2016-03-07 17:57 ` bugzilla-daemon
2016-03-07 18:03 ` bugzilla-daemon
2016-03-11 17:38 ` bugzilla-daemon
2016-03-11 17:43 ` bugzilla-daemon
2016-03-11 17:43 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-112631-13602-f2pCFB0vFw@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).