On 04/08/2015 11:26 PM, Greg KH wrote: > On Wed, Apr 08, 2015 at 07:00:37PM +0300, Boaz Harrosh wrote: >> On 04/08/2015 06:56 PM, Boaz Harrosh wrote: >>> From: Yigal Korman <yigal@xxxxxxxxxxxxx> >>> >>> [For Stable 4.0.X] >>> The parallel patch at 4.1-rc1 to this patch is: >>> Subject: mm: new pfn_mkwrite same as page_mkwrite for VM_PFNMAP >>> >>> We need this patch for the 4.0.X stable tree if the patch >>> Subject: dax: use pfn_mkwrite to update c/mtime + freeze protection >>> >>> Was decided to be pulled into stable since it is a dependency >>> of this patch. The file mm/memory.c was heavily changed in 4.1 >>> hence this here. >>> >> >> I forgot to send this patch for the stables tree, 4.0 only. >> >> Again this one is only needed if we are truing to pull >> Subject: dax: use pfn_mkwrite to update c/mtime + freeze protection >> >> Which has the Stable@ tag. The problem it fixes is minor and might >> be skipped if causes problems. > > I can't take patches in the stable tree that are not in Linus's tree > also. Why can't I just take a corrisponding patch that is already in > Linus's tree, why do we need something "special" here? > > thanks, > Hi greg Yes sorry I did not explain very well. the akpm tree in linux-next as two patches: 8dca515 mm: new pfn_mkwrite same as page_mkwrite for VM_PFNMAP dac1bd2 dax: use pfn_mkwrite to update c/mtime + freeze protection Now these patches will hit Linus tree in 4.1 merge window. The second patch is tagged with stable@ CC, because it fixes DAX which was introduced in 4.0. It depends on the 1st patch. However the first patch is not tagged stable@ because it will not apply at all to 4.0. This is because it patches mm/memory.c which will completely change in 4.1. This is why I sent this special patch which has the same exact title, and does exactly the same as the 1st patch but on the 4.0 Kernel. So when you encounter this 2nd patch with the Stable@ tag. I think the best is to just ignore it, and wait for complains, which will most probably not come because DAX is pretty experimental. (But if we do pull it we will need this here) > greg k-h > Thanks Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
