From: Harsh Shandilya <msfjarvis@gmail.com>
To: Harsh Shandilya <harsh@prjkt.io>, stable@vger.kernel.org
Subject: Re: [PATCH 0/4] 4.17-rc1 stable tagged ext4 patches for 3.18.y
Date: Sat, 21 Apr 2018 04:53:26 +0530 [thread overview]
Message-ID: <012E38BA-2CD9-4078-A685-74F392D15258@gmail.com> (raw)
In-Reply-To: <20180420222612.18881-1-harsh@prjkt.io>
On 21 April 2018 3:56:08 AM IST, Harsh Shandilya <harsh@prjkt.io> wrote:
>These are all the ext4 patches that were tagged for -stable and failed
>to apply to 3.18.y.
>
>Side note: Patch e15dc99dbb9c ("ALSA: pcm: Fix endless loop for XRUN
>recovery in OSS emulation")
>which was tagged for -stable is not required on 3.18.y so I have
>skipped
>the backport.
Please ignore this for the time being, I accidentally mailed the wrong set of patches. I'll post fixed and rebased versions of all patches later today, need to sleep this 5AM fogginess off.
tired and stupid,
Harsh Shandilya, PRJKT Development LLC
next prev parent reply other threads:[~2018-04-20 23:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 22:26 [PATCH 0/4] 4.17-rc1 stable tagged ext4 patches for 3.18.y Harsh Shandilya
2018-04-20 22:26 ` [PATCH 1/4] ext4: add validity checks for bitmap block numbers Harsh Shandilya
2018-04-21 12:28 ` [PATCH 1/3] " Harsh Shandilya
2018-04-20 22:26 ` [PATCH 2/4] ext4: fail ext4_iget for root directory if unallocated Harsh Shandilya
2018-04-21 12:28 ` [PATCH 2/3] " Harsh Shandilya
2018-04-20 22:26 ` [PATCH 3/4] ext4: don't allow r/w mounts if metadata blocks overlap the superblock Harsh Shandilya
2018-04-21 12:29 ` [PATCH 3/3] " Harsh Shandilya
2018-04-21 20:07 ` Theodore Y. Ts'o
2018-04-22 2:30 ` Harsh Shandilya
2018-04-22 4:01 ` Theodore Y. Ts'o
2018-04-22 4:04 ` Harsh Shandilya
2018-04-20 22:26 ` [PATCH 4/4] ext4: force revalidation of directory pointer after seekdir(2) Harsh Shandilya
2018-04-20 23:23 ` Harsh Shandilya [this message]
2018-04-21 12:21 ` [PATCH 0/3] 4.17-rc1 stable tagged ext4 patches for 3.18.y Harsh Shandilya
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=012E38BA-2CD9-4078-A685-74F392D15258@gmail.com \
--to=msfjarvis@gmail.com \
--cc=harsh@prjkt.io \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.