<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/drivers/char/ipmi/ipmb_dev_int.c, branch dev-5.4</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-5.4</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-5.4'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2020-02-24T05:01:27+00:00</updated>
<entry>
<title>Merge tag 'v5.4.21' into dev-5.4</title>
<updated>2020-02-24T05:01:27+00:00</updated>
<author>
<name>Joel Stanley</name>
<email>joel@jms.id.au</email>
</author>
<published>2020-02-24T05:01:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=3409ca6f2234aa37c2f54ca42aa6a3bde00a92c0'/>
<id>urn:sha1:3409ca6f2234aa37c2f54ca42aa6a3bde00a92c0</id>
<content type='text'>
This is the 5.4.21 stable release

Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>drivers: ipmi: fix off-by-one bounds check that leads to a out-of-bounds write</title>
<updated>2020-02-19T18:53:05+00:00</updated>
<author>
<name>Colin Ian King</name>
<email>colin.king@canonical.com</email>
</author>
<published>2020-01-14T14:40:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=cf0ea974b6a2c9308149f747db0ab30de1b5d36b'/>
<id>urn:sha1:cf0ea974b6a2c9308149f747db0ab30de1b5d36b</id>
<content type='text'>
commit e0354d147e5889b5faa12e64fa38187aed39aad4 upstream.

The end of buffer check is off-by-one since the check is against
an index that is pre-incremented before a store to buf[]. Fix this
adjusting the bounds check appropriately.

Addresses-Coverity: ("Out-of-bounds write")
Fixes: 51bd6f291583 ("Add support for IPMB driver")
Signed-off-by: Colin Ian King &lt;colin.king@canonical.com&gt;
Message-Id: &lt;20200114144031.358003-1-colin.king@canonical.com&gt;
Reviewed-by: Asmaa Mnebhi &lt;asmaa@mellanox.com&gt;
Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drivers: ipmi: Modify max length of IPMB packet</title>
<updated>2020-01-06T23:03:59+00:00</updated>
<author>
<name>Vijay Khemka</name>
<email>vijaykhemka@fb.com</email>
</author>
<published>2019-12-11T19:01:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=671f6224548fde167b0cc0e1c3fb852df202561b'/>
<id>urn:sha1:671f6224548fde167b0cc0e1c3fb852df202561b</id>
<content type='text'>
As per IPMB specification, maximum packet size supported is 255,
modified Max length to 240 from 128 to accommodate more data.

Signed-off-by: Vijay Khemka &lt;vijaykhemka@fb.com&gt;
Message-Id: &lt;20191211190155.1279610-1-vijaykhemka@fb.com&gt;
Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
(cherry picked from commit 380665becdeeb4f455c23582b7f32e6b3cea27d2)
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>drivers: ipmi: Support raw i2c packet in IPMB</title>
<updated>2020-01-06T23:03:59+00:00</updated>
<author>
<name>Vijay Khemka</name>
<email>vijaykhemka@fb.com</email>
</author>
<published>2019-12-11T18:56:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=885952dacfa2d2f8fd7a83474e4925aefd69b180'/>
<id>urn:sha1:885952dacfa2d2f8fd7a83474e4925aefd69b180</id>
<content type='text'>
Many IPMB devices don't support smbus protocol and this driver
only supports the smbus protocol at the moment.

Added support for the i2c protocol as well. There will be a variable
"i2c-protocol" passed by the device tree or ACPI table which determines
whether the protocol is i2c or smbus.

Signed-off-by: Vijay Khemka &lt;vijaykhemka@fb.com&gt;
Reviewed-by: Asmaa Mnebhi &lt;asmaa@mellanox.com&gt;
Message-Id: &lt;20191211185604.1266063-1-vijaykhemka@fb.com&gt;
[IPMB.txt had moved to driver-api/ipmb.rst, I adjusted]
Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
(cherry picked from commit 042f057fe2dcf38682d85d9f88df00d1a8d45dbd)
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>drivers: ipmi: Support for both IPMB Req and Resp</title>
<updated>2020-01-06T22:57:16+00:00</updated>
<author>
<name>Vijay Khemka</name>
<email>vijaykhemka@fb.com</email>
</author>
<published>2019-11-06T18:29:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=a7c784e3a0e2a4053400ee5cccc3d343d05fdf58'/>
<id>urn:sha1:a7c784e3a0e2a4053400ee5cccc3d343d05fdf58</id>
<content type='text'>
Removed check for request or response in IPMB packets coming from
device as well as from host. Now it supports both way communication
to device via IPMB. Both request and response will be passed to
application.

Signed-off-by: Vijay Khemka &lt;vijaykhemka@fb.com&gt;
Message-Id: &lt;20191106182921.1086795-1-vijaykhemka@fb.com&gt;
Reviewed-by: Asmaa Mnebhi &lt;Asmaa@mellanox.com&gt;
Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
(cherry picked from commit 0d8633bf5311177c9a26d75daec677cd87e3261b)
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>Fix uninitialized variable in ipmb_dev_int.c</title>
<updated>2019-07-24T20:53:21+00:00</updated>
<author>
<name>Asmaa Mnebhi</name>
<email>Asmaa@mellanox.com</email>
</author>
<published>2019-07-24T19:32:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=71be7b0e7d4069822c89146daed800686db8f147'/>
<id>urn:sha1:71be7b0e7d4069822c89146daed800686db8f147</id>
<content type='text'>
ret at line 112 of ipmb_dev_int.c is uninitialized which
results in a warning during build regressions.
This warning was found by build regression/improvement
testing for v5.3-rc1.

Reported-by: build regression/improvement testing for v5.3-rc1.
Fixes: 51bd6f291583 ("Add support for IPMB driver")
Signed-off-by: Asmaa Mnebhi &lt;Asmaa@mellanox.com&gt;
Message-Id: &lt;571dbb67cf58411d567953d9fb3739eb4789238b.1563996586.git.Asmaa@mellanox.com&gt;
Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
</content>
</entry>
<entry>
<title>fix platform_no_drv_owner.cocci warnings</title>
<updated>2019-06-23T21:16:52+00:00</updated>
<author>
<name>kbuild test robot</name>
<email>lkp@intel.com</email>
</author>
<published>2019-06-23T18:50:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=a88b6d5668bef303d01b706a35946bfc8e67402c'/>
<id>urn:sha1:a88b6d5668bef303d01b706a35946bfc8e67402c</id>
<content type='text'>
drivers/char/ipmi/ipmb_dev_int.c:352:3-8: No need to set .owner here. The core will do it.

 Remove .owner field if calls are used which set it automatically

Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci

Fixes: 51bd6f291583 ("Add support for IPMB driver")
CC: Asmaa Mnebhi &lt;Asmaa@mellanox.com&gt;
Signed-off-by: kbuild test robot &lt;lkp@intel.com&gt;
Message-Id: &lt;20190623185044.GA94834@lkp-kbuild21&gt;
Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
</content>
</entry>
<entry>
<title>ipmi: ipmb: don't allocate i2c_client on stack</title>
<updated>2019-06-19T14:03:55+00:00</updated>
<author>
<name>Arnd Bergmann</name>
<email>arnd@arndb.de</email>
</author>
<published>2019-06-19T12:50:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=21feadd024e747123bc0aaba8d8cbef2b5eda058'/>
<id>urn:sha1:21feadd024e747123bc0aaba8d8cbef2b5eda058</id>
<content type='text'>
The i2c_client structure can be fairly large, which leads to
a warning about possible kernel stack overflow in some
configurations:

drivers/char/ipmi/ipmb_dev_int.c:115:16: error: stack frame size of 1032 bytes in function 'ipmb_write' [-Werror,-Wframe-larger-than=]

There is no real reason to even declare an i2c_client, as we can simply
call i2c_smbus_xfer() directly instead of the i2c_smbus_write_block_data()
wrapper.

Convert the ipmb_write() to use an open-coded i2c_smbus_write_block_data()
here, without changing the behavior.

It seems that there is another problem with this implementation;
when user space passes a length of more than I2C_SMBUS_BLOCK_MAX
bytes, all the rest is silently ignored. This should probably be
addressed in a separate patch, but I don't know what the intended
behavior is here.

Fixes: 51bd6f291583 ("Add support for IPMB driver")
Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Message-Id: &lt;20190619125045.918700-1-arnd@arndb.de&gt;
Acked-by: Asmaa Mnebhi &lt;Asmaa@mellanox.com&gt;
[Broke up a line &gt;80 characters on i2c_smbus_xfer().]
Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
</content>
</entry>
<entry>
<title>Add support for IPMB driver</title>
<updated>2019-06-10T19:47:10+00:00</updated>
<author>
<name>Asmaa Mnebhi</name>
<email>Asmaa@mellanox.com</email>
</author>
<published>2019-06-10T18:57:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=51bd6f291583684f495ea498984dfc22049d7fd2'/>
<id>urn:sha1:51bd6f291583684f495ea498984dfc22049d7fd2</id>
<content type='text'>
Support receiving IPMB requests on a Satellite MC from the BMC.
Once a response is ready, this driver will send back a response
to the BMC via the IPMB channel.

Signed-off-by: Asmaa Mnebhi &lt;Asmaa@mellanox.com&gt;
Acked-by: vadimp@mellanox.com
Message-Id: &lt;319690553a0da2a1e80b400941341081b383e5f1.1560192707.git.Asmaa@mellanox.com&gt;
[Move the config option to outside the ipmi msghandler, as it's not
 dependent on that.  Fixed one small whitespace issue.]
Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
</content>
</entry>
</feed>
