On Fri, Apr 21, 2017 at 10:37:06AM +0200, Greg KH wrote: > On Thu, Apr 20, 2017 at 03:34:19PM +0200, Greg KH wrote: > > On Thu, Apr 20, 2017 at 02:07:47PM +0100, Germano Percossi wrote: > > > Hi, > > > > > > On 20/04/17 12:44, Greg KH wrote: > > > > On Thu, Apr 20, 2017 at 12:10:00PM +0100, Germano Percossi wrote: > > > > > The reason why I asked it's because I did not receive any > > > > > "Failed" notification, so I assumed you did not even try. > > > > > > > > I tried, but for patches without any specific "Fixes:" tag, I have to > > > > just guess that if the patch does not apply, then it was not wanted > > > > to go that far back. > > > > > > > > > > You were right in your assumption about 18ea43113f: it could be ported > > > but it is not so important for 3.18 and 4.4 because we are not using > > > persistent handles there. > > > > > > For what concerns a0918f1ce6 "remove bad network.." on 3.18 I just ran > > > git cherry-pick a0918f1ce6 > > > on stable/linux-3.18.y without any problem. > > > Unless you use other commands with fuzz level lower than 2 > > > it should apply as is. > > > > Odd, it does apply, thanks. I'll apply it for the next 3.18-stable > > release after the current -rc one is released in a few days. > > Hm, but it isn't in 4.4-stable, you want it there too, right? It > doesn't apply cleanly there: > > Applying cifs-remove-bad_network_name-flag.patch to linux-4.4.y > Applying patch cifs-remove-bad_network_name-flag.patch > patching file fs/cifs/cifsglob.h > Hunk #1 succeeded at 906 (offset -42 lines). > patching file fs/cifs/smb2pdu.c > Hunk #1 FAILED at 1171. > Hunk #2 succeeded at 1036 with fuzz 2 (offset -241 lines). > 1 out of 2 hunks FAILED -- rejects in file fs/cifs/smb2pdu.c Oh nevermind, you already sent the backport for that, sorry for the noise... greg k-h