)]}'
{
  "log": [
    {
      "commit": "4b181144e6c1c25aaba9b9fc7cc70c95495ecb92",
      "tree": "93f85f1c99f097ec3c60f45b7b917c1b0dfbf7f9",
      "parents": [
        "e312c24cf8229f9b6e76dbfd5d99eefe21f4ac0a"
      ],
      "author": {
        "name": "Johannes Berg",
        "email": "johannes@sipsolutions.net",
        "time": "Sat Aug 08 11:03:58 2009 +0200"
      },
      "committer": {
        "name": "John W. Linville",
        "email": "linville@tuxdriver.com",
        "time": "Fri Aug 14 09:13:51 2009 -0400"
      },
      "message": "cfg80211: fix locking for SIWFREQ\n\n\"cfg80211: validate channel settings across interfaces\"\ncontained a locking bug -- in the managed-mode SIWFREQ\ncall it would end up running into a lock recursion.\n\nThis fixes it by not checking that particular interface\nfor a channel that it needs to stay on, which is as it\nshould be as that\u0027s the interface we\u0027re setting the\nchannel for.\n\nReported-by: Reinette Chatre \u003creinette.chatre@intel.com\u003e\nReported-by: Kalle Valo \u003ckalle.valo@iki.fi\u003e\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nTested-by: Kalle Valo \u003ckalle.valo@iki.fi\u003e\nTested-by: Reinette Chatre \u003creinette.chatre@intel.com\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n"
    },
    {
      "commit": "59bbb6f7574bc693ed8313b98eac641116c95b94",
      "tree": "da24ed15c5e375782e79b3dab7022d2100a7987a",
      "parents": [
        "f26b32ed4bd5780855a79bb17fb1a431fa867dad"
      ],
      "author": {
        "name": "Johannes Berg",
        "email": "johannes@sipsolutions.net",
        "time": "Fri Aug 07 17:22:35 2009 +0200"
      },
      "committer": {
        "name": "John W. Linville",
        "email": "linville@tuxdriver.com",
        "time": "Fri Aug 14 09:13:42 2009 -0400"
      },
      "message": "cfg80211: validate channel settings across interfaces\n\nCurrently, there\u0027s a problem that affects regulatory\nenforcement and connection stability, in that it is\npossible to switch the channel while connected to a\nnetwork or joined to an IBSS.\n\nThe problem comes from the fact that we only validate\nthe channel against the current interface\u0027s type, not\nagainst any other interface. Thus, you have any type\nof interface up, additionally bring up a monitor mode\ninterface and switch the channel on the monitor. This\nwill obviously also switch the channel on the other\ninterface.\n\nThe problem now is that if you do that while sending\nbeacons for IBSS mode, you can switch to a disabled\nchannel or a channel that doesn\u0027t allow beaconing.\nCombined with a managed mode interface connected to\nan AP instead of an IBSS interface, you can easily\nbreak the connection that way.\n\nTo fix this, this patch validates any channel change\nwith all available interfaces, and disallows such\nchanges on secondary interfaces if another interface\nis connected to an AP or joined to an IBSS.\n\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n"
    }
  ]
}